Alfa AWUS036AXM / EDUP EP-AX1672 as 6GHz AP? #514
Comments
|
My opinion is 6ghz is not ready for prime time on any platform. Some people got the "disabled" channels to work. |
|
Hi @snaens
Me too. We have seen many reports from users of adapters with mt7921au chips that have successfully created a 6 GHz AP. They were all in the EU with country codes like DE and FR. This tends to indicate the issue is regulatory and not with hardware of driver. Tell us what country you are in. FYI: Recently there was one person that reported a 6 GHZ WiFi 7 AP with a mt7925 chip in the US. The report is here somewhere and I used some info from his report but I have been busy on other things. The example hostapd.conf that I have up for WiFi 6 is in really good shape. What you might want to do is use WiFi 6 with the least congested channel you can find on either 2.4 or 5 GHz until such time as this is sorted out. Something to keep in mind given that you have a robotics project going is that the range drops off greatly with 6 GHz so it may not be the holy grail. |
This is for a competition/research robot in an academic context, Ofc 6GHz needs work, but I don't mind bandwidth/hi-speed performance,
I tried that, but I feel like my specific module may be locked-out.
Conveniently I am in the country with the code DE ;) I did however only run short-length tests.
Yea I think I read that at some point, and promptly was confused when my modules (and those of some others on the net) straight up disabled or didn't support 6GHz.
I tried using it on OpenWRT on a Pi4 with my weird RZ608, but it always fails to initialize (illegal channel combination) and then shuts down.
So far we have been sneakily running on the top-end of the 5GHz spectrum, as many devices can't go that high and there are 1~2 free channels most of the time. This is usually fine, except we have 2 robots, and there is only really bandwidth for one. We have no chance contesting for 'regular' channels, as we are in a sort of "antweight" challenge, and share the room/hall with univerity robots 10x our size, which all have crazy overpowered APs
It is in a competition scenario. If you actually wanted to use the robots long-range outdoors, you'd probably be using different bands and radios. I'm going to try my RZ608 on more standard hardware on debian testing/trixie and see what happens. |
Cool. You should be up and running according to what I have read from others in DE.
You do have WPA3 selected, right? It is required for band 4 (6 Ghz). Mixed won't work and WPA2 won't work.
My favorite USB WiFi adapter in the WiFi 6, mt7921au, class is the Edup adapter as shown in the mt7921au section of the Plug and Play List. Darn good little adapter that has reasonable range, a decent price and seems to be widely available these days... make sure you get the right one. The model number is in the Plug and Play List. |
Yep, I saw your comment in the conf 👍 The bjlockie wasn't kidding when they said WiFi 6 mode isn't ready: FYI I switched modes by setting
I went looking for that one, the EDUP EP-AX1672 at first, but you can't get it in Europe apparently. So I either get the EDUP for ~45$ from the USA or the AWUS036AXM locally for ~30$. (both after tax and shipping) Anyhow, @morrownr, since you seem to have an EDUP EP-AX1672 from the US, can you please run |
$ uname -r $ iw reg get
$ sudo iw reg set DE $ iw reg get It looks like you should be good to go on the lower channels. |
|
Alright, fantastic! Order has gone out, shipping takes a week. I purchased through this link https://www.amazon.de/gp/product/B0DFYBZSR6/ |
snaens
changed the title
|
I am slowly doing some deep research into using band 4 (6 GHz) for AP mode on Linux. I am finding some good info so check back in with me when ready. |
|
may I add a comment, because it fits to the title here: I ordered a Edup AX1672 from the above Amazon UK link and today, out of curiosity I opened the case.
|
|
Hi @Andy-45
This is a good question. I have one of the Edup EP=AX1672 adapters and it does not suffer from the BT issue. I took the Alfa AXML out of the The Plug and Play List until such time as the problem is resolved. I thought the list was clean of adapters with the BT problem. Are you saying that the AXM has the BT problem? |
|
yes, the AWUS036AXM has the BT problem, look at my original post -> #495 |
Going to do it right now. That makes 3 adapters that have shown the problem and all were early adapters. The other was the Comfast 953. This problem did not show until late last year and it is a BT stack issue as best I can make of it. Hopefully it can be fixed. |
|
Hi, sorry for disappearing like that. I purchased both an Alfa AWUS036AXM and a EDUP EP-AX1672. right: Alfa AWUS036AXM, left: EDUP EP-AX1672 Note that the Alfa chips are sanded or something, and almost impossible to read. Unfortunately my Alfa came DOA (bought on amazon '2nd hand', had been returned before). I was able to create an AP on 6GHz, scans on other 6GHz-capable devices also picked it up. (Debian testing/trixie with hostapd and WiFi7 config) I see |
|
Be careful with that WiFi 6e config. It is a work in progress. Note that it is not linked to the Main Menu. The WiFi 6 config is linked to the Main Menu but does not support 6 GHz. I am working on 6 GHz but am not ready to release it yet.
This is fishy. As you saw, I removed the AXM from the Plug and Play List after noting Andy's report. The AXML has been done for a while. I'm going to investigate and see if I can find some answers about what is going on. Back to the hostapd.conf file issue: Tell me what you are trying to do and I'll see if I can get something to you. |
|
Well, I'm still trying to get an AP functioning :P The 6e config seems to work. NetworkManager on my PC (mac addr censored): Cli: My hostapd config (on raspi)
# /etc/hostapd/hostapd-WiFi6e.conf
# Documentation: https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf
# 2024-10-09
# Purpose: hostapd.conf example for WiFi 6e configuration for USB WiFi adapters using the mt7921au chip.
# Status: alpha1, please test and report.
# Requirements for WiFi-6e (ieee80211ax) on 6GHz:
# - WPA3 for authentication
# - SAE key management required for WPA3
# - Management Frame Protection required for WPA3
# - Radar awareness required for some RegDomains on 5GHz and 6GHz
# - WME/WMM required
# Information:
# - tested on RasPi4B with 64 bit RasPiOS
# - see [Main Menu](https://github.com/morrownr/USB-WiFi) for...
# -- make sure mt7921 firmware files are installed/updated
# [How to install firmware for Mediatek-based USB WiFi adapters](https://github.com/morrownr/USB-WiFi/blob/main/home/How_to_Install_Firmware_for_Mediatek_based_USB_WiFi_adapters.md)
# -- you need hostap 2.10 or later for WiFi 6 support: $ hostapd -v
# [Upgrade hostapd to support WiFi 6](https://github.com/morrownr/USB-WiFi/blob/main/home/AP_Mode/Upgrade_hostapd.md)
# - improvements are welcome
# SSID
ssid=myPI-WiFi6e
# PASSPHRASE
wpa_passphrase=myPW1234
sae_password=myPW1234
# Band: a = 5GHz & 6GHz (a/n/ac/ax), g = 2Ghz (b/g/n)
hw_mode=a
# Channel availability varies by country
# https://en.wikipedia.org/wiki/List_of_WLAN_channels
# US:
# 2.4 GHz (1-11)
# 5 GHz ((36(42) and 149(155))
# 5 GHz DFS ((52(58), 100(106), 116(122), 132(138))
# 6 GHz (see op_class below)
# Channel (change as needed)
# band 1 (2.4 GHz)
#channel=6
# band 2 (5 GHz)
#channel=36
# band 4 (6 GHz)
channel=53
# The operating class is an indication of the 6 GHz channel size. An
# operating class of 134 indicates a 160 MHz channel. Likewise, 133
# denotes an 80 MHz channel, 132 indicates a 40 MHz channel, and 131
# indicates a channel size of 20 MHz.
# 133 signifies channel width: 80 MHz
# channels 7, 23, 39, 55, 71, 87, 103, 119, 135, 151, 167, 183, 199, 215
# 134 signifies channel width: 160 MHz
# channels 15, 47, 79, 111, 143, 175, 207
op_class=132
# Country code
# https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2
country_code=DE
# All environments
#country3=0x20
# Outdoor
#country3=0x4f
# Indoor environment only
country3=0x49
#he_6ghz_reg_pwr_type=0
# Advertises the country_code and the set of allowed channels and transmit power levels
ieee80211d=1
# Enables support for 5GHz DFS channels if supported (requires ieee80211d=1)
#ieee80211h=1
# Bridge interface
#bridge=br0
wds_sta=1
# WiFi interface (wlan0 should be changed to your interface name)
interface=wlan1
# Set hostapd driver (nl80211 is used with all Linux mac80211 (in-kernel) and modern Realtek drivers)
driver=nl80211
# hostapd event logger configuration
#
# Module bitfield (ORed bitfield of modules that will be logged; -1 = all
# modules):
# bit 0 (1) = IEEE 802.11
# bit 1 (2) = IEEE 802.1X
# bit 2 (4) = RADIUS
# bit 3 (8) = WPA
# bit 4 (16) = driver interface
# bit 6 (64) = MLME
#
# Levels (minimum value for logged events):
# 0 = verbose debugging
# 1 = debugging
# 2 = informational messages
# 3 = notification
# 4 = warning
#
logger_syslog=-1
logger_syslog_level=0
# Control interface - (i.e. for hostapd_cli)
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
# Expect this AP not to change its position and antenna alignment
stationary_ap=1
he_6ghz_rx_ant_pat=1
# Various settings
#beacon_int=100
#dtim_period=2
#multicast_to_unicast=0
#tx_queue_data2_aifs=1
#tx_queue_data2_cwmin=7
#tx_queue_data2_cwmax=15
#tx_queue_data2_burst=3.0
tx_queue_data2_burst=2.0
uapsd_advertisement_enabled=1
utf8_ssid=1
multi_ap=0
bss_load_update_period=60
chan_util_avg_period=600
disassoc_low_ack=0
skip_inactivity_poll=1
preamble=1
# Security
# authentication algorithms (3 = both are allowed, use 3 for SAE otherwise use 1)
auth_algs=1
# Limit number of concurrent "clients" (stations) and do not restrict them by MAC address
max_num_sta=16
macaddr_acl=0
# hidden SSID (1 = hidden)
ignore_broadcast_ssid=0
# Opportunistic Key Caching (1 = enabled)
okc=1
# Enable WPA. (2 is required for WPA2, mixed and WPA3)
wpa=2
# Pairwise cipher
rsn_pairwise=CCMP CCMP-256 GCMP GCMP-256
group_mgmt_cipher=AES-128-CMAC
extended_key_id=1
wpa_gmk_rekey=86400
wpa_group_rekey=86400
wpa_group_update_count=4
#
# Activate only one of the following 3 sections
#
# 1. WPA2 Personal
#wpa_key_mgmt=WPA-PSK
#wpa_key_mgmt=WPA-PSK WPA-PSK-SHA256
#
# 2. WPA2/WPA3 Transitional (mixed)
# Many older WPA2 devices are not compatible with this setting
#wpa_key_mgmt=SAE WPA-PSK WPA-PSK-SHA256
#ieee80211w=1
#sae_require_mfp=1
#
# 3. WPA3 Personal (required for band 4, 6 GHz)
# Some older WiFi 4 devices may not be compatible with this setting
wpa_key_mgmt=SAE
ieee80211w=2
beacon_prot=1
# Wireless Multimedia Extensions (WME) and Wi-Fi Multimedia (WMM)
wme_enabled=1
wmm_enabled=1
# IEEE 802.11n (WiFi 4) band 1, 2.4 GHz configuration
# This section is required when operating WiFi 6 on band 1, 2.4 GHz
#ieee80211n=1
#
# generic setting - 20 MHz channel width
#ht_capab=[SHORT-GI-20]
#
# generic setting - 40 MHz channel width (if allowed)
#ht_capab=[HT40+][HT40-][SHORT-GI-20][SHORT-GI-40]
#
# mt7921au (HT capabilities 0x9ff)
# 20 MHz channel width
#ht_capab=[LDPC][GF][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935]
# 40 MHz channel width
#ht_capab=[LDPC][HT40+][HT40-][GF][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935]
#
# IEEE 802.11ac (WiFi 5) configuration
# When using band 1 (2.4 GHZ) comment out the below line
#ieee80211ac=1
# Channel width (0 = 40 MHz. 1 = 80 Mhz)
# When using band 1 (2.4 GHZ) comment out the below line
#vht_oper_chwidth=1
# VHT center channel (chan + 6)
# When using band 1 (2.4 GHZ) comment out the below line
#vht_oper_centr_freq_seg0_idx=42
# generic setting
#vht_capab=[SHORT-GI-80]
#
# mt7921au (VHT capabilities 0x339071b2)
# When using band 1 (2.4 GHZ) comment out the below line
#vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMEE][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7]
#
# IEEE 802.11ax (WiFi 6) configuration
ieee80211ax=1
# Channel width (0 = 40 MHz. 1 = 80 Mhz)
# For WiFi 6 on band 1 (2.4 GHz) comment out the below line
he_oper_chwidth=0
# HE center channel (chan + 6)
# For WiFi 6 on band 1 (2.4 GHz) comment out the below line
he_oper_centr_freq_seg0_idx=55
#53
# used by clients to discern the source of interference
# each AP in your area needs to use a different number
# allowed: 1-63
he_bss_color=37
# Activate beamforming capabilities
he_mu_beamformer=1
he_su_beamformee=1
he_su_beamformer=1
#he_default_pe_duration=4
#he_rts_threshold=1023
#he_mu_edca_qos_info_param_count=0
#he_mu_edca_qos_info_q_ack=0
#he_mu_edca_qos_info_queue_request=0
#he_mu_edca_qos_info_txop_request=0
#he_mu_edca_ac_be_aifsn=8
#he_mu_edca_ac_be_aci=0
#he_mu_edca_ac_be_ecwmin=9
#he_mu_edca_ac_be_ecwmax=10
#he_mu_edca_ac_be_timer=255
#he_mu_edca_ac_bk_aifsn=15
#he_mu_edca_ac_bk_aci=1
#he_mu_edca_ac_bk_ecwmin=9
#he_mu_edca_ac_bk_ecwmax=10
#he_mu_edca_ac_bk_timer=255
#he_mu_edca_ac_vi_ecwmin=5
#he_mu_edca_ac_vi_ecwmax=7
#he_mu_edca_ac_vi_aifsn=5
#he_mu_edca_ac_vi_aci=2
#he_mu_edca_ac_vi_timer=255
#he_mu_edca_ac_vo_aifsn=5
#he_mu_edca_ac_vo_aci=3
#he_mu_edca_ac_vo_ecwmin=5
#he_mu_edca_ac_vo_ecwmax=7
#he_mu_edca_ac_vo_timer=255
# Quirks and Workarounds:
#
# 6GHz band is completely disabled in iw list. This may be the case if you try to use a
# MEDIATEK card on Linux 6.6.30 or 6.7.x or newer. There seems to be a lot going on in the
# Kernel's WiFi section right now. A new feature called "CLC (Country Location Control)" which
# must be disabled in the mt7921_common module to use the 6GHz band. Make a file
# /etc/modprobe.d/mt7921.conf containing options mt7921_common
# disable_clc=1. Source: https://community.frame.work/t/responded-amd-rz616-wifi-card-
# doesnt-work-with-6ghz-on-kernel-6-7/43226
# Throughput jitters on MT7922 cards. You might try to disable power management for that
# card by adding the line options mt7921e disable_aspm=Y to the file
# /etc/modprobe.d/mt7921.conf. This setting flattened out the valleys in my throughput
# graphs.
# Wireless Regulation Domain would not apply correctly. There seem to be issues with the
# current wireless-regdb packages delivered with VyOS. As of now, 5GHz channels would
# not allow access point operation (iw list showing no-ir on all channels) and 6GHz
# channels would be completely disabled. Also, switching country codes (iw reg set DE)
# would not have any effect. For now, I have this workaround:
# Download and install wireless-regdb from the Ubuntu Packages page, and
# (not needed anymore with newest 1.5-rolling) manually configure your regulatory
# domain as option for the cfg80211 module by editing
# /etc/modprobe.d/cfg80211.conf and adding this line: options cfg80211 ieee80211_regdom=DE
# End of hostapd-WiFi6.confI note that selecting a frequency was very odd, especially for 80MHz. I wonder if the edup being up can convince my AX210 to do the same (it says NO-IR on all channels) |
I am working through a usb wifi adapter as AP using 6 GHz right now. 6 GHz settings for hostapd are hard to figure out but I am on the way. I can't provide more details right now.
Not likely. For 40 GHz, try channels 65 and 67. There are likely some he specific settings that need to be address on the mt7921au chip for hostapd.conf. I'll try to sort that out. Edit: I meant 6 GHz specific settings in the above sentence. |
|
@snaens |
|
I tried using wpa_supplicant instead of NetworkManager
Triggering a scan using Note
This all seems a bit like two driver interfaces/APIs being used simultaneously, and only one suppoting 6GHz, no? The EDUP AP seems to be working alright, It's been active and connectable all day. This would all be so much easier if I just had another mt7921au device... |
It sure shows up in my WiFi menu (on KDE)
|
A few months ago, I bought a Mini PC. It came with a AX210 based M.2 card. I knew I would eventually want to do things with AP mode so I bought a M.2 card based on the mt7925 chip. I think it only cost like $22 USD. The mt7925u driver is impressive so far. and has been in the kernel since 6.7. I must add that my testing has not included AP mode yet. Not enough time in the day to do everything I would like to do. I have seen OpenWRT users with M.2 cards based on the mt7925 setting up 6 GHz/WiFi 6 and WiFi 7 APs. Yeah, the driver is already in the current stable of OpenWRT. Something to think about. |
|
Yesterday I ordered a QCNFA765 card for 13€ But anything with a mt7925 costs like ~30€, and I just want something else to test this AP on. I also gave Windows 11 a shot just now (VM with PCIe passthrough), but that didn't show anything on 6GHz, even in scans. |
Someone else was asking me if I knew anything about this chip recently and I could not offer anything. I watch linux-wireless and OpenWRT. Qualcomm and Mediatek dominate the OpenWRT supported wifi routers. I support 2 routers with Qualcomm SOCs and one with a Mediatek SOC. Both companies do a good job but in my limited sample size, Mediatek drivers are better. I'd like to hear about what you find out. |
|
Delivery takes 10-ish days, I'll report back then ;) |
|
Still no luck, the new card won't connect either. |
|
Won't connect to what? An AP/wifi router? |
|
Yup, the pi + edup AP. Honestly I think this is an issue with the NetworkManager backend; How did you connect with wpa_supplicant? |
|
My setup: this time I used nmcli to connect:
the proof that it works on 6GHz:
client wpa_supplicant-wlan1.conf:
AP hostapd.conf (not optimized, just a working demo):
|
Hey all,
I'd like to create an AP on 6GHz using a compact USB or PCIe module with external antennas.
(It will be used for a robot in areas where 2.4 and 5GHz are saturated)
I read the Alfa AWUS036AXM (MT7921AUN) and EDUP EP-AX1672 (MT7921AU) are good candidates,
but I can't find out if they can be used as an AP on 6GHz.
Can someone clarify this? (send the output of
iw list)I'm curious, because the the following 2 devices use the same chipset and neither work:
The Alfa AWUS036AXML (MT7921AUN) apparently doesn't like 6GHz AP mode (NO-IR).
https://github.com/FinchSec/wifi-adapter-testing/Kali2023.1/iw-phy-info.txt#L511-L570
And in my tests a RZ608 (MT7921K) PCIe module didn't want to do 6GHz at all
-
iw listshows 'disabled' for all, no matter what country i set it to- note that I got it second-hand, no idea if it is some OEM stuff
iw list output
Through your
iw listdatabase I (finally) found a module that multiple sources confirm should be able to do 6GHz AP:the QCNFA765
I may go buy one to find out.
The text was updated successfully, but these errors were encountered: