Lan keeps disconnecting

Installing and Using OpenWrt
1

Hi, I recently noticed a sudden and repeated drop in my internet connection, at first I suspected it was an ISP issue, but after I checked my openwrt logs I noticed the LAN keeps losing connectivity with no clear reason with the blow errors repeating every 15/30 mins or so

r8169 0000:01:00.0 eth1: Link is Down
r8169 0000:01:00.0 eth1: Link is Up - 1Gbps/Full - flow control off

I suspected a faulty ethernet cable but my cable tester showed It's fine but I replaced it anyway and still the same issue.

my second suspicion was a faulty nic, so I swapped the Wan with the LAN, and still the LAN kept disconnecting, and the Wan had no issues. does anyone know how to debug/approach this issue as the logs do not show any errors.

below is my interface and firewall configuration

docker0   Link encap:Ethernet  HWaddr 02:42:97:92:82:00
          inet addr:172.17.0.1  Bcast:172.17.255.255  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

eth0      Link encap:Ethernet  HWaddr 00:18:71:82:8F:CB
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::218:71ff:fe82:8fcb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:664319 errors:0 dropped:0 overruns:0 frame:0
          TX packets:318184 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000

eth1      Link encap:Ethernet  HWaddr D8:47:32:A3:29:05
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:327535 errors:0 dropped:0 overruns:0 frame:0
          TX packets:667619 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:860 errors:0 dropped:0 overruns:0 frame:0
          TX packets:860 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000

config defaults
	option input 'ACCEPT'
	option output 'ACCEPT'
	option forward 'REJECT'
	option synflood_protect '1'

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

config include 'openclash'
	option type 'script'
	option path '/var/etc/openclash.include'

config zone
	option name 'wan'
	option input 'REJECT'
	option output 'ACCEPT'
	option forward 'REJECT'
	option family 'ipv4'
	option masq '1'
	option mtu_fix '1'
	list network 'wan'
	list device 'eth0'

config forwarding
	option src 'lan'
	option dest 'wan'

config zone 'docker'
	option input 'ACCEPT'
	option output 'ACCEPT'
	option forward 'ACCEPT'
	option name 'docker'
	list network 'docker'
2

What is at other end of cable?

3

Please show this:

ethtool -a eth1
ethtool eth1
ethtool --show-eee eth1
4

sorry I forgot to mention It,
it's connected to a Huwai AP. I also verified it's not the issue

below are the info from ethtool

Pause parameters for eth1:
Autonegotiate:  on
RX:             off
TX:             off
RX negotiated: off
TX negotiated: off

Settings for eth1:
        Supported ports: [ TP    MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Half 1000baseT/Full
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: on
        master-slave cfg: preferred slave
        master-slave status: slave
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: external
        MDI-X: Unknown
        Supports Wake-on: pumbg
        Wake-on: d
        Link detected: yes

EEE settings for eth1:
        EEE status: enabled - inactive
        Tx LPI: disabled
        Supported EEE link modes:  100baseT/Full
                                   1000baseT/Full
        Advertised EEE link modes:  100baseT/Full
                                    1000baseT/Full
        Link partner advertised EEE link modes:  Not reported
5

Do you need additional gudance to:
A - disable EEE
B - disable negotiated modes that do not match eee
In either case wait 1-2h if link flops or not.
Opponent is a black box, probably "not a problem" is the flos you see and worry about.