I would like to know what the correct way of changing the router's LAN IP address. I would like to know because my attempts to do so this far have resulted in me losing web access to the router and I end up having to reset the router.
What I've tried so far is to go to http://192.168.1.1/cgi-bin/luci/admin/network/network/lan then change the address in the "IPv4 address" text box then save and apply. After I, say, changed this address from 192.168.1.1 to 192.168.100.1, the web interface is no longer available on either 192.168.1.1 or 192.168.100.1, the DHCP server is still handing out IP addresses in the 192.168.1.0 subnet, PCs connected to the LAN ports no longer have internet access and though I can SSH into the router, I have to connect to 192.168.1.1 rather than 192.168.100.1.
I've witnessed it with chrome on Windows, Mint Linux. Also tried IE and Edge and turning off any popup blockers.
The AutoRollback popup message offering the option to accept the change doesn't appear after 30 seconds count down. I think it is because there is complete loss of access to the router. eg. cannot ping it at all on existing or new IP address. Power cycling the hub restores access.
It's not clear why I witness this problem frequently, but I think it may only happen immediately after flashing the router with 18.06 image even when you choose not to 'keep settings'. (I frequently flash one of my hubs between 17.01 and 18.06 to check things)
I have found if I factory reset the hub using Reset button on the rear, and try again, then I am able to change the LAN IP address using LuCI successfully.
Can you provide a link to this report, if any exist?
It not usually common to claim a known feature of software is a "bug." In fact, it's very confusing. So I'm not sure if you're referring to the rollback feature in OpenWrt 18. There is a known method to proceed.
"Bug" as in luci doesn't accept the changes when it can no longer access the original ip address for the gui, therefore causing the rollback. It shouldn't rollback but simply not respond to a new interface or write the new contents to /etc/config/network and try to resolve the url to the new gateway ip.
Yes, you described a known feature, designed to prevent locking yourself out of the router accidentally. ...So what happens when you hit APPLY CHANGES ANYWAY???
mindwolf:
It locks the user out
1.) doesn't respond to the original page e.g. 192.168.1.1
2.) doesn't respond to the newly set page e.g. 192.168.2.1
Also, why were you trying to @XJDHDR ?
Referring to his issue specifically
Yes, this is a known issue of trying to change the IP via GUI. Most people don't realize, they're now required to browse to the page at the new IP. This is something I rarely see in documents...perhaps it needs to be added.
Can you post the thread you're referencing, as that account only shows this thread. As you may notice, he marked it as solved.
No I'm not trolling, inquire with @moeller0 about my validity. Last night is when I setup my network with the (2) R7000's. The GUI didn't and wouldn't respond to the changes. You guys really need to work on your people skills.
Yes Sir I have followed the basic steps I loaded the firmware via serial cable/tftp, then factory reset. After not being able to connect via the changes I downloaded a fresh copy, loaded via serial/tftp again and still the same results. The only solution was manual configs.
But...consider making another post about your issue; as you see that feature works.
This topic will close 10 days after the last reply.
mindwolf:
I loaded the firmware via serial cable/tftp, then factory reset. After not being able to connect via the changes I downloaded a fresh copy, loaded via serial/tftp again and still the same results. The only solution was manual configs.