You are not logged in.
Hi,
I bought an Edimax EW-7822UAC adapter and it doesn't seem to work reliably with HostAPD.
I am using this driver: https://github.com/abperiasamy/rtl8812AU_8821AU_linux
It compiled and installed correctly.
Once the device is plugged in, hostapd is able to start properly, and clients can connect, but after some time (~1 minute) or if hostapd is restarted meanwhile, the wireless network disappears and does not appear until the device is reattached. Everything seems to be functioning correctly, only that the network is not visible. I know that this adapter is capable of 802.11ac, and the most that I have as clients to use to connect is 802.11n, but HostAPD was not configured to use ac, and during the initial instances, the network was visible and functional.
I tested with various HostAPD configurations, but all experienced the same symptoms.
I haven't tested the adapter on Windows.
So, could it be the driver (the official driver does not compile)? Or the device itself?
Is anyone else experiencing such an issue?
Could this be possibly fixed?
Thank you.
Last edited by AGT (2014-10-13 00:44:45)
Offline
I actually bought two of these adapters.
Now, I am using them on two different computers, both 64-bit, versus the original 32-bit one.
One of them (ASRock H61M-DGS) works, but the other (Biostar H61MGC) does not:
I should note that the machine which this adapter is not working on, I was previously using a Linksys WUSB600N on it (now replacing it). I noticed that it was not working sometimes, after running for a few days: the wireless network would disappear (the hostapd service would continue running); restarting the hostapd service would make the network reappear. I think that there might be an issue with this older adapter (because I cannot connect to a network with it; I can only broadcast a network), but I am not certain that is has something to do with the malfunctioning of this newer one.
When I start the hostapd service, it works for a few seconds, but then it crashes.
Here is what dmesg says:
systemd-udevd[32689]: renamed network interface wlan0 to wlp0s29u1u5
IPv6: ADDRCONF(NETDEV_UP): wlp0s29u1u5: link is not ready
device wlp0s29u1u5 entered promiscuous mode
device wlp0s29u1u5 left promiscuous mode
br3: port 1(wlp0s29u1u5) entered disabled state
RTL871X: nolinked power save enter
IPVS: Creating netns size=2048 id=1
IPVS: Creating netns size=2048 id=2
perf interrupt took too long (2502 > 2495), lowering kernel.perf_event_max_sample_rate to 50100
IPv6: ADDRCONF(NETDEV_UP): wlp0s29u1u5: link is not ready
RTL871X: nolinked power save leave
RTL871X: nolinked power save enter
RTL871X: nolinked power save leave
RTL871X: nolinked power save enter
RTL871X: nolinked power save leave
IPv6: ADDRCONF(NETDEV_UP): wlp0s29u1u5: link is not ready
device wlp0s29u1u5 entered promiscuous mode
device wlp0s29u1u5 left promiscuous mode
br3: port 1(wlp0s29u1u5) entered disabled state
RTL871X: nolinked power save enterBecause of the line "RTL871X: nolinked power save enter", I tried disabling the power saving mode with "iwconfig wlp0s29u1u5 power off", but that did not work:
Error for wireless request "Set Power Management" (8B2C) :
SET failed on device wlp0s29u1u5 ; Operation not permitted.Then, I searched and I found http://ajitabhpandey.info/2014/09/raspb … power-off/, which I didn't try, but I tried "echo 0 > /sys/module/8812au/parameters/rtw_power_mgnt" and that worked. However, I don't think that it affected anything, because the situation was the same then, when the value was 1, as it is now, when the value is 0.
Bringing the interface up ("ip link set dev <dev> up" or "ifconfig <dev> up") also does not work, although I can scan for networks (iw <dev> scan):
> ip link set dev wlp0s29u1u5 up
> ip link show dev wlp0s29u1u5
4: wlp0s29u1u5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether 80:1f:02:f4:2a:1e brd ff:ff:ff:ff:ff:f"rfkill list" displays that the interface is enabled.
Any ideas?
Thank you.
Last edited by AGT (2014-10-12 23:32:26)
Offline
It seems that the problem was frequency overlapping.
I changed the channel from 1 to 7 and it hostapd didn't stop anymore. Also, if I leave the same channel 1, and I remove both [HT40+] and [HT40-] from "ht_capab", it also works.
I found the issue by starting hostapd from the command line instead of as a service.
Here is what it showed when the channel was left to 1 and "ht_capab" had either one of [HT40+] and [HT40-] or both.
> hostapd /etc/hostapd/hostapd.cfg -P /run/hostapd.pid
Configuration file: /etc/hostapd/hostapd.cfg
wlp0s29u1u5: interface state UNINITIALIZED->HT_SCAN
Could not set channel for kernel driver
Interface initialization failed
wlp0s29u1u5: interface state HT_SCAN->DISABLED
wlp0s29u1u5: AP-DISABLED
hostapd_free_hapd_data: Interface wlp0s29u1u5 wasn't startedHere is what it showed when the channel was set to 7 and "ht_capab" had either one of [HT40+] and [HT40-] or both.
> hostapd /etc/hostapd/hostapd.cfg -P /run/hostapd.pid
Configuration file: /etc/hostapd/hostapd.cfg
wlp0s29u1u5: interface state UNINITIALIZED->HT_SCAN
20/40 MHz operation not permitted on channel pri=7 sec=11 based on overlapping BSSes
Using interface wlp0s29u1u5 with hwaddr <MAC> and ssid "<Network Name>"
wlp0s29u1u5: interface state HT_SCAN->ENABLED
wlp0s29u1u5: AP-ENABLED Here is what it shows when the channel is left to 1 and "ht_capab" has neither one of [HT40+] or [HT40-]. Configured this way, it started normally.
> hostapd /etc/hostapd/hostapd.cfg -P /run/hostapd.pid
Configuration file: /etc/hostapd/hostapd.cfg
Using interface wlp0s29u1u5 with hwaddr <MAC> and ssid "<Network Name>"
wlp0s29u1u5: interface state UNINITIALIZED->ENABLED
wlp0s29u1u5: AP-ENABLED It seems to be working well (enough) now.
Offline