Closed jgornick closed 8 years ago
@pritambaral Any chance you've had some time to think about this issue? Thanks!
Sorry. This is not a codebase I can support. I didn't write it. (Nor do I any longer have any hardware that can make use of it. Also, don't have an iPhone.)
In the README, I mention that none of the code is created by me. The code is from Realtek, modified slightly to build against newer hostapd releases.
I left your issue up so that other users of this code may be able to help you out.
I apologize for not seeing that in the README. Thank you for the quick response!
I'm currently trying to build a hostapd 2.4 version and see if the issue exists there.
Thanks again!
Have you tried the latest linux kernel? The mainline drivers may have gotten better; last I checked, AP mode was kinda working.
Of course, the mainline driver does not need this codebase. It uses the kernel's standard mac80211 interface, so it should work with nl80211
That's my next step, but because I'm setting this up on a Raspberry Pi (raspbian), they default to using the non-mac80211 driver by default. I would just need to rebuild the kernel with the mac80211 driver instead.
I don't think the non-mac80211 driver is shipped in raspbian, is it? Perhaps you installed it from somewhere like dz0ny/rt8192cu
If an out-of-tree driver is what provides the non-mac80211 driver, then uninstalling (or even rmmod
-ing or modprobe -r
-ing) it should allow using the in-tree driver.
By default it ships with the 8192cu driver. For reference, here's an issue for moving this driver forward to the mac80211 version https://github.com/raspberrypi/linux/pull/1468
Ooh, didn't know that. Bold move, but I guess good on raspbian guys for shipping it by default.
It also looks like they are adding cfg80211 support to the 8192cu driver https://github.com/raspberrypi/linux/pull/1489/files
Hmm, that would be cool (but also redundant, perhaps, since the converse is being done with the in-kernel drivers).
I believe this issue was self-inflicted with some other configuration in my environment.
I had an if-pre-up script that was updating the wireless interface MAC address via ip link set dev "$IFACE" address ...
. I was doing this because when I have a wireless interface that supports multiple SSIDs (using the mac80211 driver), you need to set the MAC address so it allows hostapd to create the other virtual interfaces with the next available MAC.
Once I removed the ip link set...
command, I was able to successfully authenticate and connect via an iOS device. With that being said, this was probably causing an issue because hostapd was getting 2 different MAC addresses for the interface, one at the physical layer and another via the ip
layer. At least that's what I think was happening 😄
Closing the issue because it's not related to this project.
Thanks!
OS: raspbian (Kernel 4.1.17) hostapd: 2.5 Adapter: 20f4:648b TRENDnet TEW-648UBM 802.11n 150Mbps Micro Wireless N Adapter [Realtek RTL8188CUS]
I've run into a issue where my iOS devices are unable to authenticate when using the rtl871xdrv hostapd driver. If I use a different interface that uses the nl80211 hostapd driver, authentication succeeds with the same hostapd configuration. I can however successfully authenticate with my MacBook when using the rtl871xdrv driver.
hostapd/wlan0.conf
Authentication logs: