I’m getting these frequent up/downs on my link connecting to the pc with rj45 cat5e cable. I tested the cable with a tester and it is ok. The drivers of the lan card are updated to the latest release. It happens on Windows and LInux too. I have not enabled software/hw offloading. I’m on 23.05 xiaomi 3200 (MediaTek MT7622 SoC and MT7531 switch i think). I tired a Wifi pcie card and another old 100MB pci card and they seem ok.
I tested the pcie lan card on x1,x4,x16 slots, doesn’t seem to matter much, though it was more stable on the x16 slot for few days but the issue started again. Sometimes when it reconnects it switches to 100MB link
Also tried this on the lan adapter settings, same issue
Speed & Duplex → 1.0 Gbps Full Duplex
Green Ethernet → Disabled
Energy-Efficient Ethernet → Disabled
Flow Control → Disabled
Is this a problem of the chip or the router os?
p.s the syncthing thing in the logs is just synchronization of files between 2 pcs in the lan
Most likely it is a cabling problem, gigE card should be fine in x1 interface.
What is at the other end of cable?
Please use the "Preformatted text </>" button for logs, scripts, configs and general console output (red circle; this works best in the 'Markdown' composer view in the blue oval):
23.05.x has been EOL for a while, there's 24.10.x and almost 25.12.x, both upgrading the kernel and r8168 significantly. Even if there were an issue in 23.05.x, it won't be fixed anymore - and without at least trying 25.12.0-rc5, you won't know how the cookie crumbles anyways.
The cable is not even 1m long, the router port is connected directly with the pcie lan card through it. I tried 2 other cables and got the same things, it works ok for hours that suddenly start having issues for 5 minutes, then works ok for a couple of more hours
Mon Feb 23 15:13:43 2026 daemon.notice netifd: Network device 'lan1' link is down
Mon Feb 23 15:13:43 2026 kern.info kernel: [1729197.325096] br-lan: port 1(lan1) entered disabled state
Mon Feb 23 15:13:43 2026 kern.info kernel: [1729197.325183] mt7530-mdio mdio-bus:00 lan1: Link is Down
Mon Feb 23 15:13:45 2026 kern.info kernel: [1729199.755597] mt7530-mdio mdio-bus:00 lan1: Link is Up - 1Gbps/Full - flow control off
Mon Feb 23 15:13:45 2026 kern.info kernel: [1729199.755735] br-lan: port 1(lan1) entered blocking state
Mon Feb 23 15:13:45 2026 kern.info kernel: [1729199.768983] br-lan: port 1(lan1) entered forwarding state
Mon Feb 23 15:13:45 2026 daemon.notice netifd: Network device 'lan1' link is up
Mon Feb 23 15:13:46 2026 kern.info kernel: [1729200.597172] br-lan: port 1(lan1) entered disabled state
Mon Feb 23 15:13:46 2026 kern.info kernel: [1729200.597270] mt7530-mdio mdio-bus:00 lan1: Link is Down
Mon Feb 23 15:13:46 2026 daemon.notice netifd: Network device 'lan1' link is down
Mon Feb 23 15:14:03 2026 kern.info kernel: [1729218.033653] mt7530-mdio mdio-bus:00 lan1: Link is Up - 100Mbps/Full - flow control off
Mon Feb 23 15:14:03 2026 kern.info kernel: [1729218.034375] br-lan: port 1(lan1) entered blocking state
Mon Feb 23 15:14:03 2026 daemon.notice netifd: Network device 'lan1' link is up
Mon Feb 23 15:14:03 2026 kern.info kernel: [1729218.047217] br-lan: port 1(lan1) entered forwarding state
after the link goes down/up for a couple of time it tends to default to 100mbps and then it seems is mare stable after that
You can permit empty bridge via luci so that bridge link does not go up and down with last cable.
Boot 25.10.0-rc5 from USB and check if the problem persists. It is fairly possible that somebody noticed same problem in upstream kernel and fixed it without much fanfare.
