OpenWrt wan just wont talk to modem, reason?

If you have connectivity problems, please first disable all fancy stuff like dnscrypt-proxy, especially as it continuously spams your log about errors...

1 Like

disabled dnscrypt, adblocker, and samba not sure what else was fancy


root@OpenWrt:~# logread -f
Mon Aug 10 10:45:47 2020 daemon.notice netifd: Interface 'lan' is now down
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Registering new address record for fe80::1691:82ff:fe30:1ec9 on br-lan.*.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Withdrawing address record for 192.168.1.1 on br-lan.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Leaving mDNS multicast group on interface br-lan.IPv4 with address 192.168.1.1.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Interface br-lan.IPv4 no longer relevant for mDNS.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Interface br-lan.IPv6 no longer relevant for mDNS.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Leaving mDNS multicast group on interface br-lan.IPv6 with address fd7c:f47e:7275::1.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Withdrawing address record for fe80::1691:82ff:fe30:1ec9 on br-lan.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Withdrawing address record for fd7c:f47e:7275::1 on br-lan.
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.542356] br-lan: port 1(eth0.1) entered disabled state
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.552821] device eth0.1 left promiscuous mode
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.557403] device eth0 left promiscuous mode
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.561895] br-lan: port 1(eth0.1) entered disabled state
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: read /etc/hosts - 4 addresses
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: read /tmp/hosts/odhcpd - 0 addresses
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq-dhcp[14923]: read /etc/ethers - 0 addresses
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.637746] mvneta f1034000.ethernet eth0: Link is Down
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Interface eth0.IPv6 no longer relevant for mDNS.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::1691:82ff:fe30:1ec9.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Withdrawing address record for fe80::1691:82ff:fe30:1ec9 on eth0.
Mon Aug 10 10:45:47 2020 daemon.notice netifd: Interface 'lan' is disabled
Mon Aug 10 10:45:47 2020 daemon.warn dnsmasq[14923]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Mon Aug 10 10:45:47 2020 daemon.notice netifd: VLAN 'eth0.1' link is down
Mon Aug 10 10:45:47 2020 daemon.notice netifd: bridge 'br-lan' link is down
Mon Aug 10 10:45:47 2020 daemon.notice netifd: Interface 'lan' has link connectivity loss
Mon Aug 10 10:45:47 2020 daemon.notice netifd: Network device 'eth0' link is down
Mon Aug 10 10:45:47 2020 daemon.err odhcpd[2049]: setsockopt(IPV6_ADD_MEMBERSHIP): No such device
Mon Aug 10 10:45:47 2020 daemon.err odhcpd[2049]: setsockopt(SO_BINDTODEVICE): No such device
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.779155] mvneta f1034000.ethernet eth0: configuring for fixed/sgmii link mode
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.786883] mvneta f1034000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.794891] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.803188] br-lan: port 1(eth0.1) entered blocking state
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.808661] br-lan: port 1(eth0.1) entered disabled state
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.814319] device eth0.1 entered promiscuous mode
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.819135] device eth0 entered promiscuous mode
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.825212] br-lan: port 1(eth0.1) entered blocking state
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.830648] br-lan: port 1(eth0.1) entered forwarding state
Mon Aug 10 10:45:47 2020 daemon.notice netifd: Interface 'lan' is enabled
Mon Aug 10 10:45:47 2020 daemon.notice netifd: Interface 'lan' is setting up now
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Joining mDNS multicast group on interface br-lan.IPv4 with address 192.168.1.1.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: New relevant interface br-lan.IPv4 for mDNS.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Registering new address record for 192.168.1.1 on br-lan.IPv4.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Joining mDNS multicast group on interface br-lan.IPv6 with address fd7c:f47e:7275::1.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: New relevant interface br-lan.IPv6 for mDNS.
Mon Aug 10 10:45:47 2020 daemon.info avahi-daemon[2979]: Registering new address record for fd7c:f47e:7275::1 on br-lan.*.
Mon Aug 10 10:45:47 2020 daemon.notice netifd: Interface 'lan' is now up
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: using only locally-known addresses for domain test
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: using only locally-known addresses for domain onion
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: using only locally-known addresses for domain localhost
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: using only locally-known addresses for domain local
Mon Aug 10 10:45:47 2020 daemon.notice netifd: bridge 'br-lan' link is up
Mon Aug 10 10:45:47 2020 daemon.notice netifd: Interface 'lan' has link connectivity
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: using only locally-known addresses for domain invalid
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: using only locally-known addresses for domain bind
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: using only locally-known addresses for domain lan
Mon Aug 10 10:45:47 2020 daemon.notice netifd: Network device 'eth0' link is up
Mon Aug 10 10:45:47 2020 daemon.notice netifd: VLAN 'eth0.1' link is up
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: read /etc/hosts - 4 addresses
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: read /tmp/hosts/odhcpd - 1 addresses
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq[14923]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Mon Aug 10 10:45:47 2020 daemon.info dnsmasq-dhcp[14923]: read /etc/ethers - 0 addresses
Mon Aug 10 10:45:48 2020 daemon.notice netifd: wan (10285): udhcpc: received SIGTERM
Mon Aug 10 10:45:48 2020 daemon.notice netifd: wan (10285): udhcpc: entering released state
Mon Aug 10 10:45:48 2020 daemon.notice netifd: wan (10285): Command failed: Permission denied
Mon Aug 10 10:45:48 2020 daemon.notice netifd: Interface 'wan' is now down
Mon Aug 10 10:45:48 2020 daemon.notice netifd: Interface 'wan' is setting up now
Mon Aug 10 10:45:48 2020 daemon.notice netifd: wan (15404): udhcpc: started, v1.31.1
Mon Aug 10 10:45:48 2020 daemon.notice netifd: wan (15404): udhcpc: sending discover
Mon Aug 10 10:45:49 2020 daemon.info dnsmasq[14923]: read /etc/hosts - 4 addresses
Mon Aug 10 10:45:49 2020 daemon.info dnsmasq[14923]: read /tmp/hosts/odhcpd - 1 addresses
Mon Aug 10 10:45:49 2020 daemon.info dnsmasq[14923]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Mon Aug 10 10:45:49 2020 daemon.info dnsmasq-dhcp[14923]: read /etc/ethers - 0 addresses
Mon Aug 10 10:45:49 2020 daemon.info avahi-daemon[2979]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::1691:82ff:fe30:1ec9.
Mon Aug 10 10:45:49 2020 daemon.info avahi-daemon[2979]: New relevant interface eth0.IPv6 for mDNS.
Mon Aug 10 10:45:49 2020 daemon.info avahi-daemon[2979]: Registering new address record for fe80::1691:82ff:fe30:1ec9 on eth0.*.
Mon Aug 10 10:45:51 2020 daemon.notice netifd: wan (15404): udhcpc: sending discover
Mon Aug 10 10:45:54 2020 daemon.notice netifd: wan (15404): udhcpc: sending discover
Mon Aug 10 10:46:00 2020 daemon.err nmbd[3518]: [2020/08/10 10:46:00.970022,  0] ../../source3/libsmb/nmblib.c:916(send_udp)
Mon Aug 10 10:46:24 2020 daemon.info watchcat[3472]: no internet connectivity for 1080 seconds. Reseting when reaching 21600
^Croot@OpenWrt:~#

