Flint 2 drop lan connection or reconnect with slower speed

Hi,

I have GL-MT6000 with stable firmware 4.7.4 (2025-03-28). No custom settings, no VPN, no attempt to change firmware to direct openwrt (considering it, actually).
No port forwarding. Nothing changed in Luci UI.
Network acceleration - OFF
Drop-in mode - OFF
NAT settings - both OFF

  • Model
    GL.iNet GL-MT6000
  • Architecture
    ARMv8 Processor rev 4
  • OpenWrt Version
    OpenWrt 21.02-SNAPSHOT r15812+1084-46b6ee7ffc
  • Kernel Version
    5.4.238

My all cables are Cat6.
WAN has a 1gb(1000mbps) fiber as input - no problem.
lan2 has direct connection to linux pc - no problem, always keeps 1gb.
lan3 has direct connection to raspberry pi (linux) - no problem, always keeps 1gb.

lan1 (also tried with lan4) has direct connection to tp-link 1gb unmanaged switch TP-Link TL-SG108. And here is the problem. It loose connection at all (happened once) OR loose connection and reconnect at decreased speed - 100mbps. From kernel logs it looks just like it drops - and then recover, without any explicit noticeable info.
When the link is lost - I unplug cable(which connect router and switch) from SWITCH and plug it back. It takes few seconds to go up again. Sometimes it goes directly to 100mbps instead of 1gb.
On reboot of router - it all starts ok - with 1gb connection.

I try to keep track on the logs to catch exact moment of disconnect and will update topic.
Should I go to newer firmware (where is the newer kernel and possible solution for this problem) ?
I might consider to buy new unmanaged switch, but it was working fine with my old router, so not sure if that is the problem.

Thanks.

Got a bit of logs, but nothing suspicious, it seems.
Before it starts to endless reconnect(not working). It does some wifi negotiation and udhcpc renew. Any hints?

Mon Apr 21 13:47:22 2025 kern.notice kernel: [64684.445309] 7986@C08L3,hw_ctrl_flow_v2_connt_act() 215: wdev_idx=0
Mon Apr 21 13:47:22 2025 kern.notice kernel: [64684.576689] 7986@C15L3,WPABuildPairMsg1() 5310: <=== send Msg1 of 4-way
Mon Apr 21 13:47:22 2025 kern.notice kernel: [64684.748615] 7986@C15L3,PeerPairMsg2Action() 6303: ===>Receive msg 2
Mon Apr 21 13:47:22 2025 kern.notice kernel: [64684.755211] 7986@C15L3,WPABuildPairMsg3() 5595: <=== send Msg3 of 4-way
Mon Apr 21 13:47:22 2025 kern.notice kernel: [64684.761829] 7986@C15L3,PeerPairMsg4Action() 6734: ===>Receive msg 4
Mon Apr 21 13:47:22 2025 kern.warn kernel: [64684.773323] 7986@C15L2,PeerPairMsg4Action() 7098: AP SETKEYS DONE(ra0) - AKMMap=WPA2PSK, PairwiseCipher=AES, GroupCipher=AES, wcid=10 from 9a:50:6e:ed:<>
Mon Apr 21 13:47:22 2025 kern.warn kernel: [64684.773323]
Mon Apr 21 13:49:44 2025 daemon.notice netifd: wan (8666): udhcpc: sending renew to 207.188.<>
Mon Apr 21 13:49:44 2025 daemon.notice netifd: wan (8666): udhcpc: lease of 207.188.<> obtained, lease time 7200
Mon Apr 21 13:50:29 2025 daemon.info dnsmasq-dhcp[6851]: DHCPREQUEST(br-lan) 192.168.1.48 76:34:cd:6b:<>
Mon Apr 21 13:50:29 2025 daemon.info dnsmasq-dhcp[6851]: DHCPACK(br-lan) 192.168.1.48 76:34:cd:6b:<>
<<
<<< HERE SOMETHING HAPPENED
<<
Mon Apr 21 13:50:34 2025 kern.info kernel: [64876.526721] mt7530 mdio-bus:1f lan4: Link is Down
Mon Apr 21 13:50:34 2025 kern.info kernel: [64876.531568] br-lan: port 4(lan4) entered disabled state
Mon Apr 21 13:50:34 2025 daemon.notice netifd: Network device 'lan4' link is down
Mon Apr 21 13:50:46 2025 kern.info kernel: [64888.815177] mt7530 mdio-bus:1f lan4: Link is Up - 100Mbps/Full - flow control rx/tx
Mon Apr 21 13:50:46 2025 kern.info kernel: [64888.822862] br-lan: port 4(lan4) entered blocking state
Mon Apr 21 13:50:46 2025 kern.info kernel: [64888.828089] br-lan: port 4(lan4) entered forwarding state
Mon Apr 21 13:50:46 2025 daemon.notice netifd: Network device 'lan4' link is up
Mon Apr 21 13:50:47 2025 kern.info kernel: [64889.838584] mt7530 mdio-bus:1f lan4: Link is Down
Mon Apr 21 13:50:47 2025 kern.info kernel: [64889.843450] br-lan: port 4(lan4) entered disabled state
Mon Apr 21 13:50:47 2025 daemon.notice netifd: Network device 'lan4' link is down
Mon Apr 21 13:50:53 2025 kern.info kernel: [64895.983088] mt7530 mdio-bus:1f lan4: Link is Up - 100Mbps/Full - flow control rx/tx
Mon Apr 21 13:50:53 2025 kern.info kernel: [64895.990773] br-lan: port 4(lan4) entered blocking state
Mon Apr 21 13:50:53 2025 kern.info kernel: [64895.995999] br-lan: port 4(lan4) entered forwarding state
Mon Apr 21 13:50:53 2025 daemon.notice netifd: Network device 'lan4' link is up
Mon Apr 21 13:50:55 2025 kern.info kernel: [64897.006477] mt7530 mdio-bus:1f lan4: Link is Down
Mon Apr 21 13:50:55 2025 kern.info kernel: [64897.011325] br-lan: port 4(lan4) entered disabled state
Mon Apr 21 13:50:55 2025 daemon.notice netifd: Network device 'lan4' link is down
Mon Apr 21 13:51:20 2025 kern.info kernel: [64922.606782] mt7530 mdio-bus:1f lan4: Link is Up - 100Mbps/Full - flow control rx/tx
Mon Apr 21 13:51:20 2025 kern.info kernel: [64922.614507] br-lan: port 4(lan4) entered blocking state
Mon Apr 21 13:51:20 2025 kern.info kernel: [64922.619736] br-lan: port 4(lan4) entered forwarding state
Mon Apr 21 13:51:20 2025 daemon.notice netifd: Network device 'lan4' link is up
Mon Apr 21 13:51:21 2025 kern.info kernel: [64923.630170] mt7530 mdio-bus:1f lan4: Link is Down
....
endless up->down

