LAN port temporarily goes down

Hi there,

I have a weird behavior on one of my LAN 2 port, where my PC is connected to.
The the port just is off and there LEDs are also not blinking anymore.

system log

Thu Jan 30 10:21:12 2025 daemon.notice hostapd: phy1-ap2: AP-STA-DISCONNECTED 10:6f:d9:2a:32:91
Thu Jan 30 10:21:12 2025 kern.info kernel: [325263.420406] ath10k_pci 0001:01:00.0: mac flush vdev 2 drop 0 queues 0x4 ar->paused: 0x0  arvif->paused: 0x0
Thu Jan 30 10:21:13 2025 daemon.notice netifd: Network device 'lan2' link is down
Thu Jan 30 10:21:13 2025 kern.info kernel: [325264.716942] br-lan: port 2(lan2) entered disabled state
Thu Jan 30 10:21:13 2025 kern.info kernel: [325264.717734] qca8k 37000000.mdio-mii:10 lan2: Link is Down
Thu Jan 30 10:21:19 2025 daemon.info hostapd: phy1-ap2: STA 10:6f:d9:2a:32:91 IEEE 802.11: associated (aid 1)
Thu Jan 30 10:21:19 2025 daemon.notice hostapd: phy1-ap2: AP-STA-CONNECTED 10:6f:d9:2a:32:91 auth_alg=sae
Thu Jan 30 10:21:19 2025 daemon.info hostapd: phy1-ap2: STA 10:6f:d9:2a:32:91 WPA: pairwise key handshake completed (RSN)
Thu Jan 30 10:21:19 2025 daemon.notice hostapd: phy1-ap2: EAPOL-4WAY-HS-COMPLETED 10:6f:d9:2a:32:91
Thu Jan 30 10:21:19 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.1) 192.168.1.193 10:6f:d9:2a:32:91
Thu Jan 30 10:21:19 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.1) 192.168.1.193 10:6f:d9:2a:32:91 manja
Thu Jan 30 10:21:22 2025 kern.info kernel: [325274.078768] qca8k 37000000.mdio-mii:10 lan2: Link is Up - 1Gbps/Full - flow control rx/tx
Thu Jan 30 10:21:22 2025 kern.info kernel: [325274.078842] br-lan: port 2(lan2) entered blocking state
Thu Jan 30 10:21:22 2025 kern.info kernel: [325274.086024] br-lan: port 2(lan2) entered forwarding state
Thu Jan 30 10:21:22 2025 daemon.notice netifd: Network device 'lan2' link is up

Hardware
Netgear R7800
Release
OpenWRT 24.10.0-rc6

In case you need other logs or similar, please let me know.

The other ports on the router are all connected and in use, but only lan2 has an issue.
The first time it happened, I had to restart the router to make it work again. It seems it also fixes itself sometimes, I didn't notice that it happened so many times.
on 29.01.2025 it happened four times and fixed itself.
today, 30.01.2025 it happened also four times, but on the fourth time it didn't come up, this was at

Thu Jan 30 12:01:17 2025 daemon.notice hostapd: phy1-ap2: AP-STA-DISCONNECTED 10:6f:d9:2a:32:91
Thu Jan 30 12:01:17 2025 kern.info kernel: [331268.387981] ath10k_pci 0001:01:00.0: mac flush vdev 2 drop 0 queues 0x4 ar->paused: 0x0  arvif->paused: 0x0
Thu Jan 30 12:01:18 2025 daemon.notice netifd: Network device 'lan2' link is down
Thu Jan 30 12:01:18 2025 kern.info kernel: [331269.644352] br-lan: port 2(lan2) entered disabled state
Thu Jan 30 12:01:18 2025 kern.info kernel: [331269.645246] qca8k 37000000.mdio-mii:10 lan2: Link is Down
Thu Jan 30 12:01:24 2025 daemon.info hostapd: phy1-ap2: STA 10:6f:d9:2a:32:91 IEEE 802.11: associated (aid 1)
Thu Jan 30 12:01:24 2025 daemon.notice hostapd: phy1-ap2: AP-STA-CONNECTED 10:6f:d9:2a:32:91 auth_alg=sae
Thu Jan 30 12:01:24 2025 daemon.info hostapd: phy1-ap2: STA 10:6f:d9:2a:32:91 WPA: pairwise key handshake completed (RSN)
Thu Jan 30 12:01:24 2025 daemon.notice hostapd: phy1-ap2: EAPOL-4WAY-HS-COMPLETED 10:6f:d9:2a:32:91
Thu Jan 30 12:01:25 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.1) 192.168.1.193 10:6f:d9:2a:32:91
Thu Jan 30 12:01:25 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.1) 192.168.1.193 10:6f:d9:2a:32:91 manja
Thu Jan 30 12:15:50 2025 daemon.info hostapd: phy0-ap2: STA 02:40:7e:e5:66:98 IEEE 802.11: associated (aid 2)

