Comments (33)
dubhater
commented on June 29, 2024
1
@kikitte Someone sent a fix for those warnings: https://lore.kernel.org/linux-wireless/[email protected]/
@Jake-Grafton What is the application in your screenshot?
from 8812au-20210820.
tcoard
commented on June 29, 2024
Updating to kernel 6.9.3 broke my wifi (I was on aircrack-ng/rtl8812au before), so I tried the repo you linked and it works!
System: Pop_OS!
Device: Linksys WUSB6300
USB Ports tried: 3.2 gen2, 3.2 gen1, 2.0
Notes: All ports work, I had to enter the credentials for my wifi network again when trying the 2.0 port.
Let me know if there is any more info you would like. (I don't know much about drivers, so I don't know what information is pertinent to send).
from 8812au-20210820.
morrownr
commented on June 29, 2024
Adding you to this message to make sure you are on this new issue for the 8812au. Note that this Issue is in the 8812au repo. See first report above.
I tried the repo you linked and it works!
That is great.
All ports work, I had to enter the credentials for my wifi network again when trying the 2.0 port.
Entering credentials again when you switch ports seems to be normal operations. Now to make sure that the driver is switching to be in the correct mode, can I get you to run the following command while in a usb2 port and then again in a usb3 port:
$ lsusb -t
Please post both sets of results. On the line for your driver, you should see 5000 if in usb3 mode and 480 if in usb2 mode. We need to make sure that is happening properly.
Let me know if there is any more info you would like. (I don't know much about drivers, so I don't know what information is pertinent to send).
Well figure out what info we need as we go. You just keep using it and if something does not work like you think it should, let us know what is wrong and we will tell you what info we need.
Your help is greatly appreciated. It will be cool when this driver is in mainline. Our 8812au adapters will finally have a proper in-kernel driver and will be plug and play.
from 8812au-20210820.
tcoard
commented on June 29, 2024
Yup, I see 5000 if in usb3 mode and 480 if in usb2 mode.
usb3:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M
|__ Port 4: Dev 6, If 0, Class=Vendor Specific Class, Driver=rtw_8812au, 5000M
|__ Port 6: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 6: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 6: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 5000M
|__ Port 6: Dev 2, If 3, Class=Human Interface Device, Driver=usbhid, 5000M
|__ Port 6: Dev 2, If 4, Class=Vendor Specific Class, Driver=, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 4: Dev 7, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 2: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 12, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 3: Dev 12, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 3: Dev 12, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 9, If 2, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 1: Dev 9, If 0, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 1: Dev 9, If 3, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 9, If 1, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 11: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 11, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 10, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 12: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 12M
usb2:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M
|__ Port 6: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 6: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 6: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 5000M
|__ Port 6: Dev 2, If 3, Class=Human Interface Device, Driver=usbhid, 5000M
|__ Port 6: Dev 2, If 4, Class=Vendor Specific Class, Driver=, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 4: Dev 7, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 2: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 12, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 3: Dev 12, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 3: Dev 12, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 9, If 2, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 1: Dev 9, If 0, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 1: Dev 9, If 3, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 9, If 1, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 10: Dev 20, If 0, Class=Vendor Specific Class, Driver=rtw_8812au, 480M
|__ Port 11: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 11, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 10, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 12: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 12M
from 8812au-20210820.
Jake-Grafton
commented on June 29, 2024
The rtw8812au driver works flawlessly with my (previously useless) ALFA AWUS036ACH!
Monitor mode works! (see screenshot)
The driver also works with USB 3 and USB 2.
USB 3 Port:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtw_8812au, 5000M
USB 2 Port:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 7, If 0, Class=Vendor Specific Class, Driver=rtw_8812au, 480M
from 8812au-20210820.
kikitte
commented on June 29, 2024
Finally we get the kernel driver! Thank you!
Model: ALFA AWUS036ACH
- USB3 & USB2 works good.
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
|__ Port 001: Dev 002, If 0, Class=Vendor Specific Class, Driver=rtw_8812au, 5000M
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 480M
|__ Port 006: Dev 002, If 0, Class=Vendor Specific Class, Driver=[none], 12M
|__ Port 006: Dev 002, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 007: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 002: Dev 004, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 002: Dev 004, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 009: Dev 006, If 0, Class=Vendor Specific Class, Driver=rtw_8812au, 480M
- Monitor mode works with aircrack-ng but not working with hcxdumptool
UPDATE: Monitor mode works with aircrack-ng but not working with hcxdumptool, I am using the wrong command to test hcxdumptool.
- **A lot of WARNING shows in dmeg**
A full log can be checked in [dmesg.txt](https://github.com/user-attachments/files/15957007/dmesg.txt).
from 8812au-20210820.
Redditor247
commented on June 29, 2024
Currently working with this driver. Installed correctly, but can't get this to go into monitor mode for whatever reason. Card being used is an Alfa AWUS036ACH, realtek 8812au driver.
sudo ip link set wlan1 down
sudo iw wlan1 set monitor none
command failed: Operation not supported (-95)This will connect to Wi-Fi and hold a connection fine, but monitor mode will error out.
UPDATE: tried a clean install of the experimental driver and nothing. Going to keep trying and update as able.
from 8812au-20210820.
kikitte
commented on June 29, 2024
@kikitte Someone sent a fix for those warnings: https://lore.kernel.org/linux-wireless/[email protected]/
@Jake-Grafton What is the application in your screenshot?
About monitor mode, may be something went wrong in my system, it is not related to this driver, Intel AX200 also not working with hcxdumptool but I can conform it works a few days ago
UPDATE: Monitor mode works with aircrack-ng but not working with hcxdumptool. I am using the wrong command to test hcxdumptool.
from 8812au-20210820.
Jake-Grafton
commented on June 29, 2024
@Jake-Grafton What is the application in your screenshot?
hcxdumptool, as it is vastly superior to the aircrack-ng suite.
from 8812au-20210820.
morrownr
commented on June 29, 2024
The author of hcxdumptool is @ZerBea . He was helping with the testing of 8821/11au. He can likely answer questions about hcxdumptool if you have any. We may need to see if anyone has an extra 8812au based adapter that we can get into his hands. Unfortunately I only have one 8812au based adapter or I would get one in the mail to him today.
from 8812au-20210820.
ZerBea
commented on June 29, 2024
@morrownr
No need to send a device, according to this screen shots, hcxdumptool is working as expected:
ZerBea/hcxdumptool#458 (comment)
BTW:
Don't worry about the 160 packets dropped by kernel.
Running monitor mode and interacting with the targets (APs andCLIENTs) places very high demands on the hardware. As a result, some packets are dropped by the kernel.
I'll order this adapter:
https://www.reichelt.de/de/en/usb-3-0-dual-band-wlan-mini-stick-867-mbps-delock-12502-p208115.html?GROUPID=5839&START=0&OFFSET=16&SID=929bb67fe740d35447714c48cdad3a0042274c665a29e76c30d98&LANGUAGE=EN&&r=1
According to Delock, it should be a RTL8812AU based one:
https://www.delock.de/produkt/12502/merkmale.html?setLanguage=en
There is no need to run hcxdumptool on high TX power devices.
ZerBea/hcxdumptool#419
from 8812au-20210820.
castillofrancodamian
commented on June 29, 2024
@morrownr The sudo sh remove-driver.sh command to uninstall the driver is not working. I restart the PC and still see networks in network manager.
from 8812au-20210820.
alkisg
commented on June 29, 2024
How about this?
sudo rm /lib/modules/6.9.6-arch1-1/updates/dkms/8812au.ko.zst
sudo depmod -a
reboot
from 8812au-20210820.
sisi399
commented on June 29, 2024
I've noticed there's ongoing development of a mac80211 driver for the RTL8812AU chip. As someone who's been following this topic casually, I'm hoping for some insights:
-
Can someone explain the recent developments in layman's terms? What significant changes have occurred?
-
Historical context: In the past, many issues with RTL8812AU-based devices were attributed to Realtek not releasing mac80211-compatible source code. Has this situation changed?
-
What prompted this development? Did Realtek change their policy and release source code, or is this an independent effort?
-
I've seen mentions of a developer named "lwfinger" in relation to this project. Are they affiliated with Realtek, or are they an independent contributor?
-
Was developing a mac80211 driver always technically feasible, and the delay was due to a lack of developer expertise or interest? Or were there genuine technical or legal barriers that have only recently been overcome?
I've attempted to research these questions independently but haven't found comprehensive answers. As a novice in this field, I'd greatly appreciate any insights from those more knowledgeable about the situation.
Thank you for any information or clarification you can provide!
from 8812au-20210820.
morrownr
commented on June 29, 2024
Hi @sisi399
I've noticed there's ongoing development of a mac80211 driver for the RTL8812AU chip.
You are at the right place. Read message one in this thread for instructions on how to test.
I've seen mentions of a developer named "lwfinger" in relation to this project. Are they affiliated with Realtek, or are they an independent contributor?
Larry Finger passed away last Friday. RIP Larry. He will be greatly missed but we are trying to carry on without him. We are still using his rtw88 repo to do the work. @dubhater and I have the appropriate rights to use the site.
I am really busy right now so maybe we can get to more of your questions later. Right now, we need testers so please read the first message in thread and consider helping us by testing.
Regards,
from 8812au-20210820.
dubhater
commented on June 29, 2024
AP mode should work now.
I also enabled power saving. @castillofrancodamian You will be disappointed:
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=125 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=147 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=170 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=295 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=113 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=32.2 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=158 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=76.6 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=201 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=18.3 ms
As far as I can tell, it's because of the way rtw88 decides when to enter power saving and for how long. The official driver makes those decisions differently. Something to ask Ping-Ke about...
from 8812au-20210820.
ZerBea
commented on June 29, 2024
@dubhater
Does this mean that the nl80211 message "NL80211_PS_DISABLED" addressed to "NL80211_ATTR_PS_STATE" will be ignored in monitor mode too?
from 8812au-20210820.
dubhater
commented on June 29, 2024
Is that the same as running iw wlp3s0f3u2 set power_save off ? I don't think rtw88 is ignoring it.
from 8812au-20210820.
ZerBea
commented on June 29, 2024
Thanks for that information.
Yes, it is the same - monitored by nlmon & Wireshark:
$ sudo iw dev wlp48s0f4u2u4 set power_save off
Frame 232: 52 bytes on wire (416 bits), 52 bytes captured (416 bits) on interface nlmon0, id 0
Linux netlink (cooked header)
Linux Generic Netlink protocol
Linux 802.11 Netlink
Attribute: NL80211_ATTR_IFINDEX
Len: 8
Type: 0x0003, NL80211_ATTR_IFINDEX (3)
Attribute Value: 0x00000003 (3)
Attribute: NL80211_ATTR_PS_STATE
Len: 8
Type: 0x005d, NL80211_ATTR_PS_STATE (93)
Attribute Value: NL80211_PS_DISABLED (0)
Frame 233: 52 bytes on wire (416 bits), 52 bytes captured (416 bits) on interface nlmon0, id 0
Linux netlink (cooked header)
Netlink message
Netlink message header (type: Error)
Error code: Success (0)
Netlink message header (type: 0x0024)
nlmon in combination with Wireshark is a powerful instrument to debug NETLINK.
Unfortunately we can't trust it 100%. Some drivers report success but ignore the command.
from 8812au-20210820.
castillofrancodamian
commented on June 29, 2024
AP mode should work now.
I also enabled power saving. @castillofrancodamian You will be disappointed:
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=125 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=147 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=170 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=295 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=113 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=32.2 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=158 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=76.6 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=201 ms 64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=18.3 msAs far as I can tell, it's because of the way rtw88 decides when to enter power saving and for how long. The official driver makes those decisions differently. Something to ask Ping-Ke about...
But from what I understand, that behavior is correct (using an Android phone as reference). What I reported in the past is not the same as the ping you see. In my case there were interruptions in the use of the internet via Wi-Fi, not now.
Maybe what was happening to me was a power saving mode that was not working correctly. In addition, it had other problems, such as complete disconnections from a Wi-Fi network. I no longer notice any of the problems I noticed with the previous controller.
I also notice that enabling and disabling the power saving mode works.
[franco@pc ~]$ ping mr70x.lan -c 30
PING mr70x.lan (192.168.40.1) 56(84) bytes of data.
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=1 ttl=64 time=2.16 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=2 ttl=64 time=77.4 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=3 ttl=64 time=408 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=4 ttl=64 time=2.55 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=5 ttl=64 time=2.54 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=6 ttl=64 time=373 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=7 ttl=64 time=191 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=8 ttl=64 time=2.84 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=9 ttl=64 time=2.46 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=10 ttl=64 time=2.49 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=11 ttl=64 time=2.48 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=12 ttl=64 time=30.3 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=13 ttl=64 time=667 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=14 ttl=64 time=2.66 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=15 ttl=64 time=2.38 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=16 ttl=64 time=190 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=17 ttl=64 time=212 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=18 ttl=64 time=2.85 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=19 ttl=64 time=2.21 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=20 ttl=64 time=2.31 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=21 ttl=64 time=2.49 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=22 ttl=64 time=324 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=23 ttl=64 time=348 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=24 ttl=64 time=371 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=25 ttl=64 time=190 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=26 ttl=64 time=3.58 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=27 ttl=64 time=2.40 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=28 ttl=64 time=258 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=29 ttl=64 time=282 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=30 ttl=64 time=306 ms
--- mr70x.lan ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29034ms
rtt min/avg/max/mdev = 2.164/142.199/667.424/173.980 ms
[franco@pc ~]$ sudo iw wlan0 set power_save off
[franco@pc ~]$ ping mr70x.lan -c 30
PING mr70x.lan (192.168.40.1) 56(84) bytes of data.
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=1 ttl=64 time=2.13 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=2 ttl=64 time=2.61 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=3 ttl=64 time=2.90 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=4 ttl=64 time=2.26 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=5 ttl=64 time=3.80 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=6 ttl=64 time=2.01 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=7 ttl=64 time=2.41 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=8 ttl=64 time=2.05 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=9 ttl=64 time=2.23 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=10 ttl=64 time=1.97 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=11 ttl=64 time=2.29 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=12 ttl=64 time=2.04 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=13 ttl=64 time=2.39 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=14 ttl=64 time=2.92 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=15 ttl=64 time=2.26 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=16 ttl=64 time=2.07 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=17 ttl=64 time=2.25 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=18 ttl=64 time=2.13 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=19 ttl=64 time=2.36 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=20 ttl=64 time=2.17 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=21 ttl=64 time=2.18 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=22 ttl=64 time=1.97 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=23 ttl=64 time=3.46 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=24 ttl=64 time=2.14 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=25 ttl=64 time=2.43 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=26 ttl=64 time=3.58 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=27 ttl=64 time=2.39 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=28 ttl=64 time=2.30 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=29 ttl=64 time=1.93 ms
64 bytes from mr70x.lan (192.168.40.1): icmp_seq=30 ttl=64 time=2.29 ms
--- mr70x.lan ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29040ms
rtt min/avg/max/mdev = 1.928/2.395/3.796/0.468 ms
from 8812au-20210820.
dubhater
commented on June 29, 2024
In my case there were interruptions in the use of the internet via Wi-Fi, not now.
Oh, I didn't remember that.
In addition, it had other problems, such as complete disconnections from a Wi-Fi network. I no longer notice any of the problems I noticed with the previous controller.
More bad news: I have interruptions in the use of the internet. For example, sometimes NetworkManager can't reach ping.archlinux.org for many seconds. If I move the RTL8812AU into a particular position, it stops receiving beacons and gets disconnected from the AP. The distance is about 3 meters, with no obstacles. The AP is on channel 48. The 2.4 GHz band seems better.
I didn't use the official driver long enough to see if it has the first problem, but I did reproduce the second problem with it. It has some code which tries to fix it, doesn't succeed entirely.
from 8812au-20210820.
aikawayataro
commented on June 29, 2024
Is this the right place for a status report 😅?
Im running rtw88 with my AWUS036ACH right now and it works pretty well!
I've made an Arch Linux package for this driver with firmware included, you can find it here (it's "fixed" cuz there's already an rtw88 package, but it's unmaintained).
I will be running it for some time and will report any problems I encounter, thank you!
from 8812au-20210820.
morrownr
commented on June 29, 2024
Is this the right place for a status report 😅?
Yes
Im running rtw88 with my AWUS036ACH right now and it works pretty well!
Nice adapter. I have one.
I've made an Arch Linux package for this driver with firmware included...
I'm trying to think about whether putting rtw88 (the one we are using, not mainline) up on AUR is going to have the effect that you are intending. Are AUR users going to know to report problems here? If AUR users post issues at lwfinger/rtw88, I'm not sure that anyone is currently monitoring issues there. The owner, Larry Finger, passed away last week. Dubhater and I do have the rights to change the code at the site but you really don't want us handling the administrator chores as we are shorthanded anyway. It was 3 person team and now it is 2. What might work better is for you to make a post in the appropriate Arch forum that has a link to this issue and instructions to read message 1. Also, make it clear this is about testing rtl8812au based adapters. Things can get really complicated quickly and we really need to try to avoid that if we can.
Looking forward to your 8812au report.
from 8812au-20210820.
aikawayataro
commented on June 29, 2024
Are AUR users going to know to report problems here? If AUR users post issues at lwfinger/rtw88, I'm not sure that anyone is currently monitoring issues there.
Of course, I will leave a comment about 8812au testing with proper place for reports, sorry.
Things can get really complicated quickly and we really need to try to avoid that if we can.
I believe there won't be this kind of problem, I only posted this package link here in my comment and I doubt it will spread much.
My deepest condolences on Larry's passing. He has truly impacted wireless Linux.
from 8812au-20210820.
morrownr
commented on June 29, 2024
My deepest condolences on Larry's passing. He has truly impacted wireless Linux.
He will be missed.
Where is your report?
from 8812au-20210820.
castillofrancodamian
commented on June 29, 2024
AP mode should work now.
I tried to try AP mode but it is not working. Is the configuration file the same as the one presented in USB-WiFi?
This file I tried:
/etc/hostapd/hostapd.conf
# /etc/hostapd/hostapd-WiFi5.conf
# Documentation: https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf
# 2022-09-25
# SSID
ssid=FDC
# PASSPHRASE
wpa_passphrase=1111111111
# Band: a = 5GHz & 6GHz (a/n/ac/ax), g = 2Ghz (b/g/n)
hw_mode=a
# Channel
channel=36
# Channel width (0 = 40 MHz. 1 = 80 Mhz)
vht_oper_chwidth=1
# VHT center channel (chan + 6)
vht_oper_centr_freq_seg0_idx=42
# Country code
country_code=AR
# Advertises the country_code and the set of allowed channels and transmit power levels
ieee80211d=1
# Enables support for 5GHz DFS channels (requires ieee80211d=1)
ieee80211h=1
# Bridge interface
###bridge=br0
# WiFi interface
interface=wlan0
# Set hostapd driver (nl80211 is used with all Linux mac80211 (in-kernel) and modern Realtek drivers)
driver=nl80211
#ctrl_interface=/var/run/hostapd
#ctrl_interface_group=0
# Various settings
#beacon_int=100
#dtim_period=2
#max_num_sta=32
macaddr_acl=0
#rts_threshold=2347
#fragm_threshold=2346
#send_probe_response=1
# Security
# auth_algs=3 is required for WPA3-SAE and WPA3-SAE Transition mode
auth_algs=1
ignore_broadcast_ssid=0
# wpa=2 is required for WPA2 and WPA3 (read the docs)
wpa=2
rsn_pairwise=CCMP
# only one wpa_key_mgmt= line should be active.
# wpa_key_mgmt=WPA-PSK is required for WPA2-AES
wpa_key_mgmt=WPA-PSK
# wpa_key_mgmt=SAE WPA-PSK is required for WPA3-SAE Transition mode
#wpa_key_mgmt=SAE WPA-PSK
# wpa_key_mgmt=SAE is required for WPA3-SAE
#wpa_key_mgmt=SAE
#wpa_group_rekey=1800
# ieee80211w=1 is required for WPA3-SAE Transition mode
# ieee80211w=2 is required for WPA3-SAE
#ieee80211w=1
# if parameter is not set, 19 is the default value.
#sae_groups=19 20 21 25 26
# sae_require_mfp=1 is required for WPA3-SAE Transition mode
#sae_require_mfp=1
# if parameter is not 9 set, 5 is the default value.
#sae_anti_clogging_threshold=10
# Note: Capabilities can vary even between adapters with the same chipset.
#
# Note: Only one ht_capab= line and one vht_capab= should be active. The
# content of these lines is determined by the capabilities of your adapter.
#
# IEEE 802.11n
ieee80211n=1
wmm_enabled=1
#
# generic setting
###ht_capab=[HT40+][HT40-][SHORT-GI-20][SHORT-GI-40]
#
# mediatek chipsets
# mt7612u - mt7610u
#ht_capab=[HT40+][HT40-][GF][SHORT-GI-20][SHORT-GI-40]
# mt7921au
##ht_capab=[LDPC][HT40+][HT40-][GF][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935]
#
# realtek chipsets
# rtl8812au - rtl8811au - rtl8811cu
ht_capab=[HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][MAX-AMSDU-7935]
# rtl8812bu
#ht_capab=[LDPC][HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][MAX-AMSDU-7935]
# rtl8814au
#ht_capab=[LDPC][HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][MAX-AMSDU-7935][DSSS_CCK-40]
#
# IEEE 802.11ac
ieee80211ac=1
#
# generic setting
###vht_capab=[SHORT-GI-80]
#
# mt7610u
#vht_capab=[SHORT-GI-80][MAX-A-MPDU-LEN-EXP3][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN]
# mt7612u
#vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][MAX-A-MPDU-LEN-EXP3][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN]
# mt7921au (VHT Cap. 339071b2)
#vht_capab=[MAX-MPDU-11454][RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][SU-BEAMFORMEE][BF-ANTENNA-4][MAX-A-MPDU-LEN-EXP7][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN]
#
# rtl8812au - rtl8812bu
vht_capab=[MAX-MPDU-11454][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][HTC-VHT][MAX-A-MPDU-LEN-EXP7]
# rtl8814au
#vht_capab=[MAX-MPDU-11454][RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][HTC-VHT][MAX-A-MPDU-LEN-EXP7]
# rtl8811au
#vht_capab=[MAX-MPDU-11454][SHORT-GI-80][RX-STBC-1][HTC-VHT][MAX-A-MPDU-LEN-EXP7]
# rtl8811cu
#vht_capab=[MAX-MPDU-11454][SHORT-GI-80][HTC-VHT][MAX-A-MPDU-LEN-EXP7]
#
# Note: [TX-STBC-2BY1] may cause problems with some Realtek drivers
# end of hostapd-WiFi5.conf
[franco@pc ~]$ iw dev
phy#0
Interface wlan0
ifindex 3
wdev 0x1
addr 7a:b5:c2:b7:66:c8
ssid FDC
type AP
channel 36 (5180 MHz), width: 80 MHz, center1: 5210 MHz
txpower 17.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0
from 8812au-20210820.
aikawayataro
commented on June 29, 2024
Where is your report?
Originally I just meant a status report that it's working fine.
But now, after using it for a while, I encountered a problem. After some time the wifi connection becomes unstable but still works, I just get a connection timeouts and it goes back to "normal" after a few seconds. The "broken" phase will return after some time, interval I've noticed is close to 10 minutes (sometimes it's longer).
Just unplugging wifi solves the problem for me. Interesting, but it stops working almost 4800 seconds after I plug it. (I observed this delay twice). During unstable wifi, my kernel log is spammed with these messages ([12122.732596] connected the device, [16932.148366] wifi issue begins):
[12122.732596] usb 4-4: reset SuperSpeed USB device number 5 using xhci_hcd
[12130.211073] rtw_8812au 4-4:1.0: Firmware version 52.14.0, H2C version 0
[12130.254278] 00000000: 29 81 0b 86 0c 00 00 00 02 00 00 00 00 00 00 00 )...............
[12130.254285] 00000010: 15 14 14 15 15 15 1b 1b 1b 1b 1b ee ee e0 ff ff ................
[12130.254287] 00000020: ff ff 23 20 1f 1d 21 21 22 22 24 24 28 29 27 2a ..# ..!!""$$()'*
[12130.254289] 00000030: fe ee ff ff ee ff 00 ee ff ff 17 15 14 13 13 13 ................
[12130.254291] 00000040: 1b 1b 1a 1a 1a 0e ee e0 ff ff ff ff 24 23 22 22 ............$#""
[12130.254292] 00000050: 24 20 1e 1a 19 18 1b 1e 1f 21 ed ee ff ff ee ff $ .......!......
[12130.254293] 00000060: 00 ee ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[12130.254295] 00000070: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[12130.254296] 00000080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[12130.254297] 00000090: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[12130.254298] 000000a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[12130.254300] 000000b0: ff ff ff ff ff ff ff ff 7f 1c 27 00 33 88 00 88 ..........'.3...
[12130.254301] 000000c0: 00 00 00 10 00 00 00 55 00 ff 03 ff ff ff ff ff .......U........
[12130.254303] 000000d0: da 0b 12 88 41 66 42 00 00 00 00 00 00 09 03 52 ....AfB....{...R
[12130.254304] 000000e0: 65 61 6c 74 65 6b 0d 03 38 30 32 2e 31 31 6e 20 ealtek..802.11n
[12130.254305] 000000f0: 4e 49 43 08 03 31 32 33 34 35 36 ff ff ff ff ff NIC..123456.....
[12130.254307] 00000100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[12130.254308] 00000110: ff ff ff ff ff ff ff 21 03 03 0a ff 00 ff ff ff .......!........
[12130.254309] 00000120: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[12130.254311] 00000130: 81 ae 98 2d 03 93 96 11 fc 8c 00 11 9b 78 4a ce ...-.........xJ.
[12130.254312] 00000140: e0 48 e0 70 27 00 78 ea 60 d0 e1 20 32 63 4f 3c .H.p'.x.`.. 2cO<
[12130.254314] 00000150: 12 40 92 15 8b 4a 4f 8a 15 d1 98 00 ff ff ff ff [email protected].........
[12130.254315] 00000160: ff ff ff ff ff ff ff ff 00 02 e1 63 12 29 03 00 ...........c.)..
[12130.254317] 00000170: cb 3f a0 e0 c2 f0 f7 cf 01 36 08 32 05 eb 94 d7 .?.......6.2....
[12130.254318] 00000180: 14 6d c8 67 80 e0 f8 80 30 80 30 38 ff ff ff ff .m.g....0.08....
[12130.254319] 00000190: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[12130.254321] 000001a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[12130.254322] 000001b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[12130.254323] 000001c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[12130.254324] 000001d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[12130.254326] 000001e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[12130.254327] 000001f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
...
[16932.148366] rtw_8812au 4-4:1.0: failed to get tx report from firmware
[16954.842707] rtw_8812au 4-4:1.0: failed to get tx report from firmware
[16977.003793] rtw_8812au 4-4:1.0: failed to get tx report from firmware
[16999.591275] rtw_8812au 4-4:1.0: failed to get tx report from firmware
[17021.965408] rtw_8812au 4-4:1.0: failed to get tx report from firmware
[17044.446098] rtw_8812au 4-4:1.0: failed to get tx report from firmware
[17066.633808] rtw_8812au 4-4:1.0: failed to get tx report from firmware
[17088.820528] rtw_8812au 4-4:1.0: failed to get tx report from firmware
[17111.197898] rtw_8812au 4-4:1.0: failed to get tx report from firmware
[17133.278251] rtw_8812au 4-4:1.0: failed to get tx report from firmware
[17155.888865] rtw_8812au 4-4:1.0: failed to get tx report from firmware
[17177.969160] rtw_8812au 4-4:1.0: failed to get tx report from firmware
[17200.716225] rtw_8812au 4-4:1.0: failed to get tx report from firmware
Previous driver I used was https://github.com/aircrack-ng/rtl8812au but sometimes required me to replug my wi-fi after startup and works flawlessly after that (It got broken after recent commit and they ignore user reports so I decided to give rtw88 a shot).
from 8812au-20210820.
morrownr
commented on June 29, 2024
I tried to try AP mode but it is not working. Is the configuration file the same as the one presented in USB-WiFi?
The settings for AP mode are different for rtw_8821au than for 8821au (the vendor driver) so I expect that to be the case with this driver also. I had not tested AP mode yet for this driver since Dubhater said it was not working but now I'll take a look and will post what I find.
from 8812au-20210820.
dubhater
commented on June 29, 2024
@aikawayataro "failed to get tx report from firmware" is caused by the power saving. They are about 22 seconds apart. It's strange that it's so regular.
from 8812au-20210820.
morrownr
commented on June 29, 2024
hostapd.conf settings for rtw_8812au:
ht_capab=[HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][MAX-AMSDU-7935]
vht_capab=[MAX-MPDU-11454][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMEE][HTC-VHT]
Things to keep in mind:
-
The settings above are based on what the driver says it can do and not me actually testing the settings. I will test but have not had time yet,
-
Interestingly enough, rtw_8821au actually shows more capability than rtw_8812au. This is not what I am used to seeing with AC600 vs. AC1200.
-
If the settings do not work, report what you find. rtw88 (mainline) does not have a good track record for supporting what it says it supports but this driver is an add on and I have been following exactly what it is depending on for core support. You are the first tester of AP mode in this driver.
from 8812au-20210820.
morrownr
commented on June 29, 2024
FYI: The above setting are for band 2 (5 GHz). If you need band 1 settings, let me know.
from 8812au-20210820.
morrownr
commented on June 29, 2024
Bug report:
Debian 12 with kernel 6.6
Country code: US
I am seeing the following for rtw_8812au, which is not correct:
5720 MHz [144] (disabled)
In the same machine, the mt7922 PCIe adapter is showing the following, which is correct:
5720 MHz [144] (24.0 dBm) (radar detection)
Is the rtw_8812au driver using info from the eeprom? At one time, several years ago, the disabled reading would have been correct but that channel has been allowed for several years now in the US.
from 8812au-20210820.
aikawayataro
commented on June 29, 2024
@aikawayataro "failed to get tx report from firmware" is caused by the power saving. They are about 22 seconds apart. It's strange that it's so regular.
I was too amazed at how regular the interval is. Sometimes it's not 22 seconds, but 12 or even 15 (varies between replugs). The more interesting part is that this behavior always starts 4800 seconds after I plugged it in. I will play with the power for a bit to confirm, thank you.
from 8812au-20210820.
Related Issues (20)
- Need help updating the Tested Linux Distributions section of README.md
- LED control HOT 5
- AP mode issues go here HOT 5
- Wi-Fi Direct (p2p) mode issues go here (need testers and reports, please help) HOT 2
- IBSS (ad-hoc) mode issues go here (need testers and reports, please help)
- WPA3 support HOT 8
- 5 GHz AP with 80 MHz HOT 23
- Documentation - README.md, FAQ.md and 8812au.conf (discussion and recommendations go here) HOT 4
- (info) Problem Reporting Guidelines - Please Read Before Posting an Issue. HOT 3
- (info) This repo does not support the 8811au or 8821au chipsets (AC600) - Please Read Before Posting an Issue.
- ALFA AWUS036ACH not working in USB3.0 mode on 2.4Ghz networks HOT 13
- raspberry pi 5 os bookworm? HOT 50
- Missing device ID HOT 3
- Confirmed Archer T4UH v2
- Driver not building HOT 1
- Any ideas on how to set the ibss mode? HOT 2
- Supported Driver HOT 7
- Monitor mode doesn't work (AWUS036ACH v2) HOT 17
- 4addr(AP/VLAN) modes HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from 8812au-20210820.