WAX206 - Speed on WAN port goes done to 10Mbit after 10 days of operation

Hi,

I uses WAX206 devices as dump APs and the WAN Port as uplink to the router. Before the WAX206 I used Netgear R7800 as APs. The router is a ZyXEL NBG6817. I facing with my both WAX206 that after weeks there is an error in the kernel log that the speed switches down to 10Mbit on WAN port. I never saw that with my R7800 and also have that with 2 WAX206.

Could this a software issue as it happens with both of my WAX206. If I reconnect the cable speed is back to 1Gbit. Why does the WAX206 negotiate automatically to the higher rate again?

[296544.976707] mt7530-mdio mdio-bus:00: port 3 failed to delete b0:a4:60:3d:1c:83 vid 1 from fdb: -2
[296544.986057] mt7530-mdio mdio-bus:00: port 4 failed to delete b0:a4:60:3d:1c:83 vid 1 from fdb: -2
[296544.995090] mt7530-mdio mdio-bus:00: port 4 failed to delete b0:a4:60:3d:1c:83 vid 1 from fdb: -2
[296545.004048] mt7530-mdio mdio-bus:00: port 5 failed to delete b0:a4:60:3d:1c:83 vid 1 from fdb: -2
[296545.013297] mt7530-mdio mdio-bus:00: port 5 failed to delete b0:a4:60:3d:1c:83 vid 1 from fdb: -2
[328805.307243] mt7530-mdio mdio-bus:00 lan4: Link is Down
[328807.778713] mt7530-mdio mdio-bus:00 lan4: Link is Up - 1Gbps/Full - flow control rx/tx
[370969.468687] mt7530-mdio mdio-bus:00 wan: Link is Down
[427517.167284] mt7530-mdio mdio-bus:00 lan4: Link is Down
[427517.172884] br-lan: port 4(lan4) entered disabled state
[500230.977370] mt7530-mdio mdio-bus:00 wan: Link is Down
[500230.982857] br-lan: port 5(wan) entered disabled state
[500250.737337] RTL8221B-VB-CG 2.5Gbps PHY mdio-bus:07: Downshift occurred from negotiated speed 1Gbps to actual speed 10Mbps, check cabling!
[500250.750634] mt7530-mdio mdio-bus:00 wan: Link is Up - 10Mbps/Full - flow control rx/tx

Cheers,
Nils

Did you test with another cable as the message suggests?

Anything is possible at this point, you will need to try debugging this further. If both WAX206 are not sharing (any) cable segment, I wouldn't suppose this to be an issue (but if you can replace the cable easily, that would be an easy confirmation). Another this you could try, would be putting an unmanaged switch just in front of the wax206, as this would bring two changes to your test, a) you'd get a short patch cable between wax206 and switch, so a known-good/ different cable and b) you'd break the immediate communication between the qca8337 switch chipset in the nbg6817 and the mt7531ae switch chipset of your wax206, using a different mediator (the unmanaged switch) instead.

Beyond that, can you identify anything that coincides with those speed changes?

--
If both wax206 show the same issue, concentrate your testing on one of them - keep the other as-is, as a kind of control group.

1 Like

Does this happen on both APs at the same time? In that case, I would start looking into the main router (even if this did not happen with other APs).

I have 4 of these configured as access points. The 2.5G (Wan) port is slow on all of them so I am forced to use one of the 1G ports to get useful speed. My guess is that it’s caused by the cheap managed switches I use (TP-LINK TL-SG108E V3). And these switches don’t support more than 1G anyway.

Which version of Openwrt are you using?
I'm on: OpenWrt SNAPSHOT, r25239-a3a33f02ce

@hecatae The actual stable: OpenWrt 23.05.2 r23630-842932a63d
@eduperez It does not happen the same time but on both APs. I exchanged the cable to be sure but only to the port in the wall as they are permanently installed.
@slh very good idea with the switch. Have an dump as spare part that I can put in between. Changed it and now we have to wait....

But interesting that @lurulf has also problems with that port....

1 Like

I'm on 23.05.2. 23.05.0 was the same. I have stock firmware with the following changes, none which should have any impact on wired networking:

opkg remove wpad-basic-mbedtls
opkg install wpad-mbedtls
opkg install dawn umdns

They are not stable for extended periods of time, so I have a scheduled reboot every night.

They are configures exclusively through use of uci/script, no "fiddling" with vi:

uci set system.@system[0].hostname='XXXXXXXXXXXXXXXX'
uci set system.@system[0].timezone='CET-1CEST,M3.5.0,M10.5.0/3'
uci set system.@system[0].zonename='Europe/Oslo'