Hello,

It is speculated that the network port speed negotiation compatibility may not be very good.

You can try the following command on SSH to fix 1Gbps for LAN4:

ethtool -s lan4 speed 1000 duplex full autoneg off

Unfortunately it didn't help.
I'm on latest stable 4.7.7 now. And applied those ethtool autoneg off command from above.
There is no obvious logic in when in happens, it can work for days untill it goes down, sometimes at night when laptop is sleeping or during work hours when there are a lot of traffic.
But Im wondering if the switch could be a problem. My scheme is like this:

Internet ---> (WAN) Flint 2 --> LAN4 -> cat 6 cable --> RJ45 socket --> cat6 cable --> Switch TP-Link TL-SG108

Log:
Mon May 5 07:34:04 2025 kern.info kernel: [229527.098555] mt7530 mdio-bus:1f lan4: Link is Up - 1Gbps/Full - flow control rx/tx
Mon May 5 07:34:04 2025 kern.info kernel: [229527.106154] br-lan: port 4(lan4) entered blocking state
Mon May 5 07:34:04 2025 kern.info kernel: [229527.111467] br-lan: port 4(lan4) entered forwarding state
Mon May 5 07:34:04 2025 daemon.notice netifd: Network device 'lan4' link is up
Mon May 5 07:37:13 2025 daemon.notice netifd: Network device 'lan4' link is down
Mon May 5 07:37:13 2025 kern.info kernel: [229716.535730] br-lan: port 4(lan4) entered disabled state
Mon May 5 07:37:13 2025 kern.info kernel: [229716.541202] mt7530 mdio-bus:1f lan4: Link is Down
Mon May 5 07:43:14 2025 kern.err kernel: [230077.710366] 7986@C11L1,header_packet_process() 7261: header_packet_process(): CheckRxError!
Mon May 5 07:43:14 2025 kern.err kernel: [230077.718808] 7986@C11L1,header_packet_process() 7261: header_packet_process(): CheckRxError!