I dont think so. I have two WAX220 and no devices have ever had conncectivity issues. Then again i have no Apple devices. Only speed issues with the uplink.
Yesterday I decided to flash again openwrt on my WAX220.
The last vendor firmware started to exhibit some nasty glitches with WMM with my yamaha AVR.
Well it seems stable, however there are an inconsistency between the AP and the router reported link rates.
ethtool on the router (ER-X) says 1gb full duplex
ethtool on the AP (WAX220) says 1gb unknown duplex (ERR 255).
iperf3 test is consistent with a 1gb full duplex speed.
Have you tried with snapshot to compare the behavior?
I just flashed mine to latest snapshot but not yet tested, can you show me how to reproduce the problem?
It could not be reproducible, because It could be hardware dependant:
opened 12:50PM - 29 Jan 24 UTC
target/mediatek
bug
release/23.05
Official Image
### Describe the bug
When connecting the NETGEAR WAX220 to a 1Gbps port the dup… lex detection fails and ethtool states: `Speed: 1000Mb/s Duplex: Unknown! (255)` when connected to a 2.5Gbps port its works correctly and ethtool states Speed: 2500Mb/s Duplex: Full. This result in a-sync TX en RX when connected to a 1Gbps port `369 Mbits/sec receiver, 940 Mbits/sec sender`
### OpenWrt version
r23630-842932a63d
### OpenWrt release
23.05.2
### OpenWrt target/subtarget
mediatek/filogic
### Device
Netgear WAX220
### Image kind
Official downloaded image
### Steps to reproduce
1. Connect WAP to a 1Gbps
2. View the duplex setting with ethtool
3. Run a iperf3 test with the flag --bidir
4. View results.
5. Repeat step 1 till 4 when connected to a 2.5Gbps port.
### Actual behaviour
Speed seems to be async and TX and RX differ a lot see results below:
```
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 2500baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 2500baseT/Full
Advertised pause frame use: Symmetric Receive-only
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: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 6
Transceiver: external
Auto-negotiation: on
MDI-X: Unknown
Current message level: 0x000000ff (255)
drv probe link timer ifdown ifup rx_err tx_err
Link detected: yes
Connecting to host 192.168.10.66, port 5201
[ 5] local 192.168.10.9 port 36152 connected to 192.168.10.66 port 5201
[ 7] local 192.168.10.9 port 36162 connected to 192.168.10.66 port 5201
[ ID][Role] Interval Transfer Bitrate Retr Cwnd
[ 5][TX-C] 0.00-1.00 sec 45.4 MBytes 380 Mbits/sec 209 82.0 KBytes
[ 7][RX-C] 0.00-1.00 sec 110 MBytes 926 Mbits/sec
[ 5][TX-C] 1.00-2.00 sec 44.0 MBytes 369 Mbits/sec 267 70.7 KBytes
[ 7][RX-C] 1.00-2.00 sec 112 MBytes 937 Mbits/sec
[ 5][TX-C] 2.00-3.00 sec 43.8 MBytes 367 Mbits/sec 249 55.1 KBytes
[ 7][RX-C] 2.00-3.00 sec 112 MBytes 937 Mbits/sec
[ 5][TX-C] 3.00-4.00 sec 44.6 MBytes 374 Mbits/sec 170 109 KBytes
[ 7][RX-C] 3.00-4.00 sec 112 MBytes 937 Mbits/sec
[ 5][TX-C] 4.00-5.00 sec 44.2 MBytes 371 Mbits/sec 219 77.8 KBytes
[ 7][RX-C] 4.00-5.00 sec 112 MBytes 938 Mbits/sec
[ 5][TX-C] 5.00-6.00 sec 45.1 MBytes 379 Mbits/sec 137 66.5 KBytes
[ 7][RX-C] 5.00-6.00 sec 112 MBytes 937 Mbits/sec
[ 5][TX-C] 6.00-7.00 sec 42.9 MBytes 360 Mbits/sec 147 139 KBytes
[ 7][RX-C] 6.00-7.00 sec 112 MBytes 937 Mbits/sec
[ 5][TX-C] 7.00-8.00 sec 45.6 MBytes 383 Mbits/sec 230 65.0 KBytes
[ 7][RX-C] 7.00-8.00 sec 112 MBytes 937 Mbits/sec
[ 5][TX-C] 8.00-9.00 sec 43.4 MBytes 364 Mbits/sec 223 63.6 KBytes
[ 7][RX-C] 8.00-9.00 sec 112 MBytes 938 Mbits/sec
[ 5][TX-C] 9.00-10.00 sec 42.0 MBytes 352 Mbits/sec 214 62.2 KBytes
[ 7][RX-C] 9.00-10.00 sec 112 MBytes 937 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID][Role] Interval Transfer Bitrate Retr
[ 5][TX-C] 0.00-10.00 sec 441 MBytes 370 Mbits/sec 2065 sender
[ 5][TX-C] 0.00-10.01 sec 440 MBytes 369 Mbits/sec receiver
[ 7][RX-C] 0.00-10.00 sec 1.09 GBytes 940 Mbits/sec sender
[ 7][RX-C] 0.00-10.01 sec 1.09 GBytes 935 Mbits/sec receiver
```
### Expected behaviour
Correct detection of the duplex setting and full utilization of the line speed as with the use of a 2.5Gpbs port see below
```
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 2500baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 2500baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
2500baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 2500Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 6
Transceiver: external
Auto-negotiation: on
MDI-X: Unknown
Current message level: 0x000000ff (255)
drv probe link timer ifdown ifup rx_err tx_err
Link detected: yes
Connecting to host 192.168.10.66, port 5201
[ 5] local 192.168.10.9 port 36150 connected to 192.168.10.66 port 5201
[ 7] local 192.168.10.9 port 36158 connected to 192.168.10.66 port 5201
[ ID][Role] Interval Transfer Bitrate Retr Cwnd
[ 5][TX-C] 0.00-1.00 sec 114 MBytes 960 Mbits/sec 0 539 KBytes
[ 7][RX-C] 0.00-1.00 sec 111 MBytes 933 Mbits/sec
[ 5][TX-C] 1.00-2.00 sec 112 MBytes 936 Mbits/sec 0 539 KBytes
[ 7][RX-C] 1.00-2.00 sec 112 MBytes 935 Mbits/sec
[ 5][TX-C] 2.00-3.00 sec 112 MBytes 944 Mbits/sec 0 609 KBytes
[ 7][RX-C] 2.00-3.00 sec 110 MBytes 926 Mbits/sec
[ 5][TX-C] 3.00-4.00 sec 111 MBytes 934 Mbits/sec 0 609 KBytes
[ 7][RX-C] 3.00-4.00 sec 112 MBytes 935 Mbits/sec
[ 5][TX-C] 4.00-5.00 sec 112 MBytes 944 Mbits/sec 0 609 KBytes
[ 7][RX-C] 4.00-5.00 sec 112 MBytes 936 Mbits/sec
[ 5][TX-C] 5.00-6.00 sec 111 MBytes 934 Mbits/sec 0 609 KBytes
[ 7][RX-C] 5.00-6.00 sec 112 MBytes 935 Mbits/sec
[ 5][TX-C] 6.00-7.00 sec 112 MBytes 943 Mbits/sec 0 609 KBytes
[ 7][RX-C] 6.00-7.00 sec 112 MBytes 935 Mbits/sec
[ 5][TX-C] 7.00-8.00 sec 111 MBytes 933 Mbits/sec 0 609 KBytes
[ 7][RX-C] 7.00-8.00 sec 112 MBytes 935 Mbits/sec
[ 5][TX-C] 8.00-9.00 sec 112 MBytes 943 Mbits/sec 0 609 KBytes
[ 7][RX-C] 8.00-9.00 sec 112 MBytes 935 Mbits/sec
[ 5][TX-C] 9.00-10.00 sec 112 MBytes 944 Mbits/sec 0 609 KBytes
[ 7][RX-C] 9.00-10.00 sec 112 MBytes 936 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID][Role] Interval Transfer Bitrate Retr
[ 5][TX-C] 0.00-10.00 sec 1.10 GBytes 941 Mbits/sec 0 sender
[ 5][TX-C] 0.00-10.02 sec 1.09 GBytes 938 Mbits/sec receiver
[ 7][RX-C] 0.00-10.00 sec 1.09 GBytes 936 Mbits/sec sender
[ 7][RX-C] 0.00-10.02 sec 1.09 GBytes 933 Mbits/sec receiver
```
### Additional info
The Iperf test are done with the same hardware, cables and settings.
### Diffconfig
_No response_
### Terms
- [X] I am reporting an issue for OpenWrt, not an unsupported fork.
That's why I and others suggested a note in the wiki of nwa50ax pro and wax220...
OK I looked into that Github comment, so what they mean is, WAX220 might have more than 1 type of LAN PHY and Realtek PHY is known to have problem? I might take a look of mine tonight.
Nope, it says that there are various revisions of realtek phy and some of them are problematic (the oldest one).
I just tested and my WAX220 has the same problem as well
You could try buying a 2.5gb switch...
Otherwise you have to revert to the vendor firmware, which has a severe bug with WMM and probably with multicast to unicast.
Is it possible to force duplex? And I just tested with 100M and it's even worse, unable to connect at all.
You can using ethtool and running
ethtool -s eth0 speed 1000 duplex full autoneg on
but the results show that it doesn't exactly fix the issue. See my post above about the speed tests when I tried it.
If you are affected you can only buy a 2.5gb switch or revert to stock firmware or wait for a fix by openwrt developers
@Flole @daniel could this be related to the issues with 10/100/1000? The below is when connected to a 1000 switch
[ 3.278578] mtk_soc_eth 15100000.ethernet eth0: PHY [mdio-bus:06] driver [RTL8221B-VB-CG 2.5Gbps PHY] (irq=61)
[ 3.288667] mt7986b-pinctrl 1001f000.pinctrl: Can not find pin
[ 3.294480] genirq: Failed to request resources for mdio-bus:06 (irq 61) on irqchip mt-eint
[ 3.302828] RTL8221B-VB-CG 2.5Gbps PHY mdio-bus:06: Error -22 requesting IRQ 61, falling back to polling
[ 3.316157] mtk_soc_eth 15100000.ethernet eth0: configuring for phy/2500base-x link mode
Gory19
July 17, 2024, 6:48pm
174
Does the new openwrt update fix the issue?
johnb
July 19, 2024, 4:00pm
176
Thanks for posting this patch.
Does this let you negotiate 1Gbps duplex on your hardware?
I haven't seen any follow ups to this patch on this thread yet.
no the patch i provided is for the apple disconnect issue.
1 Like
I'm a little confused about this device.
Netgear claims it has 4*4 5 GHz radio, but I can only see three antennas and so is claimed by the OpenWrt wiki.
Are they doing false advertising? Which one is true?
It's false advertising. The radios are 3x3 for the 5GHz and 2x2 for the 2.4GHz.
And can it still achieve 3600 Mbps theoretical speed over 5 GHz in WiFi 6 or is it false too? I've seen some MCS tables but I'm not sure at which column to look at.
Can it operate at 160 MHz in 3x3 mode? Now I own a wireless router that can either do 2x2 at 160 or 4x4 at 80.
I believe it can theoretically achieve 3.6 Gbps over the 5GHz with 160MHz channel width, at least according to my OpenWRT install. I ran a speed test using iPerf3 and achieved 1.5Gbps from laptop to AP, but the radio in my computer can only go up to 2.4Gbps theoretical speed. I don't know if either device's CPU can truly achieve 2.4Gbps or faster in a speedtest so my test was flawed. The 2.4GHz can only do 40MHz channel width though on a 2x2.