Redmi AC2100 DSA and cable modem -> no DHCP answer?

Installing and Using OpenWrt Network and Wireless Configuration
21

Install ethtool. Run ethtool -S wan to read the hardware statistics. Are there any RxDropped, RxFiltering, or any type of Errs?

22

no, there is nothing to see, when I connect the modem back directly and run ifup wan

Thu Aug 26 18:46:58 2021 daemon.notice netifd: Network device 'wan' link is down
Thu Aug 26 18:46:58 2021 daemon.notice netifd: Interface 'wan' has link connectivity loss
Thu Aug 26 18:46:58 2021 daemon.notice netifd: Interface 'wan' is now down
Thu Aug 26 18:46:58 2021 daemon.notice netifd: Interface 'wan' is disabled
Thu Aug 26 18:46:58 2021 kern.info kernel: [ 1854.468189] mt7530 mdio-bus:1f wan: configuring for phy/gmii link mode
Thu Aug 26 18:46:58 2021 kern.info kernel: [ 1854.475360] 8021q: adding VLAN 0 to HW filter on device wan
Thu Aug 26 18:46:58 2021 daemon.notice netifd: Interface 'wan' is enabled
root@gw:~# ethtool -S wan | grep -e RxD -e RxF -e Err
     TxCrcErr: 0
     RxDrop: 0
     RxFiltering: 0
     RxAlignErr: 0
     RxCrcErr: 0
     RxUnderSizeErr: 0
     RxFragErr: 0
     RxOverSzErr: 0
     RxJabberErr: 0
23

hi, again some good NEWS... after reading a little in the dsa docs I have seen, that the driver can implement the EEE powersaving function for ethtool. So I was thinking give it a try and disable it:

before:

root@gw:~# ethtool --show-eee wan
EEE Settings for wan:
        EEE status: enabled - active
        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:  100baseT/Full
                                                 1000baseT/Full

then I was running ethtool --set-eee wan eee off and connected the router directly to the modem and restarted again the interface - and I got an IP :slight_smile:

root@gw:~# ethtool --show-eee wan
EEE Settings for wan:
        EEE status: disabled
        Tx LPI: disabled
        Supported EEE link modes:  100baseT/Full 
                                   1000baseT/Full 
        Advertised EEE link modes:  Not reported
        Link partner advertised EEE link modes:  Not reported

I added the ethtool --set-eee ... line to my rc.local and rebooted - this also works

should I report this as an bug to openwrt?

1 Like
24

What does --show-eee show when it does not work?

26

I check it when I come home :slight_smile:

27

ok, thats the output after a reboot (without the rc.local change) when the modem is directly connected:

root@gw:~# ethtool --show-eee wan
EEE Settings for wan:
	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
28

So EEE is enabled but inactive.

29

Today I updated from rc4 to release and came to the point, where I had again no internet after the upgrade.

Thats really bad, I had to run again to find my switch to plug them between.

Is there also a other way to disable EEE on boot without the ethtool?

Or maybe it can be fixed in next release? Looks like the detection is faulty... before with 19.07 it was working without a switch.....

30

Today I updated to 21.02.1 - but the problem is still present... I updated my workaround in my /etc/rc.local to:

if ! test -e /usr/sbin/ethtool
then
  wget http://my-internal-host/mypath/ethtool -O /usr/sbin/ethtool
  chmod +x /usr/sbin/ethtool
fi

ethtool --set-eee wan eee off

and copied the ethtool from my router to my-internal-host. So I can survive a firmware update, without a lost internet connection.

Just want to add, that I have reported this at https://bugs.openwrt.org/index.php?do=details&task_id=4127