I will install release 24.10.0-rc7 and see what happens.

I checked the internet for the error message ath10k_pci 0001:01:00.0: mac flush vdev 2 drop 0 queues 0x4 ar->paused: 0x0 arvif->paused: 0x0 and there are a few entries, but nothing helps me understanding where it comes from and if I can fix it somehow :slight_smile:

At first i'd try to swap LAN2 and one of the others.
If this error stays on LAN2 it's the router, if not it's the cable or device connected to this cable.

I did change the port and the other ports were all working.
I was just thinking that it might be a bug, or is this connected to a defect port on the router that has issues from time to time?

It's possible that your router has got a hardware fault.
For me, it really looks so.

But it's not impossible that it is software related.
You could try the latest stable release (23.05.5) instead of the rc,
just to make sure there isn't a bug or regression in it.
And maybe share your

/etc/config/network

I will try to switch the port for my PC, maybe the NIC of my PC is the problem.
Currently port 2 has issues. If e.g. the port 3 also has the same issues, then I know it is my PCs NIC.

in case you see something fishy in my network config, I am happy about feedback :slight_smile:

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

config globals 'globals'
        option ula_prefix 'fdd8:1527:c5cd::/48'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'lan1'
        list ports 'lan2'
        list ports 'lan3'
        list ports 'lan4'

config interface 'lan'
        option device 'br-lan.1'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config interface 'wan'
        option device 'wan.7'
        option proto 'pppoe'
        option username ''
        option password ''
        option ipv6 'auto'
        option keepalive '0 1'

config device
        option type '8021q'
        option ifname 'wan'
        option vid '7'
        option name 'wan.7'

config device
        option name 'eth0'

config interface 'Management'
        option proto 'static'
        option device 'br-lan.10'
        option ipaddr '192.168.10.1'
        option netmask '255.255.255.0'

config interface 'DMZ'
        option proto 'static'
        option device 'br-lan.20'
        option ipaddr '192.168.20.1'
        option netmask '255.255.255.0'

config interface 'Arbeit'
        option proto 'static'
        option device 'br-lan.40'
        option ipaddr '192.168.40.1'
        option netmask '255.255.255.0'

config interface 'IoT'
        option proto 'static'
        option device 'br-lan.30'
        option ipaddr '192.168.30.1'
        option netmask '255.255.255.0'

config bridge-vlan
        option device 'br-lan'
        option vlan '1'
        list ports 'lan1:t'
        list ports 'lan2:u*'

config bridge-vlan
        option device 'br-lan'
        option vlan '10'
        list ports 'lan1:t'

config bridge-vlan
        option device 'br-lan'
        option vlan '20'
        list ports 'lan1:t'

config bridge-vlan
        option device 'br-lan'
        option vlan '30'
        list ports 'lan1:t'
        list ports 'lan3:u*'
        list ports 'lan4:u*'

config bridge-vlan
        option device 'br-lan'
        option vlan '40'
        list ports 'lan1:t'

config bridge-vlan
        option device 'br-lan'
        option vlan '50'
        list ports 'lan1:t'

config bridge-vlan
        option device 'br-lan'
        option vlan '60'
        list ports 'lan1:t'

What device is this?

That is the wifi of my PC. I have it also activated.
LAN is static and wifi has DHCP

Hmmmm.

So your PC is connecting with WiFi and ethernet and you are wondering why you may have conflicts...

Please shut off the WiFi.

1 Like

hmm, seems I had a bug in my head. Thank you for the feedback. I thought wifi is just a backup and only gets active when LAN is not available, but I think this was a mistake.

1 Like

It will connect to both and, depending on the OS, decide which route it wants to take where or it may pick one over the other.

My prima facie thought, given that device triggers the drop, was either this or

(which I know the definition of) was, trolling you and, 'cutting' your connection because your WiFi network had been compromised.

1 Like

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