Raxis

thats ok, I fixed it myself and repackaged the latest image with the fix and loaded it on my xr 500 and its working fine I'll slap it up here but everyone pay attention below: I AM NOT OFFCIAL, OR PART OF NETGEAR OR NETDUMA I AM A RANDOM INTERNET USER if anyone uses it, it's at your own risk because its put together by a rando on the internet and all that, feel free to stick it in ai to compare it vs the stock one and have it find the difference Don't be annoying to the dumaos team if you choose to try my fixed version, there is no support, you are on your own. Changelog: WAN DCHP client fix usr/share/udhcpc/default.script line 478 errant trailing space removed XR500-V2.3.5.152-fixed.img

Looks like the new one on the netgear site is using dumaos 3.3.539 also they still haven't fixed the wan dhcp bug where every 12 hours or so it kicks you off for a second. do they have a bug reporting thing? its a trailing space in usr/share/udhcpc/default.script line 478, someone did a workaround to fix another bug and put an extra space in which makes it rejig the wan every time it renews even if its the same ip kicking you off. Basically "$router" != "$old_router " needs to be "$router" != "$old_router" got sick of it so I went hunting

yup, when its setup with default IP and acting as the main router it works/loads as normal, it only errors out when its not the main router/default ip

routerlogin.net sends it off to the netgear page, because this unit is being used in AP mode atm. but when reset(and not AP mode) routerlogin.net doesn't resolve/work is it possible dumaos isn't running because it expects to be the main router on the default IP range?

even after a reset (in firmware) a reset(with button for 30 seconds), upgrading to intermediate, RC10, RC14 I get Dumaos is not running(no matter how long I wait) only way I can log into router is to use ipaddresshere/adv_index.htm anyone got a fix for this?