The rollback warning seems to be confusing many people.
The explanation of what to do next is hard to follow.
For example
"perform an unchecked configuration apply."
Could be:
apply the configuration anyway.
The button "Apply unchecked" could be "Apply anyway" or just "Apply"
Many more under: https://forum.openwrt.org/search?q=apply%20unchecked
From what I've read so far the problem is not that the dialog is confusing but that it does not appear at all. At least this is what's reported by the users. Haven't been able to reproduce yet though.
I don't recall not observing the dialog when browsing using IPv4 addresses
However when i use the full-hostname e.g openwrt.lan I don't have any issues at all, the session seems to go over IPv6 and changing IPv4 address/subnet does not trigger rollback.
Yeah, it is expected that access by hostname should be more or less smooth.
After reviewing the linked threads again I am still not sure what the actual problem is. Will change the wording in the dialog anyway to make it more explicit.
fwiw, I don't know if the following info is of any help, but I managed to reproduce the problem on my test Home Hub 5A.
18.06.1 installed. I deleted the WAN6 interface, and reconfigured the WAN interface with a static IP address and changed ifname from dsl0 to eth0.2, which I often do. Pressed 'Save & Apply' for WAN changes to be completed.
Then I progressed to trying to change the LAN IP address as shown below.
BusyBox v1.28.3 () built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 18.06.1, r7258-5eb055306f
-----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@OpenWrt:/#
root@OpenWrt:/#
root@OpenWrt:/#
root@OpenWrt:/# ifconfig
br-lan Link encap:Ethernet HWaddr 88:A6:C6:0E:C2:2A
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::8aa6:c6ff:fe0e:c22a/64 Scope:Link
inet6 addr: fd5c:b5:fd1b::1/60 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:458 errors:0 dropped:0 overruns:0 frame:0
TX packets:351 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:52540 (51.3 KiB) TX bytes:94296 (92.0 KiB)
eth0 Link encap:Ethernet HWaddr A2:EB:AA:6C:2B:8E
inet6 addr: fe80::a0eb:aaff:fe6c:2b8e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:529 errors:0 dropped:5 overruns:0 frame:0
TX packets:394 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:75212 (73.4 KiB) TX bytes:102390 (99.9 KiB)
eth0.1 Link encap:Ethernet HWaddr 88:A6:C6:0E:C2:2A
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:462 errors:0 dropped:4 overruns:0 frame:0
TX packets:351 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:52724 (51.4 KiB) TX bytes:94296 (92.0 KiB)
eth0.2 Link encap:Ethernet HWaddr A2:EB:AA:6C:2B:8E
inet addr:192.168.1.209 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::a0eb:aaff:fe6c:2b8e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1192 (1.1 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:100 errors:0 dropped:0 overruns:0 frame:0
TX packets:100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:7352 (7.1 KiB) TX bytes:7352 (7.1 KiB)
root@OpenWrt:/#
root@OpenWrt:/#
root@OpenWrt:/#
Used LuCI to try and change LAN IP address from 192.168.1.1 to 192.168.111.1.
After pressing 'Save & Apply' button, the following appeared on console at around 10 seconds later during the 30 seconds count down.
root@OpenWrt:/# [ 88.154549] br-lan: received packet on eth0.1 with own address as source address
[ 88.196189] br-lan: port 1(eth0.1) entered disabled state
[ 88.329787] device eth0.1 left promiscuous mode
[ 88.333312] br-lan: port 1(eth0.1) entered disabled state
[ 88.339692] device eth0 left promiscuous mode
[ 88.346641] IPv6: ADDRCONF(NETDEV_UP): eth0.1: link is not ready
[ 88.405942] device eth0 entered promiscuous mode
[ 88.415254] br-lan: port 1(eth0.1) entered blocking state
[ 88.419355] br-lan: port 1(eth0.1) entered disabled state
[ 88.425539] device eth0.1 entered promiscuous mode
[ 88.441036] br-lan: port 1(eth0.1) entered blocking state
[ 88.445098] br-lan: port 1(eth0.1) entered forwarding state
I pressed the Enter key a couple of times to bring up prompt.
After the 30 seconds had elapsed, the message offering to Revert or apply changes DID NOT appear. The console displayed the following additional messages:
root@OpenWrt:/#
root@OpenWrt:/#
root@OpenWrt:/#
root@OpenWrt:/# [ 118.190557] br-lan: received packet on eth0.1 with own address as source address
[ 118.228516] br-lan: port 1(eth0.1) entered disabled state
[ 118.238282] device eth0.1 left promiscuous mode
[ 118.241797] br-lan: port 1(eth0.1) entered disabled state
[ 118.248830] device eth0 left promiscuous mode
[ 118.258250] IPv6: ADDRCONF(NETDEV_UP): eth0.1: link is not ready
[ 118.314358] device eth0 entered promiscuous mode
[ 118.321805] br-lan: port 1(eth0.1) entered blocking state
[ 118.325917] br-lan: port 1(eth0.1) entered disabled state
[ 118.332222] device eth0.1 entered promiscuous mode
[ 118.341901] br-lan: port 1(eth0.1) entered blocking state
[ 118.346021] br-lan: port 1(eth0.1) entered forwarding state
No further activity on console. Cannot ping router on 192.168.1.1 or 192.168.111.1 from PC wired to LAN port. I then executed 'ifconfig' command.
root@OpenWrt:/#
root@OpenWrt:/#
root@OpenWrt:/#
root@OpenWrt:/#
root@OpenWrt:/# ifconfig
br-lan Link encap:Ethernet HWaddr 88:A6:C6:0E:C2:2A
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::8aa6:c6ff:fe0e:c22a/64 Scope:Link
inet6 addr: fd5c:b5:fd1b::1/60 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:83 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5562 (5.4 KiB) TX bytes:1892 (1.8 KiB)
eth0 Link encap:Ethernet HWaddr A2:EB:AA:6C:2B:8E
inet6 addr: fe80::a0eb:aaff:fe6c:2b8e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:953 errors:0 dropped:5 overruns:0 frame:0
TX packets:781 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:134198 (131.0 KiB) TX bytes:242699 (237.0 KiB)
eth0.1 Link encap:Ethernet HWaddr 88:A6:C6:0E:C2:2A
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:83 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5562 (5.4 KiB) TX bytes:1892 (1.8 KiB)
eth0.2 Link encap:Ethernet HWaddr A2:EB:AA:6C:2B:8E
inet addr:192.168.1.209 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::a0eb:aaff:fe6c:2b8e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:71 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:3418 (3.3 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:274 errors:0 dropped:0 overruns:0 frame:0
TX packets:274 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:20984 (20.4 KiB) TX bytes:20984 (20.4 KiB)
root@OpenWrt:/#
root@OpenWrt:/#
root@OpenWrt:/#
If I power cycle the hub, I can regain access to the hub at 192.168.1.1
Okay, can you reproduce the same problem solely via SSH?
uci set network.lan.ipaddr=192.168.111.1
/sbin/reload_config
I think I've just 'stumbled' across why I am having this issue on HH5A.
Default LAN IP is 192.168.1.1.
I always configure WAN IP to be 192.168.1.209 to be able to wire the hub to my main network later.
I think I've discovered if the WAN and LAN IP are still on same subnet (ie. 192.168.1.x), the message offering to Revert or Apply changes when I want to change the LAN IP to say 192.168.111.1 does NOT appear.
If I start with changing WAN IP to say 192.168.0.209 instead of 192.168.1.209, then the message offering to Revert or Apply changes does seem to appear.
I'm just testing a few other different combinations following this new observation in case I am mistaken.
Ah - interesting observation! It might be that the browser confirmation "slipped through" before the WAN got up leading to the address conflict so from LuCI's pov the client was reachable and the rollback timer got cancelled. Need to try reproducing that.
In answer to your earlier question, yes, the UCI set command worked.
BusyBox v1.28.3 () built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 18.06.1, r7258-5eb055306f
-----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@OpenWrt:/# ping 192.168.1.222
PING 192.168.1.222 (192.168.1.222): 56 data bytes
64 bytes from 192.168.1.222: seq=0 ttl=128 time=0.744 ms
64 bytes from 192.168.1.222: seq=1 ttl=128 time=0.604 ms
^C
--- 192.168.1.222 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.604/0.674/0.744 ms
root@OpenWrt:/#
root@OpenWrt:/#
root@OpenWrt:/# uci set network.lan.ipaddr=192.168.111.1
root@OpenWrt:/#
root@OpenWrt:/# /sbin/reload_config
root@OpenWrt:/#
root@OpenWrt:/# [ 81.008665] br-lan: port 1(eth0.1) entered disabled state
[ 81.022860] device eth0.1 left promiscuous mode
[ 81.026303] br-lan: port 1(eth0.1) entered disabled state
[ 81.151178] device eth0 left promiscuous mode
[ 81.158702] IPv6: ADDRCONF(NETDEV_UP): eth0.1: link is not ready
[ 81.230766] device eth0 entered promiscuous mode
[ 81.242388] br-lan: port 1(eth0.1) entered blocking state
[ 81.246502] br-lan: port 1(eth0.1) entered disabled state
[ 81.252725] device eth0.1 entered promiscuous mode
[ 81.264509] br-lan: port 1(eth0.1) entered blocking state
[ 81.268547] br-lan: port 1(eth0.1) entered forwarding state
root@OpenWrt:/#
root@OpenWrt:/# [ 99.516443] lantiq,xrx200-net 1e108000.eth eth0: port 0 lost link
[ 99.522971] br-lan: port 1(eth0.1) entered disabled state
[ 101.564485] lantiq,xrx200-net 1e108000.eth eth0: port 0 got link
[ 101.570480] br-lan: port 1(eth0.1) entered blocking state
[ 101.574514] br-lan: port 1(eth0.1) entered forwarding state
[ 105.660472] lantiq,xrx200-net 1e108000.eth eth0: port 0 lost link
[ 105.666499] br-lan: port 1(eth0.1) entered disabled state
[ 107.708484] lantiq,xrx200-net 1e108000.eth eth0: port 0 got link
[ 107.713826] br-lan: port 1(eth0.1) entered blocking state
[ 107.718520] br-lan: port 1(eth0.1) entered forwarding state
root@OpenWrt:/# ifconfig
br-lan Link encap:Ethernet HWaddr 88:A6:C6:0E:C2:2A
inet addr:192.168.111.1 Bcast:192.168.111.255 Mask:255.255.255.0
inet6 addr: fe80::8aa6:c6ff:fe0e:c22a/64 Scope:Link
inet6 addr: fd5c:b5:fd1b::1/60 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:248 errors:0 dropped:0 overruns:0 frame:0
TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:32875 (32.1 KiB) TX bytes:6639 (6.4 KiB)
eth0 Link encap:Ethernet HWaddr 86:A3:CA:D6:71:10
inet6 addr: fe80::84a3:caff:fed6:7110/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:822 errors:0 dropped:5 overruns:0 frame:0
TX packets:531 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:118269 (115.4 KiB) TX bytes:118212 (115.4 KiB)
eth0.1 Link encap:Ethernet HWaddr 88:A6:C6:0E:C2:2A
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:252 errors:0 dropped:4 overruns:0 frame:0
TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:33059 (32.2 KiB) TX bytes:6639 (6.4 KiB)
eth0.2 Link encap:Ethernet HWaddr 86:A3:CA:D6:71:10
inet addr:192.168.1.209 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::84a3:caff:fed6:7110/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2966 (2.8 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:143 errors:0 dropped:0 overruns:0 frame:0
TX packets:143 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:10215 (9.9 KiB) TX bytes:10215 (9.9 KiB)
root@OpenWrt:/#
root@OpenWrt:/#
root@OpenWrt:/# ping 192.168.111.2
PING 192.168.111.2 (192.168.111.2): 56 data bytes
64 bytes from 192.168.111.2: seq=0 ttl=128 time=0.666 ms
64 bytes from 192.168.111.2: seq=1 ttl=128 time=1.000 ms
^C
--- 192.168.111.2 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.666/0.833/1.000 ms
root@OpenWrt:/#
The preconditions were the same as with the LuCI based test?
yes, same pre-conditions.
I just tried to change LAN IP address, but using different addresses to confirm my earlier observations.
Started with:
WAN: 192.168.12.209
LAN: 192.168.111.1
Change WAN to 192.168.111.209. Press 'Save & Apply'. Change successfully complete. WAN and LAN using same subnet.
WAN: 192.168.111.209
LAN: 192.168.111.1
Now to change LAN to 192.168.0.1. Press 'Save & Apply'. No message to offer Revert or Apply changes. ie. cannot change LAN IP using LuCI.
The workaround for my situation would be to simply change the LAN IP before changing the WAN IP to avoid both WAN and LAN using apparently the same subnet.
Yeah, in this case the conceptual problem is that the initial configuration (the one with 192.168.111.209 + 192.168.111.1) is already flawed (subnet conflict) and it only works "by chance" due to the correct arp entries etc. to be present. Since LuCI will roll back to the flawed config, but with reinitialized interfaces and flushed arp entries, you end up in the lockout state.
Not really sure how to solve that. The most robust solution would be assigning a higher metric to WAN so that overlapping subnets would not result in routing conflicts.
I agree, it is bad practise to assign same subnet to both WAN and LAN interfaces, but it works, perhaps not intentionally, with LuCI in LEDE 17.01.
Oh well, I guess my observations probably isn't related to other users who are unable to change the LAN IP using LuCI. At least the mystery is solved for the HH5A when I've encountered this issue using 18.06.
I confirm this is still happening with OpenWrt 21.02.1 on (my specific case) D-Link DAP-2695.
Any changes I do keeps reverting using Luci
Ref.:
https://forum.openwrt.org/t/lan-ip-change-gets-rolled-back-on-d-link-dap-2695/113978