WAN Drops -- Please Help!

SO FRUSTRATED! Been learning and working on setting up my very first OpenWRT router for days now. I'm not an idiot, but also not a networking expert. I've successfully flashed my Netgear WNDR3800 (old, I know) to OpenWRT v23.05.0. I've been making progress on setting up a USB thumb drive plugged into the router to share on my LAN via SMB. All is going fairly well, EXCEPT FOR THE INTERNET [WAN] CONNECTION!

I've connected the WAN port of my router to my cable modem ethernet port. I know my cable modem and my ISP connection/service are working just fine because when plugged into my old router via the same exact cable all is fine. So after a bit of a wait, my OpenWRT router finally establishes a WAN connection to my ISP and serves internet access to devices on my LAN. But after 5 or so minutes max, the WAN connection is severed and my router and LAN clients have NO internet access. This is driving my insane! Do I have a bad router? Is something wrong with my OpenWRT configuration? Is my ISP dropping the DHCP WAN connection after a bit? I just want to get this thing working and move on to other stuff! Any help?

PS: Don't know how to upload System Log to my post here.

You can upgrade to 23.05.3 https://firmware-selector.openwrt.org/

Log is in Luci -> Status -> System log -> Scroll to end

If should say something about netifd, dhcp, wan etc.

(or if you prefer SSH just say so, it is easier to diagnose then.

Thx @brada4 .

OK, I will upgrade to v23.05.3 and re-test.

I know how to locate and copy the text of the log from LuCI. I just don't know how to properly upload it here for others' viewing.

In principle you copy from ssh (like putty client), command logread.
In principle lan side clients get internet once openwrt starts like until next upgrade.

Upgraded to OpenWRT v23.05.3. WAN connection was a bit more stable for a bit longer -- I was hopeful! But then it all came crashing down again. I could tell things were still not quite right as my internet radio would cut out every once and a while; and then eventually went out completely.

The WAN interfaces "seem" to still have a connection:

But there is effectively NO internet access for LAN clients. I see packet loss with ping:

PING cnn.com (151.101.195.5): 56 data bytes
64 bytes from 151.101.195.5: seq=0 ttl=58 time=15.287 ms
64 bytes from 151.101.195.5: seq=1 ttl=58 time=16.990 ms
64 bytes from 151.101.195.5: seq=2 ttl=58 time=16.153 ms

--- cnn.com ping statistics ---
5 packets transmitted, 3 packets received, 40% packet loss
round-trip min/avg/max = 15.287/16.143/16.990 ms

WHY IS MY OPENWRT ROUTER NOT ABLE TO MAINTAIN A WIRED WAN CONNECTION?

Interesting update: I've set up a WWAN {Wireless WAN] connection on my OpenWRT router, so it now gets it's WAN [internet] via the 2.4 GHz Wi-Fi radio. With this configuration, the WAN [internet] is STABLE [so far] for LAN cients! WTF? So the WIRED WAN port on my router is faulty?

It could be. Or a faulty cable. Or a faulty port on the other side. Or, it could also be an issue where the ports don't negotiate the link properly. It's hard to say without looking at logs.

For now, the best thing to do is to inspect the wan port for any debris, bent pins, or anything else in the port that could cause problems. Also replace the cable with a known good one (ideally short)... don't assume you have a good cable just because it is new and/or worked with previous equipment.

Sometimes helps to reverse cable

What do you mean reverse the cable?

If one of involved connectors is worn off then plugging it to different socket may help.

Better is to replace the cable entirely.

Like if shop opens only monday thats best to be done while at home. Yes, ultimately to replace.

I am having a similar issue here - flashed to OpenWRT, and it loses WAN access (though much less frequently).

Tested my ethernet cable with a hardware CAT5/6 tester, it's good.

Here is the issue:

  • Router boots up fine
  • Wifi and LAN connections are good
  • Every hour or two, internet goes out, and (according to log) OpenWRT boots Wifi LAN clients. Everything is at default, except for some firewall rules that seem to be configed even after flashing. I don't see anythign useful in the logs.

Here is recent log:

Wed May 15 09:23:03 2024 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED[MAC ADDRESS REDACTED BY USER]
Wed May 15 09:23:03 2024 daemon.info hostapd: phy1-ap0: STA [MAC ADDRESS REDACTED BY USER] IEEE 802.11: authenticated
Wed May 15 09:23:03 2024 daemon.info hostapd: phy1-ap0: STA [MAC ADDRESS REDACTED BY USER] IEEE 802.11: associated (aid 1)
Wed May 15 09:23:03 2024 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED [MAC ADDRESS REDACTED BY USER] auth_alg=open
Wed May 15 09:23:03 2024 daemon.info hostapd: phy1-ap0: STA [MAC ADDRESS REDACTED BY USER] WPA: pairwise key handshake completed (RSN)
Wed May 15 09:23:03 2024 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED [MAC ADDRESS REDACTED BY USER]
Wed May 15 09:23:30 2024 daemon.info hostapd: phy0-ap0: STA [MAC ADDRESS REDACTED BY USER] IEEE 802.11: authenticated
Wed May 15 09:23:30 2024 daemon.info hostapd: phy0-ap0: STA [MAC ADDRESS REDACTED BY USER] IEEE 802.11: associated (aid 3)
Wed May 15 09:23:30 2024 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED[MAC ADDRESS REDACTED BY USER] auth_alg=open
Wed May 15 09:23:30 2024 daemon.info hostapd: phy0-ap0: STA [MAC ADDRESS REDACTED BY USER] WPA: pairwise key handshake completed (RSN)
Wed May 15 09:23:30 2024 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED be:f7:94:37:89:f3
Wed May 15 09:23:31 2024 daemon.warn odhcpd[1703]: No default route present, overriding ra_lifetime!
Wed May 15 09:25:24 2024 daemon.warn odhcpd[1703]: No default route present, overriding ra_lifetime!
Wed May 15 09:32:45 2024 daemon.warn odhcpd[1703]: No default route present, overriding ra_lifetime!
Wed May 15 09:39:31 2024 daemon.warn odhcpd[1703]: No default route present, overriding ra_lifetime!
Wed May 15 09:39:52 2024 daemon.warn odhcpd[1703]: No default route present, overriding ra_lifetime!
Wed May 15 09:41:41 2024 daemon.notice netifd: wan (2709): udhcpc: sending renew to server 192.168.68.1
Wed May 15 09:41:41 2024 daemon.notice netifd: wan (2709): udhcpc: lease of 192.168.68.103 obtained from 192.168.68.1, lease time 7200
Wed May 15 09:43:38 2024 daemon.warn odhcpd[1703]: No default route present, overriding ra_lifetime!
Wed May 15 09:49:46 2024 daemon.warn odhcpd[1703]: No default route present, overriding ra_lifetime!
Wed May 15 09:54:47 2024 daemon.warn odhcpd[1703]: No default route present, overriding ra_lifetime!
Wed May 15 10:00:21 2024 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED [MAC ADDRESS REDACTED BY USER]
Wed May 15 10:00:21 2024 daemon.info hostapd: phy0-ap0: STA [MAC ADDRESS REDACTED BY USER] IEEE 802.11: disassociated
Wed May 15 10:00:22 2024 daemon.info hostapd: phy0-ap0: STA [MAC ADDRESS REDACTED BY USER]: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed May 15 10:01:07 2024 daemon.warn odhcpd[1703]: No default route present, overriding ra_lifetime!
Wed May 15 10:01:42 2024 daemon.err uhttpd[2125]: [info] luci: accepted login on / for root from 192.168.1.100
Wed May 15 10:09:22 2024 daemon.warn odhcpd[1703]: No default route present, overriding ra_lifetime!

Much less frequently than what?

How do you determine WAN is out if your AP kicked the clients?

Are you testing the client via Ethernet?

Much less frequently than what?

Than the OP's issue. My WAN drops out for about 1 minute or so every few hours

I am evaluating the WAN drop based on LAN (wired) connection. My WiFi is fine.

Yup!

1 Like