New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#457 - LEDE 17.01-rc1 r3042: Changing LAN static IP address doesn't force new DHCP addresses LEDE #5493
Comments
richb-hanover: Output from getstats.sh (https://github.com/richb-hanover/OpenWrtScripts/blob/master/getstats.sh)
===== getstats.sh at Thu Feb 2 04:20:06 UTC 2017 =====
[ cat /etc/banner ]
_________
/ /\ _ ___ ___ ___
/ LE / \ | | | __| \| __|
/ DE / \ | |__| _|| |) | _|
/________/ LE \ |____|___|___/|___| lede-project.org
\ \ DE /
\ LE \ / -----------------------------------------------------------
\ DE \ / Reboot (17.01.0-rc1, r3042-ec095b5)
\________\/ -----------------------------------------------------------
|
nbd: This is not a LEDE issue at all. On some devices reconfiguring might lead to having ethernet disconnect and reconnect automatically, but there's no guarantee of that. This would have the same effect as pulling the ethernet cable and putting it back in. |
richb-hanover:
Install LEDE 17.01-rc1 r3042 on both Archer C7 and Netgear WDR3400:
I log in successfully to 192.168.1.1, enter a password, then use web gui to change static IP address of the LAN interface (to 192.168.250.1)
The web gui shows a spinner, but (of course) doesn't reconnect to the router, since the address has changed.
I waited a while (60 seconds?) and my OSX box doesn't notice that the Ethernet has a new IP - it's still on 192.168.1.x
If I disconnect the Ethernet cable and reconnect immediately, within a second or two, OSX detects the new (correct) IP address in the correct 192.168.250.0/24 subnet.
I think OpenWrt/CeroWrt used to recover without requiring a disconnect of the Ethernet cable (but could be mistaken).
This isn't a severe problem, because disconnecting/reconnecting the Ethernet is a perfect workaround.
The text was updated successfully, but these errors were encountered: