The OpenWrt Firmware Selector

Just added 21.02.0-rc3 to the firmware wizard, please test!

Both previous RCs had issues with the ImageBuilder so custom images wouldn't work, but should be fixed now!

2 Likes

Upgraded a TP-Link RE650 v1 and a GL-iNet AR750S (NOR) from rc2 to rc3. First time I've used libremesh - included packages for diffutils, sqm and relayd. No problems so far (~30 mins). Many thanks.

1 Like

Worked great to grab rc3 on my WRT32X thanks, this is all I use now for firmwares.

@aparcar Thanks for your work. I was able to generate custom 21.02.0-rc3 images for my Raspberry Pi 4B (64-bit), Netgear R7800 and TP-Link Archer A7 v5 using https://chef.libremesh.org.

@aparcar is see you are injecting ucert into peoples images

  1. does this pose interoperability issues with official or personal builds?
  2. is there an ethical obligation to disclose custom modifications that deviate from official releases?

I'm adding ucert and luci as default packages, which are normally not included (in snapshot builds). I'm using the server for my own devices as well and they all trust the ASU build key. This is a security improvement from my point of view but since people may don't want this I'm already thinking on how to make it optional.

  • does this pose interoperability issues with official or personal builds?

No, ucert is only activate if you actively require key checking via an extra env variable.

  • is there an ethical obligation to disclose custom modifications that deviate from official releases?

It shows you the list of installed packages which I'd consider as "disclosure".

Overall, please use the other thread for such questions, this thread is meant for the firmware wizard which only allows to download stock images.

Update: I modified ASU to no longer add the public CA key and also removed ucert from the default package selection. This weakens the upgrade security but removes any "hidden" modifications.

Whoever want's security on the upgrade server should install the two packages auc and ucert, the former allows custom image requests from a running device and the latter verifies them.

Thanks for the update,working fine for me without any problems i tried it yesterday

Might I suggest simplifying the dropdown list for Firmware Selector, the amount of options are starting to pile up. There probably only ever needs to be 5 options. The upcoming snapshot/release, the current snapshot/release, then the master nightly:

  1. 21.02-Release (latest RC, or final)
  2. 21.02-Snapshot
  3. 19.07-Release (latest update)
  4. 19.07-Snapshot
  5. Master-Snapshot

Great work on this simple tool and thanks.

Nice!

I noticed that if I switch versions after previously entering/selecting the model number, the page does not automatically refresh with links to the images.

You have to re-enter/select the model number again for the page to refresh.

I just noticed that now 3 snapshot releases exist

  • the previous
  • the current
  • the next version

I never saw those other 2 folders except the master in the file system, the other 2 seem to be hidden.
I would find it helpful, if the hidden-flag gets removed in the filesystem.

I have not been able to reproduce this. Can you provide an concrete example? Thanks!

@aparcar is this something you can help with?

I'm unsure what's the best way to handle this. Hiding them results in less testing, showing them results in more people using it in production hand having a hard time.

I get your point.
But it does not make sense to show the additional snapshots in the firmware selector and hide them in the downloads-page, where tech-guys hang around.


As A tech savy person I really like that those additional snapshot builds exist and I actually missed that they existed. I also think the previous and current snapshot are less dangerous to use than the upcoming snapshot (although all 3 are not meant for freshmans).

To address your concerns, once the new firmware selector is meant to go productive, I would rather recommend to simplify the regular download page on "https://openwrt.org/downloads", such that there are only 2 links left on that page, to make it easier to use for non-IT-experts:

  1. the link to the new firmware selector with a "Download OpenWRT here" message
  2. a link to a separate page where all the stuff of the old download page gets moved, to be renamed to "tech experts downloads" or similar. There is lots of stuff on the old download page overwhealming newbees. But the 3 snapshots would fit in very well on a tech experts download page.

@jow what is your opinion here? Should we show those pre-releases?

No, they shouldn’t be shown in a simple firmware selector.

4 Likes

Thanks for the timely response. I'll update the version file

@mwarning do you mind modifying the collect.py script that it ignores all 'pre-releases' but SNAPSHOTS?

Here ya go: https://gitlab.com/openwrt/web/firmware-selector-openwrt-org/-/merge_requests/53

Hi! Is chef.libremesh.org 's build server down? Attended sysupgrade seems to not be working.