You still have avahi there, reacting to connectivity changes and causing log spam.

But stripping away the superflous spam, leaves this log, which shows a low-level link loss and re-connnection:

Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.637746] mvneta f1034000.ethernet eth0: Link is Down
...
Mon Aug 10 10:45:47 2020 daemon.notice netifd: VLAN 'eth0.1' link is down
Mon Aug 10 10:45:47 2020 daemon.notice netifd: bridge 'br-lan' link is down
Mon Aug 10 10:45:47 2020 daemon.notice netifd: Interface 'lan' has link connectivity loss
Mon Aug 10 10:45:47 2020 daemon.notice netifd: Network device 'eth0' link is down
...
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.779155] mvneta f1034000.ethernet eth0: configuring for fixed/sgmii link mode
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.786883] mvneta f1034000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.794891] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.803188] br-lan: port 1(eth0.1) entered blocking state
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.808661] br-lan: port 1(eth0.1) entered disabled state
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.814319] device eth0.1 entered promiscuous mode
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.819135] device eth0 entered promiscuous mode
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.825212] br-lan: port 1(eth0.1) entered blocking state
Mon Aug 10 10:45:47 2020 kern.info kernel: [ 1061.830648] br-lan: port 1(eth0.1) entered forwarding state

I have no special knowledge about "mvneta", but it could possibly be something like

  • faulty cable
  • repeated full/half duplex negotiation or sgmii mode things.

Something, where the low-level driver is unhappy with the link status.

I went and did a direct connection to modem and found that when disconected to coaxial a button appears to factory reset. Did this and my god that was a long 15mins of blinking lights not knowing if i broke the modem.
I let the modem sit for a bit with no coaxial, connected the Coaxial and waited a bit about 5 mins, connected the WAN to WAN on router that was off, waited a bit, turned on router and still nothing new.

