The OpenWrt Firmware Selector

Release and security announcements
1184

Recently, I wanted to test OpenWrt 24.10.0 and was very impressed with owut. Thanks, @efahl!

I am managing at least ten Raspberry Pi 4 OpenWrt setups for my friends and family, which has helped me understand networking and security in a broader context.

Based on my comment, I am facing some issues with the firmware selector, and the same problem is present in owut since both use the same API.

If you do not provide a custom rootfs_size_mb, the SquashFS option includes the ext4 overlay. Conversely, if you do provide a custom rootfs_size_mb, the firmware uses the f2fs overlay. This inconsistency is a bit dangerous for triggering the update remotely because the /overlay has to migrate from ext4 to f2fs. This has already bricked the setup or created an inconsistent state. Please have a look at my comment.

Please have a look at the screenshot.

Screenshot 2024-12-27 at 13.21.29
Screenshot 2024-12-27 at 13.21.291424×1876 353 KB

I have a few questions:

  1. Why is the Raspberry Pi 4 profile's default rootfs_size_mb set to 84 MB? Most users opt for Pi 4 options to add additional packages, and since the minimum size for SD cards and built-in MMCs is more than 4 GB, can't we increase the default rootfs_size_mb for Pis to at least 128 MB or at least 256 MB?

  2. Is it possible to extend the API to accept additional /overlay partition types for the SquashFS root filesystem option, such as f2fs or ext4 or at least make is constant either f2fs.

  3. Can we add two more options under "Customize installed packages and/or first boot script" to influence the rootfs_size_mb option and the /overlay partition type for the SquashFS, as mentioned in point 2?

Thank you all devs for the wonderful job.