The r8125 plug-in was added to the 21.02 version. It was selected during compilation. However, after installation, it was found that the 8125b network card could only work at 1000M, and could not negotiate to 2500M. Manual modification would not work! How can I solve it?
Both connected devices are 8125b network cards！
I need mwan3 very much, but at present, mwan3 does not work well in 22.03!
.3 just got released, might be worth checking.
The reason why mwan3 does not work properly is that it uses iptables, which cannot be fully adapted to the nftables in 22.03, unless mwan3 uses nftables!
did you try to force autonegotiation with ethool?
ethtool -s eth(*) autoneg on advertise 0x80000000002f
Still test 22.03, even if you don't want to use it long term, just to check/ confirm if it's working in the newer kernel. Once you know the answer to that, you can either:
- backport the r8152 kernel changes between v5.4 and v5.10 fixing this
- or use fw3/ iptables instead of fw4/ nftables on 22.03
Neither will be particularly fun, but one of those options is the only possible way.
After upgrading the 22.03 system, 1G is also automatically negotiated, and 2.5G is successfully negotiated after passing the command you gave. What is the reason for this?
Why doesn't the interface auto-negotiate to 2.5G, only 1G? Do I need to modify anything when building?
After using 22.03, it is still the same, and it can only auto advertise to 1G. Command modification required!
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Port: Twisted Pair
Supports Wake-on: pumbg
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: yes