So im gonna go and find some archived versions of OpenWRT (not david) and kinda work backwards, from the latest build and climb backwards in time. My thinking is that at some point I got this to work and at some point this wasnt an issue. https://openwrt.org/about/history

I dont thinks its the cables as they work fine for LInksys firmware, as for the sgmii mode, I have no idea about that to say the least..

I was wondering when a partition is installed over with a different version, does it clear that partition first? Im curios if there is like a random bit floating in the partition that isnt being wiped when i install from factory.

100% confused now
Slowly went backwards through the old versions of openwrt (Not david) and hit
Docsis 3 and cloned my Mac but nothing ever connected.
Went all the way to LEDE for 2017 and still same issue.

On a side note ddwrt just makes the lights flash like crazy and then restarts to Linksys.

My belief is that during the bad update something happened in both partitions that messed it up. I'm sure there is a way to 0 out a partition for a true fresh install but I'm unaware of that.

Back to Linksys
Any tips are welcomed

So one thing to try would be to keep the OpenWrt Mac address and power down the DOCSIS modem and OpenWrt router for say minutes and then power them up again.
In DOCSIS the modem will only listen to/accept new Mac addresses on its LAN side for a short duration after booting, and only if the modem has accepted your router will the rest of the wan side network function as expected.
But this is a wild guess and in all likelihood will not fix your real issues.

1 Like

Flashing OpenWrt twice without saving settings will remove all old images from the flash. That means flash an image, boot it up, and immediately "upgrade" with the same image, opt to not save settings. Then repeat.

While you are doing that, unplug the cable modem and leave it powered off for at least 30 minutes. Have the router configured and running when you start up the modem again.

tried this and wow the modem took a long time to get internet.
and no change However i did pull the config / firewall. Maybe something is wrong.
firewall

config defaults
        option syn_flood        1
        option input            ACCEPT
        option output           ACCEPT
        option forward          REJECT
# Uncomment this line to disable ipv6 rules
#       option disable_ipv6     1

config zone
        option name             lan
        list   network          'lan'
        option input            ACCEPT
        option output           ACCEPT
        option forward          ACCEPT

config zone
        option name             wan
        list   network          'wan'
        list   network          'wan6'
        option input            REJECT
        option output           ACCEPT
        option forward          REJECT
        option masq             1
        option mtu_fix          1

config forwarding
        option src              lan
        option dest             wan

# We need to accept udp packets on port 68,
# see https://dev.openwrt.org/ticket/4108
config rule
        option name             Allow-DHCP-Renew
        option src              wan
        option proto            udp
        option dest_port        68
        option target           ACCEPT
        option family           ipv4

# Allow IPv4 ping
config rule
        option name             Allow-Ping
        option src              wan
        option proto            icmp
        option icmp_type        echo-request
        option family           ipv4
        option target           ACCEPT

config rule
        option name             Allow-IGMP
        option src              wan
        option proto            igmp
        option family           ipv4
        option target           ACCEPT

# Allow DHCPv6 replies
# see https://dev.openwrt.org/ticket/10381
config rule
        option name             Allow-DHCPv6
        option src              wan
        option proto            udp
        option src_ip           fc00::/6
        option dest_ip          fc00::/6
        option dest_port        546
        option family           ipv6
        option target           ACCEPT

config rule
        option name             Allow-MLD
        option src              wan
        option proto            icmp
        option src_ip           fe80::/10
        list icmp_type          '130/0'
        list icmp_type          '131/0'
        list icmp_type          '132/0'
        list icmp_type          '143/0'
        option family           ipv6
        option target           ACCEPT

# Allow essential incoming IPv6 ICMP traffic
config rule
        option name             Allow-ICMPv6-Input
        option src              wan
        option proto    icmp
        list icmp_type          echo-request
        list icmp_type          echo-reply
        list icmp_type          destination-unreachable
        list icmp_type          packet-too-big
        list icmp_type          time-exceeded
        list icmp_type          bad-header
        list icmp_type          unknown-header-type
        list icmp_type          router-solicitation
        list icmp_type          neighbour-solicitation
        list icmp_type          router-advertisement
        list icmp_type          neighbour-advertisement
        option limit            1000/sec
        option family           ipv6
        option target           ACCEPT

# Allow essential forwarded IPv6 ICMP traffic
config rule
        option name             Allow-ICMPv6-Forward
        option src              wan
        option dest             *
        option proto            icmp
        list icmp_type          echo-request
        list icmp_type          echo-reply
        list icmp_type          destination-unreachable
        list icmp_type          packet-too-big
        list icmp_type          time-exceeded
        list icmp_type          bad-header
        list icmp_type          unknown-header-type
        option limit            1000/sec
        option family           ipv6
        option target           ACCEPT

