U-boot layout is nice. But is there a config option to opt for WEB interface instead of TFTP? Newer u-boot's especially TP-Link's trigger web interface when pressed reset button while starting up. Which is much normie-friendly.
How are normies gonna know what TFTP is? That's not normie friendly.
Or how about this, a permanent area in flash, which is like 8MB. It will contain an initramfs image, it will run when the main fw can't run?
if you're able to make your way from standard to u-boot layout, you're probably familiar with TFTP ...
is the webui part of uboot, or is it a web server executing uboot commands in the background ?
In TP-Link Archer AX80 eu, I think it's tied to the u-boot. That would be probably complicated. How about my other idea?
if it comes with uboot, sources should be available.
a stripped down image, only used for recovery, it's probably doable.
TFTP is already simple enough and friendly enough. No need to overcomplicate it with HTML tags and new bugs.
If you look at the ubootmod code for EX5601 you can see that booting to the recovery initramfs firmware is available but has to be selected via UART (option 3). So I guess it should be possible to implement your idea but you will have to adjust the logic / order such that it gets executed by pressing the reset button instead.
Sounds like the OO.
TFTP recovery process has been used even by Enterprise Servers & Network equipments since long time ago. I guess it has a long tradition that many IT folks are already familiar with.
For what is worth: check out bootloader section in OpenWRT Wiki for more info on many existing bootloader projects out there. For bootloader with web-based UI, you might want to check out bl-mt798x project - although you need to pay attention to the caveats mentioned in that Wiki page.
All Gl-inet routers ave a uboot-webui that is based on this:
Yes, very true, but those having to do batch reflashing for a rollout will find a uboot-webui far quicker and slicker than the faff of setting up a tftp server or client (some uboot implementations are servers, some clients at the whim of the manufacturers) then being quick enough the catch the exact moment to connect.
Same goes for on site updates/maintenance, all that is needed is a laptop with an ethernet port and a browser, no special setup.
So for the average home user, a uboot-webui is simplicity itself.
There must be a certain entry level required for reflashing hardware. If a user has troubles configuring IP address in required range, starting TFTP server... Well, should he reflash a router at all?
AFAIK, upstream u-boot doesn't include a httpd. As a consequence, maintaining a patchset (keeping it working and secure) would take considerable development effort downstream, by the OpenWrt maintainer. And size is always an issue (even on NAND, raw access guarantee).
Indeed. One might argue if you really want to mess with your router - you probably want to equip yourself with a bit more skills. Anyway as in IT tradition: if certain practice works then don’t break it - that’s probably the reason behind TFTP popularity.
Even simple html parser and server are complex things. It requires memory to store, it requires skill to write. Without that it will just create big surface for an attacker. Do manufacturers want their routers attacked and reflashed? Most don't. That's why I don't expect webUI bootloaders to become a common thing.
True. As @slh has said the same: Maintaining a web server would take significant effort and have it work across multiple CPU targets require even more efforts. The benefit probably would not justify the cost for it - and many routers are currently flashed without changing u-boot.
Brightspeed XR1710G same device as the W1700K - #70 by YYH2913 might be of interest to you.
don't take the discussion there (unless you own a XR1710G), since it'd be considered off topic.
I do have a XR1710G, so this is for my own device's adaptation. With the upstream still being unstable, recovering and flashing from the web UI via the reset method is obviously much easier than using TFTP or xmodem.
I was referring to OP, this isn't "your" thread.
My mistake, I misunderstood who you were replying to! Thanks.
Speaking of the web recovery, I really don't think U-Boot WebUI is meant for everyday users. Most people never need to unbrick or flash custom builds; they just need standard vendor updates. An unnecessary web service like that just brings extra security concerns for the average user.