WAN issues

[Trekster]

Hi all

For the last couple of days i've had WAN issues, more specifically the AC66 loses the DHCP lease. Now i've read all of the other posts regarding this and have been in touch with my ISP who say "our end looks ok, no issues".

So i'm back to square one, with no solution in sight. I'm using CAT6 shielded cable between my modem(Netgear CG3000) and the WAN port of the AC66. I'm not seeing any disconnects nor does the lease "die" when it runs out, usually the lease is over 2 days but it does lose it in a couple of hours.

The only thing i can see in the system logs is:

Nov 26 22:05:36 nmbd[479]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.1 for name WORKGROUP<1d>.
Nov 26 22:05:36 nmbd[479]: This response was from IP 192.168.0.145, reporting an IP address of 192.168.0.145.
Nov 26 22:09:56 WAN Connection: ISP's DHCP did not function properly.
Nov 26 22:09:56 stop_nat_rules: apply the redirect_rules!
Nov 26 22:10:02 dnsmasq[31323]: exiting on receipt of SIGTERM
Nov 26 22:10:02 dnsmasq[31719]: started, version 2.67 cachesize 1500
Nov 26 22:10:02 dnsmasq[31719]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
Nov 26 22:10:02 dnsmasq[31719]: warning: interface ppp1* does not currently exist
Nov 26 22:10:02 dnsmasq[31719]: asynchronous logging enabled, queue limit is 5 messages

So not much help there...is there any way, as a stop gap measure until resolved, that i could setup something on the router to ping a site and restart the WAN if there is no response?

EDIT:

Using FW 3.0.0.4.374.35_2

 

[Trekster]

Thanks for the info, i've just downgraded to 34_2 and will monitor the situation.

I'm still interested if someone could point me in the right direction regarding setting up a job to restart the WAN, when a site doesn't respond, could be usefull for me in the future

 

[Trekster]

Tried a downgrade but the issue still persists :-/


Sent from my RM-821_eu_euro1_425 using Tapatalk

 

[RMerlin]

You can't "lose" a lease. Once you get an IP, you have a lease. If the connection drops in the mean time, it's not that you lost the lease, but that the connection between you and the ISP flat out dropped.

I would suspect the modem and the connection to the ISP first if you have issues with different FW versions. Have your ISP confirm that the signal levels are normal from their end.