uci del network.@device[0].ports
uci add_list network.@device[0].ports='eth1.1'
uci add_list network.@device[0].ports='eth0.2'
uci del network.wan
uci del network.wan6
uci set network.lan.proto='static'
uci set network.lan.ipaddr='192.168.x.x'
uci set network.lan.gateway='192.168.x.1'
uci set network.lan.broadcast='192.168.x.255'
uci set network.lan.netmask='255.255.255.0'
uci del network.lan.dns
uci add_list network.lan.dns='192.168.x.1'
uci add_list network.lan.dns='1.0.0.1'
uci add_list network.lan.dns='1.1.1.1'
uci del network.lan.ip6assign
uci del dhcp.lan.ra_slaac
uci set dhcp.lan.ignore='1'
uci set dhcp.wan.ignore='1'
uci set dhcp.odhcpd.ignore='1'
uci commit

#Skru av ting vi ikke skal ha
/etc/init.d/dnsmasq disable
/etc/init.d/dnsmasq stop
/etc/init.d/odhcpd disable
/etc/init.d/odhcpd stop
/etc/init.d/firewall disable
/etc/init.d/firewall stop
#/etc/init.d/network reload

uci set uhttpd.main.redirect_https='1'

uci set wireless.radio0.htmode='VHT80'
uci set wireless.radio0.channel='100'

uci set wireless.radio1.htmode='HT20'
uci set wireless.radio1.channel='6'

for radio in 0 1; do
  #Sette land
  uci set wireless.radio${radio}.country='NO'
  #Denne skal ikke endres fra standardverdi: 0
  uci del wireless.radio${radio}.cell_density
  #Skru på radio
  uci del wireless.radio${radio}.disabled
  #SSID
  uci set wireless.default_radio${radio}.ssid='XXXXXXXXXXXXXXXX'
  #Passord
  uci set wireless.default_radio${radio}.key='XXXXXXXXXXXXXXXX'
  #Sikkerhet
  uci set wireless.default_radio${radio}.encryption='psk2+ccmp'
  #Denne skal ikke endres fra standardverdi: 1
  uci del wireless.default_radio${radio}.wmm
  #=========================
  #Sikkerhetsinnstillinger
  #=========================
  #Chromecast tåler ikke ieee80211w=2 (required), så da blir det ieee80211w=1 (optional)
  uci set wireless.default_radio${radio}.ieee80211w='1'
  uci set wireless.default_radio${radio}.wpa_disable_eapol_key_retries='1'
  #=========================
  #Roaming (802.11r+802.11k+802.11v + DAWN)
  #=========================
  #802.11r
  uci set wireless.default_radio${radio}.ieee80211r='1'
  uci set wireless.default_radio${radio}.mobility_domain='123f'
  uci set wireless.default_radio${radio}.ft_over_ds='1'
  uci set wireless.default_radio${radio}.ft_psk_generate_local='1'
  #802.11k
  uci set wireless.default_radio${radio}.ieee80211k='1'
  #Slettes da de blir satt automagisk når man skrur på 802.11k
  uci del wireless.default_radio${radio}.rrm_beacon_report
  uci del wireless.default_radio${radio}.rrm_neighbor_report
  uci set wireless.default_radio${radio}.time_advertisement='2'
  uci set wireless.default_radio${radio}.time_zone='CET-1CEST,M3.5.0,M10.5.0/3'
  #802.11v
  uci set wireless.default_radio${radio}.bss_transition='1'
  uci set wireless.default_radio${radio}.wnm_sleep_mode='1'
  uci set wireless.default_radio${radio}.wnm_sleep_mode_no_keys='1'
  #Jeg vil ikke ha proxy_arp pga sikkerhet: https://www.cisco.com/c/en/us/support/docs/ip/dynamic-address-allocation-resolution/13718-5.html
  uci del wireless.default_radio${radio}.proxy_arp
  #Må ha en "commit" da jeg bruker tidligere verdier for å sette nasid (802.11r innstilling)
  uci commit
  uci set wireless.default_radio${radio}.nasid=$(uci get system.@system[0].hostname).$(uci get wireless.default_radio${radio}.ssid)_${radio}
  uci commit
done

I'm getting a mr90x delivered tomorrow and will be able to compare with my wax206.

1 Like

Just an update on this, ISP Engineer has just replaced my 1GB ONT with a 2.5GB ONT, so I now see a full 2.5GB uplink, will report it it drops.

1 Like