DHCP stops working after a while

[Cake]

I have this problem now too. My ubiquity device - M5 nano (my edge device) got the surge of all power surges 3 weeks back, so just got a replacement yesterday. This one is a mikrotik brand - SXT SA5. I am double nat'd, when lease exp. and its time for my AC68U to renew the log shows- WAN Connection: ISP's DHCP did not function properly.
I have tried normal, aggressive and using a static IP.

blimey
sigh,

edit: I should add I can toggle the wan on and off on the AC68U. It will get me a new lease and this happens like clockwork when the lease expires.

 

[Cake]

Working on this a little today. This happens at random every couple of hours instead of when lease expires.
Searching the forms I use

service restart_wan

until I figure out a better solution.

When I put in:

nvram show | grep -e "wan_ipaddr=" | cut -f2 -d"="

size: 55064 bytes (10472 left)
0.0.0.0
0.0.0.0
192.168.101.128
192.168.101.200

The 192.168.101.128 was from my old modem, why is this in the list? The router's GUI WAN says 192.168.101.200

Does anybody know how to track down why 192.168.101.128 is in the list? Could this be my trouble?

Edit: What is wan_wan_ipaddr? Is it safe to remove?

wan0_ipaddr_x=192.168.101.200
wan_wan_ipaddr_x=192.168.101.128

Edit#3 This did not work.

nvram unset wan_wan_ipaddr_x
nvram commit

I have change my static ip wan of router to 192.168.101.128 via the GUI. So far so good.

Edit #4
I think I got it fixed, I think its is the ISP's device incorrect settings making trouble. Hope this helps someone else who is double nat'd and just switched out ISP modems, just set your router to static, and use the ip listed in nvram's wan_wan_ipaddr_x value. The unset in edit#3 really didn't help. Now

nvram show | grep -e "wan_ipaddr=" | cut -f2 -d"="

size: 55018 bytes (10518 left)
0.0.0.0
0.0.0.0
192.168.101.128
192.168.101.128

No problems for almost a hour.
Final Edit: Nevermind, all of the above didn't do the trick. :-( I will be using somebody else's script from another thread to monitor and restart wan I guess.

 

[Cake]

Took the time to download and flash new firmware. I have now switched my blame to the router (AC68U) and thyself. (I plugged in a dumb switch behind the isp's device, no linux computers in the house have had dhcp problems yesterday or today.)

Why is 192.168.101.200 and 192.168.101.128 found in nvram wan?

The only thing I could think of is the OpenVPN server (which is set to always on), generated a opvn file. That .ovpn file listed 192.168.101.128 (which is wrong).
As mention before I am double nat'd, so I would have just downloaded the ovpn from the router and changed the .opvn file to my public ip (ddns) manually, and set up port forwarding on the router from the ISP's device. The next step is to forgot that I did that, and fast forward 1 year later. When new ISP modem is fired up and gives out 192.168.101.200 it never got changed in the vpn_server config. -->That is my best guess. Only a guess and I am a "Newb" Hope this may help if someone else has the same trouble.

Yesterday I was using a script, and set it to ping google every 30 seconds and restart the wan when fail. Thats how bad it got to be. Very frustrating.

Fresh install, all is well now.