Andrew

Identify different phy-s just that one line on top of ethtool provided info: ``` mii-tool eth0 -v ... product info: vendor 00:07:32, model 0 rev 0 ... ``` Type for...

Only "product info" line is important because it is not shown by ethtool. You dont have to connect anything to flaky port.

To have non-destructive cable replug create br-wan with those 2 ports, just take care to not loop them eg by not connecting both at once, and bring the dhcp "wan"...

Asus AX53U `product info: vendor 00:e8:a5, model 1 rev 2` same type on both dsa and wan ports, works flawlessly

Phy type with mii-tool -v ethtool report of negotiation - enough to confirm best speed is agreed if fixing ethtool -s advertise to 1g fdx helps wild errors in ethtool...

Gigabit is always duplex, mii-tool is just to read phy type. What phy type is on lan ports? EDIT: indeed if it is different it will behave differently at the...

You said ~1min to go down, which sounds kind of powersave. Lets wait a bit , say 1h stable. If the problem is properly identified certainly ;-) It is about...

You can add command in /etc/rc.local before exit 0 line ?particular phy? breaks when post-eee it gets 10baseT signal. ping @nbd168

You can formally try to disable eee, though seems dependent on ethtool support https://git.openwrt.org/?p=project/netifd.git;a=commitdiff;h=eee02ccca8c8ba2540108e6a5cff10888bb337c9

1/ identify device and OpenWRT version (as seen in `ubus call system board`) 2/ mii-tool -v lan5 (the phy identifiiers) 3/ ethtool lan5 / ethtool --show-eee lan5 (the link modes)...