config rule
        option name             Allow-IPSec-ESP
        option src              wan
        option dest             lan
        option proto            esp
        option target           ACCEPT

config ruleconfig rule
        option name             Allow-ISAKMP
        option src              wan
        option dest             lan
        option dest_port        500
        option proto            udp
        option target           ACCEPT

# include a file with users custom iptables rules
config include
        option path /etc/firewall.user


### EXAMPLE CONFIG SECTIONS
# do not allow a specific ip to access wan
#config rule
#       option src              lan
#       option src_ip   192.168.45.2
#       option dest             wan
#       option proto    tcp
#       option target   REJECT

# block a specific mac on wan
#config rule
#       option dest             wan
#       option src_mac  00:11:22:33:44:66
#       option target   REJECT

# block incoming ICMP traffic on a zone
#config rule
#       option src              lan
#       option proto    ICMP
#       option target   DROP

# port redirect port coming in on wan to lan
#config redirect
#       option src                      wan
#       option src_dport        80
#       option dest                     lan
#       option dest_ip          192.168.16.235
#       option dest_port        80
#       option proto            tcp

# port redirect of remapped ssh port (22001) on wan
#config redirect
#       option src              wan
#       option src_dport        22001
#       option dest             lan
#       option dest_port        22
#       option proto            tcp

### FULL CONFIG SECTIONS
#config rule
#       option src              lan
#       option src_ip   192.168.45.2
#       option src_mac  00:11:22:33:44:55
#       option src_port 80
#       option dest             wan
#       option dest_ip  194.25.2.129
#       option dest_port        120
#       option proto    tcp
#       option target   REJECT

#config redirect
#       option src              lan
#       option src_ip   192.168.45.2
#       option src_mac  00:11:22:33:44:55
#       option src_port         1024
#       option src_dport        80
#       option dest_ip  194.25.2.129
#       option dest_port        120
#       option proto    tcp
~
~
~

Config file


config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd6a:fe04:4cc4::/48'

config interface 'lan'
        option type 'bridge'
        option ifname 'eth0.1'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config interface 'wan'
        option ifname 'eth1.2'
        option proto 'dhcp'
        option macaddr 'xx:xx:xx:xx:xx:xx' 
        option broadcast '1'

config interface 'wan6'
        option ifname 'eth1.2'
        option proto 'dhcpv6'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '0 1 2 3 5t'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '4 6t'

Do you have Internet now?

That's a stock config other than forcing a MAC on the WAN, which should not be necessary.

sadly no
restarted the router and wasnt able to connect to internet.

Im thinking take the 2x install back to back and up that to 3 or 4, over write the partition A and B twice.

That should not be necessary.

Try a pure default configuration, do not set a MAC address or the broadcast flag.

1 Like

Still nothing sadly
I waited an hour with router booted and waiting, reconnected the power to the modem and waited for something to happen but no reconnection. Rebooted the router, and still no connection.

I'm wondering if this opewrtn, router, or modem/ISP that's causing this issue or if its me

Could it be a vlan issue ass that's on by default?
Or may a firewall issue.?

Test again with stock firmware. Running stock firmware is the best way to rule out a hardware issue.

i got it after what i would call is holding both resets (router and modem each have one). holding them one after another. This did something to Openwrt and i couldnt talk to it via lan at all and a network scan showed no router or modem. However, the modems GREEN light finally flickered, this told me the router and modem talk to each other but not me to them.
I then did the on off on off on off to the router and it worked. Now mind you both partitions are now DAVID's build but i got it to work.

Is there a long term log in the router that i can see what happened? Like why now? its later in the day then normal, did the ISP finally come threw?

I have so many questions on why this worked now.

I did wanna go to the default OPENWRT build due to security updates, but im not sure the risk

You could've set a logfile to usb or some permanent storage, but it doesn't by default as flash doesn't like write

Was afraid that was the answer, im gonna stay on the DAVID build in that case.

Spectrum doesn't actually know when their regional DHCP servers are down, therefore support will just have you reset things for hours until their DHCP server is noticed by someone and repaired (usually an hour and a half). They certainly won't admit it's their fault even when it is.

At least that's how my region drops out every month or two. Mine used to be Bresnan Cable which they bought and essentially plugged in with a cross-connect and left it that way for 20 years. Yay Spectrum!

Anyway I bet your DHCP server was down., or some other aspect of the cable service (downstream ranging failed, etc).

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.