Customized image builds via Firmware Selector and ASU/OWUT broken https://forum.openwrt.org/t/customized-image-builds-via-firmware-selector-and-asu-owut-broken/230500 #openwrt

Customized image builds via Firmware Selector and ASU/OWUT broken https://forum.openwrt.org/t/customized-image-builds-via-firmware-selector-and-asu-owut-broken/230500 #openwrt
"Speedrunning Laptop Deployment for Non-Profit Organisations" Vortrag von @AgentK am 20.04.2025, 14:00–14:35, auf der ##easterhegg #eh22
"Wie wir bei @computertruhe Chemnitz 140 gespendete Laptops effizient mit Open Source (FOG Project, OpenWRT) refurbishen – von Lager & Reinigung bis zur automatisierten OS-Installation. "
#FOGProject #OpenWRT
Managing Network Devices via #Orgmode Table and #OpenWRT Router
https://karl-voit.at/2025/04/18/openwrt-config-via-org/
I do maintain only one single table with all of my devices. I can control their IP and their ability to connect to the Internet (or not).
With this table, I do have a great overview of my devices and their IPs.
I thought you might like the idea ...
I've been dabbling with replacing my ancient Asus router with a Raspberry Pi over the last few days and thought I'd write up the process for anyone interested.
https://www.neilbullock.co.uk/raspberry-pi-5-router-using-openwrt
Easter hack: terraform-provider-openwrt
https://linderud.dev/blog/easter-hack-terraform-provider-openwrt/
Banana Pi BPI-RV2 RISC-V Router board public sale,World‘s first RISC-V Router board,OpenWrt support
https://docs.banana-pi.org/en/BPI-RV2/BananaPi_BPI-RV2
#router #gateway #network #riscv #openwrt #bananapi #raspberrypi
.@FLOSS_Weekly EP 829: THIS MACHINE KILLS VOGONS - @herberticus & Frank joined @JP_Bennett to chat about @mtaht's legacy, #bufferbloat, #LibreQoS, #Starlink & #SpaceX, #OpenWrt and MORE! cc @hackaday
https://hackaday.com/2025/04/16/floss-weekly-episode-829-this-machine-kills-vogons/
#DaveTaht #RFC8290 #FLOSS #BandwidthIsALIE #FQ_CoDel
#sch_CAKE #OpenSource #FLOSSWeekly #Hackaday FQCoDel #schCAKE #latency #jitter #Linux #Rust #RustLang #LinuxKernel #WiFi #broadband #QoE #QoS #QualityOfExperience #QualityOfService
My biggest issue with #OpenWRT so far is the upgrade process. As in, keeping the OS up to date. The package manager's upgrade functionality, which is fully baked into the OS and its GUI web interface, prominently displays a warning at the top that tells you not to use it. Don't upgrade packages, it can and will break your system: https://openwrt.org/meta/infobox/upgrade_packages_warning
Okay, then why is that feature baked into the OS at all?
Meanwhile, the sysupgrade feature, which is the recommended way to keep the OS up to date, is also baked into the OS, but only at the cli level. If you want to use the GUI web interface, you need to manually install the attended-sysupgrade package, after which point you can manually re-flash the OS whenever you want to using up to date packages, provided that you also (somehow) keep up to date about their releases without the use of a real tool to check for updates using the GUI. Why isn't that baked into the OS instead?
The whole thing is just very confusing.
If someone following me is interested, i started a terraform openwrt provider.
It's a veryvery shallow shim around the uci JSON RPC calls from OpenWRT.
Just hacking on this for the support I need. But others might be interested.
I finally battle tested my BananaPi RPI-R3 with #OpenWRT. After a long time I am configuring weird network staffs (#yggdrasil, #xray and etc) without my beloved #nix. GUI configs sometimes really cosy... before you need something unusual (ALWAYS for me).
I also tried #nixos (bless nixos-sbc), but it's not cool to write #uboot to SD card or ssd. I need to try something like a generic UEFI boot loader on onboard eMMC. Ideally secure boot, but I don't think I have anouth mana for that kind of magic
OpenWrt Developers released #OpenWrt version 24.10.1. https://openwrt.org/downloads
OpenWrt 24.10.1 - Service Release https://forum.openwrt.org/t/openwrt-24-10-1-service-release/230061 #openwrt
Mein selbst zusammen-gehacktes/kompiliertes #OpenWrt für den TP-Link WR841 v10 mit 16 MB Flash (statt vom Hersteller 4 MB) geht leider ständig in eine #Bootloop und startet nicht richtig, vermutlich weil es es das root-Dateisystem unter /dev/mtdblock4 nicht mounten kann.
Zurücksetzen/Reset hab ich schon mehrfach probiert;
- OpenWrt mit sysupgrade neu installieren
- mit firstboot alles resetten.
Hat nix gebracht.
Kann mir da jemand helfen?
Im #Failsafe-Modus kann ich es zum Glück starten.
UPDATE: Seems like it was a faulty router firmware update (GL.inet Flint 2) that caused issues.
I guess I will replace the OEM firmware (which is a fork of OpenWRT) with pure #OpenWRT after all
I'm running a 10 year old router (a Ubiquiti Edgerouter X). I just updated it to the latest #openwrt release - I have a small service window at lunch where I can take the Internet down without impacting my work AND I don't get complaints from the family.
I love that I can still run current firmware on a 10 year old device.
Klassisches Beispiel von: Ich sollte mich mal mit was neuem beschäftigen, aber der Bequem-Widerstand war zu lange zu groß. Dann doch mal ein paar Stunden reingelesen, etwas experimentiert und ab jetzt, solange es sich vermeiden lässt, nix anderes mehr.