WAN is randomly dropped and not re-aquired until reboot; C7 on Comcast cable

Installing and Using OpenWrt
1

I am using LEDE 17.01.2 on a TP-Link Archer C7v2 and having problems maintaining connection to Comcast Cable via TP-Link TC-7610 Modem. The connection starts out fine but about once a day the WAN goes down and requires a reboot to get the connection back. The log info shows the information at point of the drop. I never had any issues with my old Luma router. Has anyone seen similar issues with Comcast, TP-Link TC-7610 Modem, or LEDE 17.01.2 in general losing connectivity on a daily basis?

Along with the info at point of drop the syslog also shows dozens of the following each hour.

Sat Sep 16 13:29:01 2017 daemon.info odhcpd[957]: Raising SIGUSR1 due to address change on br-lan
Sat Sep 16 13:29:02 2017 daemon.info odhcpd[957]: Using a RA lifetime of 1800 seconds on br-lan

syslog at point of WAN going down.

Sat Sep 16 17:11:35 2017 daemon.notice netifd: Interface 'wan6' is now down
Sat Sep 16 17:11:35 2017 daemon.notice netifd: Network alias '' link is down
Sat Sep 16 17:11:35 2017 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Sat Sep 16 17:11:35 2017 daemon.notice netifd: Interface 'wan6' is disabled
Sat Sep 16 17:11:35 2017 daemon.info odhcpd[957]: Raising SIGUSR1 due to address change on eth0
Sat Sep 16 17:11:35 2017 daemon.info odhcpd[957]: Raising SIGUSR1 due to default route change
Sat Sep 16 17:11:35 2017 daemon.info odhcpd[957]: Raising SIGUSR1 due to default route change
Sat Sep 16 17:11:35 2017 daemon.info odhcpd[957]: Raising SIGUSR1 due to address change on br-lan
Sat Sep 16 17:11:35 2017 daemon.info dnsmasq[1945]: reading /tmp/resolv.conf.auto
Sat Sep 16 17:11:35 2017 daemon.info dnsmasq[1945]: using local addresses only for domain lan
Sat Sep 16 17:11:35 2017 daemon.info dnsmasq[1945]: using nameserver 209.244.0.3#53
Sat Sep 16 17:11:35 2017 daemon.info dnsmasq[1945]: using nameserver 209.244.0.4#53
Sat Sep 16 17:11:35 2017 daemon.notice netifd: wan (1290): udhcpc: received SIGTERM
Sat Sep 16 17:11:35 2017 daemon.notice netifd: Interface 'wan' is now down
Sat Sep 16 17:11:35 2017 daemon.notice netifd: Interface 'wan' is setting up now
Sat Sep 16 17:11:35 2017 daemon.notice netifd: wan (13520): udhcpc: started, v1.25.1
Sat Sep 16 17:11:35 2017 daemon.notice netifd: wan (13520): udhcpc: sending discover
Sat Sep 16 17:11:36 2017 daemon.info odhcpd[957]: Using a RA lifetime of 0 seconds on br-lan
Sat Sep 16 17:11:37 2017 daemon.info dnsmasq[1945]: exiting on receipt of SIGTERM
Sat Sep 16 17:11:37 2017 daemon.info dnsmasq[13672]: started, version 2.77 cachesize 500
Sat Sep 16 17:11:37 2017 daemon.info dnsmasq[13672]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC no-ID loop-detect inotify
Sat Sep 16 17:11:37 2017 daemon.info dnsmasq-dhcp[13672]: DHCP, IP range 192.168.7.100 -- 192.168.7.249, lease time 12h
Sat Sep 16 17:11:37 2017 daemon.info dnsmasq[13672]: using local addresses only for domain lan
Sat Sep 16 17:11:37 2017 daemon.info dnsmasq[13672]: reading /tmp/resolv.conf.auto
Sat Sep 16 17:11:37 2017 daemon.info dnsmasq[13672]: using local addresses only for domain lan
Sat Sep 16 17:11:37 2017 daemon.info dnsmasq[13672]: using nameserver 209.244.0.3#53
Sat Sep 16 17:11:37 2017 daemon.info dnsmasq[13672]: using nameserver 209.244.0.4#53
Sat Sep 16 17:11:37 2017 daemon.info dnsmasq[13672]: read /etc/hosts - 3 addresses
Sat Sep 16 17:11:37 2017 daemon.info dnsmasq[13672]: read /tmp/hosts/odhcpd - 0 addresses
Sat Sep 16 17:11:37 2017 daemon.info dnsmasq[13672]: read /tmp/hosts/dhcp.cfg02411c - 2 addresses
Sat Sep 16 17:11:37 2017 daemon.info dnsmasq-dhcp[13672]: read /etc/ethers - 0 addresses
Sat Sep 16 17:11:38 2017 daemon.notice netifd: wan (13520): udhcpc: sending discover
Sat Sep 16 17:11:41 2017 daemon.notice netifd: wan (13520): udhcpc: sending discover
Sat Sep 16 17:12:11 2017 daemon.notice netifd: wan (13520): udhcpc: received SIGTERM
Sat Sep 16 17:12:11 2017 daemon.notice netifd: Interface 'wan' is now down
Sat Sep 16 17:12:11 2017 daemon.notice netifd: Interface 'wan' is setting up now
Sat Sep 16 17:12:11 2017 daemon.notice netifd: wan (13936): udhcpc: started, v1.25.1
Sat Sep 16 17:12:11 2017 daemon.notice netifd: wan (13936): udhcpc: sending discover
Sat Sep 16 17:12:14 2017 daemon.notice netifd: wan (13936): udhcpc: sending discover
Sat Sep 16 17:12:17 2017 daemon.notice netifd: wan (13936): udhcpc: sending discover
Sat Sep 16 17:13:11 2017 daemon.notice netifd: wan (13936): udhcpc: received SIGTERM
Sat Sep 16 17:13:11 2017 daemon.notice netifd: Interface 'wan' is now down
Sat Sep 16 17:13:11 2017 daemon.notice netifd: Interface 'wan' is setting up now
Sat Sep 16 17:13:11 2017 daemon.notice netifd: wan (14211): udhcpc: started, v1.25.1
Sat Sep 16 17:13:11 2017 daemon.notice netifd: wan (14211): udhcpc: sending discover
Sat Sep 16 17:13:14 2017 daemon.notice netifd: wan (14211): udhcpc: sending discover
Sat Sep 16 17:13:17 2017 daemon.notice netifd: wan (14211): udhcpc: sending discover
2

I have the same problem using LEDE 17.01.2 on a TP-Link Archer C2600 with DSL WAN connection but not the same syslog. It happens about once a week. When it fails, I can't even ping the router in the command window until I reboot it which seems to indicate that the error is in router itself.

3

I had nothing but problems at my home with comcast. I thought it was lede dropping the connection but the modem was disconnecting. If you can, take a look at your modem logs and see if you don't have a bunch of reboots. You can add the modem ip to an interface to be able to get to it from in side your network as opposed to having to directly plug into it from a computer. Lets say your modem IP address is 192.168.100.1:

  1. Add 192.168.100.2 as an interface on WAN
  2. From a browser on your network type in 192.168.100.1. You should be in the modem diagnostics page now.

Hopefully this helps narrow down the issue.

4

I tried to post the syslog but this 'Sorry, new users can only put 2 links in a post.' came up.

5

Aluu, what modem (make/model) are you using?