I created a list of 50 address reservation in the LAN (DHCP), it took me like an hour, then after a reboot it was completely wiped, not a single device
Is there a way to save the settings in the GLi.Net GUI to avoid this problems again?
Update 10 hours later: It happened again, fortunately this time I had saved settings in LuCI and I was able to recover quickly, but I am worry about the reliability of the 4.6.3-op24 firmware
Did you configure the address reservation in the GL GUI?
And if have edited them in the Luci as well?
Yes, everything was done via the GL GUI, I only used LuCI to backup and restore settings, I think the problem happened when I turn ON and OFF a few times IPv6 and rebooted, after one of those reboots I noticed the laptop IP was not the reserved one, I checked the GL GUI for reserved IPs and it was empty.
Maybe when the GL GUI was updating the /etc/config/dhcp file while enabling and disabling IPv6 something got corrupted and erased that information from the DHCP file?
It just got erased again, randomly, I think I am going to switch to vanilla OpenWrt
NOTE: I did enable and then disabled IPv6 a few minutes before it got wiped, I checked /etc/config/dhcp and none of the IP reservations were there, so, magically the DHCP file is being updated behind the scenes, not good.
Now I can say with certainty that it is something related to the IPv6 on/off process, I just got wiped the list for the 4th time
Got it.
IPv6 Disabled:
IPv6 Enabled:
Reboot:
It did not reproduce by my side. please check if other features enabled?
In my case every time it happened, it was within 1-2 hours after I turned on/off IPv6
@bruce please follow this sequence, with a brand new installation, all default settings, add a few static leases, then enable IPv6, reboot, disable IPv6, reboot, and enable again IPv6, wait 1-2 hours and check if the static leases are still there, thank you
I have 19 static leases and IPV6 enabled, and my MT6000 does not show any problem.
I started with 4.5.8, upgrade to 4.6.2 and finally to 4.6.3 op24.
In my situation, I think the problem was that I added the static leases before enabling IPv6, I have now enabled IPv6 first, then created the static leases, so far no issues
Sorry, I follow these steps and cannot reproduce:
4.6.2 stable firmware,
reset default settings,
add static IP (2 devices),
IPv6 enable,
reboot,
IPv6 disable,
reboot,
IPv6 enable,
online 5h,
the 2 devices static leases still in list.
Something similar happened to me with MT6000 firmware 4.6.2
Tried my best to narrow it down but the best I could get to was that I was assigning too many IPs at once.
Unlike the OP, I was not using ipv6.
Everything started with a "Privacy Warning" in my phone:
"This network is blocking encrypted DNS traffic.
The names of websites and other servers your device accesses on this network may be monitored and recorded by other devices on this network."
I assumed it was the AdGuard Home, so I disabled it. Same message but I started to notice devices in the network to disconnect. Generally I have about 22 devices and it went down to 12.
After enabling/disabling AdGuard a few times I could notice my Address Reservation list was back to the one from like a month ago (about 5 devices reserved). At this point with AdGuard disabled, I proceeded to rebuild my Address Reservation list, and slowly I kept losing devices again.
I tried deleting the new items and the devices reconnected.
Now my network is happy but my ocd kicks in from time to time as I really wanted to organize all my IPs.
I am not sure if this could be relating to naming devices with special characters like ' " ( [.
Seems to work when just naming the device but not when assigning an IP.
Another thing I thought about was that the DHCP feature might not be ok with reassigning an IP while the device is connected. At this point I was already 3 hours in of troubleshooting so did not test to disconnect the devices completely ( I did test rebooting but did not work), then reconnect.
Hope this could narrow down the investigation a bit for the GLiNet folks.
Thanks!
I was also assigning many IPs quickly, I think I did around 20-30 in just a few minutes, I was also running AdGuard, I never found the root cause for the issue, probably adding to many static leases in a short period of time?
Question for you, did you define the gateway under DHCP server?
I am starting to believe that maybe the DHCP server may be culprit (or at least part of it)
My raspberry pi was acting pretty weird, on the client list the eth0 and wlan0 IPs were constantly swapping or duplicating each other. I had defined in the raspberry the gatway and IPs
Back to MT6000. I had noticed the "gateway" space was optional, but I just filled it in anyway even if it's the same as the router. Now the raspberry is stable. Same to my Ring my cameras, which were constantly coming in and out from the list.
I will go back to the Addressing Reservation later today. I am proceeding with one Ip at a time now
No, I have always been using the default gateway. Good luck and keep as posted with the new static lease adventure
my problem has been solved by defining the gateway under DHCP server
Somehow the space says "optional" so I only assumed all the devices would respect the router as the DHCP server.
I have three APs as clients that maybe were acting up. Not sure but I have no problems anymore. Have defined my full list of "Addressing Reservation" for about 30 clients and my network is happy.
Not entirely sure if this may help with the original ipv6 problem. I'd say give it a try
Thanks
Just to be sure, if you are using DHCP to assign static routes then the DHCP server should NOT assign a gateway (per DHCP RFC). Maybe not useful, I just wanted to make sure you knew this part while looking at it.
Thanks!
Idk what to do now. This works for me. I guess I’ll plan to test again without assigning the gateway
If you use classless static routing - just publish a 0.0.0.0/0 route with your gateway address. By RFC a dhcp client is supposed to ignore the default gateway, so you just distribute it the same way as your other routes. But none of this sounds like the problem you are having based on your comments.
The Address Reservation for the clients IP, do you configure this in the GL GUI or the Luci?
