I achieved over 1.6 Gbps with 160 MHz and a 2x2 laptop wifi card in iperf3. That's great!
Is there any progress, even in the snapshot builds, about the performance with ethernet links under 2.5 Gbps? I am experiencing issues with 1G between AP and router.
Does somebody knows if there is something special with die failsafe mode on the wax220 (23.05.4)?
As described in the Wiki, a flashing LED indicates that I am in failsafe mode. but i could not connect via ssh to root@192.168.1.1 with static ip setup.
On two other openwrt devices, it works that way.
Turn on your device and press and hold the reset button for 15-20 seconds.
Nothing for now.
I ended buying a 2.5gb unmanaged switch (less than 50€/$ on Amazon)
But who should fix it? Is it a vendor issue or just OpenWrt's implementation that is flawed?
See my post of 11th of july and the link I provided
Thank you for your answer.
But what you describe is the procedure for the factory reset and not for the failsafe mode???
did the patching help? also dumb question, but can I apply the patch at runtime or do i have to build my own image?
hello,
i'm thinking about replacing my R7800 with a WAX220 for AP usage in a 2.5G network, but i'm a little bit scared about wifi coverage since R7800 has external antennas (even if i could not find antennas gain) and WAS220 has not.
any of you noticed any problem in wifi coverage?
thanks
I have both at home - WAX220 is perfect if you have devices in the same room. But if your devices are behind the wall then R7800 is way faster
thanks
well, not good if someone is not living in a big openspace 
does anyone have info on the development on the ethernet issue?
No fix with the latest update.
Looks like there is no update on this?
For 1G port issue - this commit from yesterday looks like it should address the issues with 1G ports
and this patch is for anyone who has the iphone wifi issues
--- mac80211.sh 2024-07-05 14:27:14.207087744 +0100
+++ package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh 2024-07-05 13:59:31.758567460 +0100
@@ -465,25 +465,25 @@
append base_cfg "he_mu_edca_qos_info_q_ack=0" "$N"
append base_cfg "he_mu_edca_qos_info_queue_request=0" "$N"
append base_cfg "he_mu_edca_qos_info_txop_request=0" "$N"
- append base_cfg "he_mu_edca_ac_be_aifsn=8" "$N"
+ append base_cfg "he_mu_edca_ac_be_aifsn=15" "$N"
append base_cfg "he_mu_edca_ac_be_aci=0" "$N"
- append base_cfg "he_mu_edca_ac_be_ecwmin=9" "$N"
+ append base_cfg "he_mu_edca_ac_be_ecwmin=10" "$N"
append base_cfg "he_mu_edca_ac_be_ecwmax=10" "$N"
append base_cfg "he_mu_edca_ac_be_timer=255" "$N"
append base_cfg "he_mu_edca_ac_bk_aifsn=15" "$N"
append base_cfg "he_mu_edca_ac_bk_aci=1" "$N"
- append base_cfg "he_mu_edca_ac_bk_ecwmin=9" "$N"
+ append base_cfg "he_mu_edca_ac_bk_ecwmin=10" "$N"
append base_cfg "he_mu_edca_ac_bk_ecwmax=10" "$N"
append base_cfg "he_mu_edca_ac_bk_timer=255" "$N"
- append base_cfg "he_mu_edca_ac_vi_ecwmin=5" "$N"
- append base_cfg "he_mu_edca_ac_vi_ecwmax=7" "$N"
- append base_cfg "he_mu_edca_ac_vi_aifsn=5" "$N"
+ append base_cfg "he_mu_edca_ac_vi_ecwmin=10" "$N"
+ append base_cfg "he_mu_edca_ac_vi_ecwmax=10" "$N"
+ append base_cfg "he_mu_edca_ac_vi_aifsn=15" "$N"
append base_cfg "he_mu_edca_ac_vi_aci=2" "$N"
append base_cfg "he_mu_edca_ac_vi_timer=255" "$N"
- append base_cfg "he_mu_edca_ac_vo_aifsn=5" "$N"
+ append base_cfg "he_mu_edca_ac_vo_aifsn=15" "$N"
append base_cfg "he_mu_edca_ac_vo_aci=3" "$N"
- append base_cfg "he_mu_edca_ac_vo_ecwmin=5" "$N"
- append base_cfg "he_mu_edca_ac_vo_ecwmax=7" "$N"
+ append base_cfg "he_mu_edca_ac_vo_ecwmin=10" "$N"
+ append base_cfg "he_mu_edca_ac_vo_ecwmax=10" "$N"
append base_cfg "he_mu_edca_ac_vo_timer=255" "$N"
fi
the patch changes can be ran under /lib/netifd/wireless/mac80211.sh
Yeah I saw that from my email (I was in that GitHub thread), and I'm not rushing, just wait to see when new snapshot will have it.
Well this looks exciting! I just flashed the latest SNAPSHOT and this was the output of ethtool:
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
2500baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
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: 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
I did some iPerf3 tests and some file transfers to test the speed and reliability. Download is delivering full gigabit, the upload is much better at around 730 - 850 Mbps. The upload is rather unstable and fluctuates a bit, though. iPerf was all over the place for the upload. When I saturated the link with an FTP transfer, it appeared to stabilize. I understand this is still in the works, but things are looking much better. The link also negotiated on the eth0 port automatically without ethtool. I am anxious to see the final release.
Might it be possible to backport this to the next service release of 23.05.x?
Does anybody worked with the failsafemode or the serial connection of the wax220?
Curiously, after an update the firewall parameters have changed from allow to deny so that I can no longer reach the AP.
On another of my APs (D-Link), I was able to change this parameter in failsafe mode.
The WAX220, on the other hand, signals to me via the LED that I am in failsafe mode, but I cannot access the device via SSH. Any ideas?
Last time I made similar mistake and I used nmrpflash utility to flash back another OpenWrt firmware to recover my WAX220
The upload fluctuations appear to be fixed in today's SNAPSHOT. I can't wait for the next stable release!