Comments (11)
Eine damit verbundene Frage ist z.B. wie wir die Konfiguration aus der alten Firmware in die neue übernhmen bzw. wie wir alte Knoten updaten.
from firmware.
I think the first migration from the old firmware to our new one can only be done by hand. But for the next releases an autoupdater can be handy. The updater needs to take care of updating the config if needed.
from firmware.
this also relates to #308
from firmware.
#308 is unclear to me and (apparently) is about changing the root filesystem type to JFFS2 first and foremost.
In contrast, this issue is about automatically flashing new firmware images once they become available, sort of an automatic "sysupgrade", which is a different thing and quite simple to implement (at least for routers in standard configuration).
from firmware.
this seems to be an approach to build individual images: libremesh/chef#31 .
Even it helps not to push them onto the routers automatically.
from firmware.
u have to fillet the dinosaur before u can eat it.
Do u think it's necessary to build individual images?
Otherwise if @sarumpaet knows about a simple solution to sysupgrade automagically we are close to kind of a working way.
from firmware.
@bobster-galore See the very first comment by cholin. We just need to make buildbot release files discoverable (automatically) and set up some router-side script that does the updating. For Gluon, the "discovery" part is their manifest file (e.g., https://cccgoe.de/freifunk/stable/sysupgrade/stable.manifest - note the router type identifier - first column - is very similar to what we use in, e.g., https://util.berlin.freifunk.net/hardware?name=tp-wr842-v3 ), and the updating script is https://github.com/freifunk-gluon/packages/blob/master/admin/autoupdater/files/usr/sbin/autoupdater . We could probably just adapt our build process/add the manifest file and copy the Gluon autoupdater.
from firmware.
@sarumpaet that would be really nice since we could get rid of really outdated fw like kathleen 0.0.0 etc. which is more a security risk than a nice memory.
Furthermore it would be a comfortable promise not to see ppl where u installed a freifunk-router. ;)
Perhaps there could be an early adopters mode to get rc-Versions installed? E.g. choosing only stable or rc also, ppl / installations who would care for a testing mode?
from firmware.
Even it helps not to push them onto the routers automatically.
The is an app for that. Currently it still requires certs for https but could later just rely on usign. A cron could run the updater automatically to check for new releases or outdated packages
Do u think it's necessary to build individual images?
These images are only individual if you changed the default installed packages. If a package combination was build before, it's reused. This enables auto-upgrades even for users with modified firmwares and only builds actually requested images, not all, possibly never used, images.
Anyway, just my two cents.
from firmware.
For the record: Gluon switch to a new autoupdater implemented in C some time ago: https://github.com/freifunk-gluon/packages/tree/master/admin/autoupdater/src
from firmware.
An other option might be the "Attendedsysupgrade"-suite (https://github.com/aparcar/attendedsysupgrade-server) based on a GSoC project.
It seems to be a generic project for OpenWrt-based firmwares.
from firmware.
Related Issues (20)
- luci-mod-freifunk-ui: footer(?) broken on upstream-master HOT 11
- Documentation for Firmware Build System HOT 5
- packages/configtools: "sharenet-switch" should generate a "wan" section HOT 3
- Ubiquiti Rocket M5: hardware not conforming to regulatory requirements
- patches: openwrt/imagebuilder-custom-postinst-script: does not apply on recent OpenWrt-19.07 HOT 2
- luci-mod-freifunk-ui: footer(?) missing with recent OpenWrt-19.07 HOT 1
- LuCI configuration-change: timeout of confirmation triggers rollback HOT 3
- snmp-addons: Option "Instance" is deprecated
- OpenWrt-base for developing next release (year 2020) HOT 11
- wolfSSL vs. mbedTLS HOT 1
- daemon.warn dnsmasq-dhcp: DHCP packet received on br-wan which has no address HOT 4
- xDSL: WAN not configurable via LuCI due missing packages HOT 5
- Failed to execute template 'freifunk/index' HOT 3
- OWM-App: verschieben ins globale Freifunk-repo HOT 3
- build: selecting an invalid package is silently accepted
- Upgrading from pre-Hedy will lead to missing UCI-section for GPIO-control
- From email: wizard cannot be run anymore after initial installation HOT 2
- improve performance by distributing irqs over all CPUs HOT 1
- dhcp defaults: fix commit f4d3207 HOT 1
- Move to main as default branch
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from firmware.