NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR50 Cannot change DHCP range or IP Subnet
Since I upgraded to firmare V2.7.1.6 I'm having some problems... My router seems to have its LAN interface configured with IP subnet 192.168.1.0/24 and the router's address is 192.168.1.250 The...
The start and end of the dhcp range are parameters. Maybe it would be possible to set them from the telnet interface. i.e.
config set dhcp_start = 192.168.1.2
config set dhcp_end = 192.168.1.99 (or something)
config commit
and there is lan_ipaddr, which on my Orbi is lan_ipaddr = 192.168.1.1
I just realized that while I have several soldering irons, I have no device with an RS232 port. Does this mean U-Boot is not ever in my future?
TBH, uboot was far outside *my* comfort zone too... but when my router bricked after a short power brownout the TFTP recovery process didn't work at all and I wasn't prepared to junk $400 of Orbi equipment that was less than 2 years old! Connecting the serial console to the boot loader was the only way to get things working again - but there is almost zero documentation for this.
Thanks for mentioning the firmware version... turns out my router's auto update is also not working (the page that checks for firmware updates says 'service unreachable'). I just installed v2.7.2.102 manually and will see if things are any better. The 'release notes' that came with this version are basically empty so I don't know what it supposedly fixes other than:
- Fixes the device manager display issue on the Orbi app.
The IP subnet info was unaffected by the update (probably to be expected) - but I can't mess with that until after my wife finished here zoom pilates class or I'll be in deep trouble! ;-)
Cheers!
The start and end of the dhcp range are parameters. Maybe it would be possible to set them from the telnet interface. i.e.
config set dhcp_start = 192.168.1.2
config set dhcp_end = 192.168.1.99 (or something)
config commit
and there is lan_ipaddr, which on my Orbi is lan_ipaddr = 192.168.1.1
I just realized that while I have several soldering irons, I have no device with an RS232 port. Does this mean U-Boot is not ever in my future?
I only just discovered the telnet interface... and yes, this did indeed allow me to fix the problem!
config set lan_ipaddr=192.168.1.1
config show
will dump all the current configuration info and I spotted a few other bugus things (e.g. the netbios name was set to some garbage for me)
NOTE: For those who don't know about this, you go to the following URL:
and click the 'enable telnet' box then you can log into the router's management command line using
telnet 192.168.1.1
Obviously substitute the correct IP address for your router
This thread is also full of useful info https://community.netgear.com/t5/Orbi/ORBI-RBK50-RBS50-Tips-Tricks-Hidden-Secrets-etc/td-p/1745266
Here are the instructions for the ORBI serial port if you ever need it...
https://www.snbforums.com/attachments/orbi-serial-port-pdf.23898
found via a web search that turned up this page on installing/fixing custom router firmware:
You can buy a USB debug dongle from Amazon for about $10 and it attaches to three header pins on the Orbi router motherboard. (cracking open the router case is a whole nother thing! ;-)