Closed crgorect closed 3 years ago
@crgorect
I am currently learning hostapd. I am nowhere near the point where I can help you explore this issue. I'll leave this issue open as this site does see a lot of traffic so maybe someone can help.
It has been a while since this issue was posted. Is this still an issue? I have learned a lot while testing and using hostapd over the last few months. While I don't have an answer for this specific issue, what I have learned is that this driver is not the best for AP mode. These are the driver/adapter combos I recommend:
mt7612u/ driver is in-kernel mt7610u/ driver is in-kernel rtl8812au/ I have a driver up on this site. It is the best Realtek Linux I have ever seen. rtl8811au/ I have a driver up on this site.
I would avoid these chipsets for AP mode applications:
rtl8812bu rtl8811cu rtl8814au
I apologize for not updating. We actually went about finishing up development and got proper addressing working and at that point after testing we did in fact get the metadata to populate correctly and can make modifications. Sorry for not posting an update right away! Thanks for your help!
Hi, I am using this driver to create an AP with WPS mode. I have populated the metadata fields and hostapd seems to believe that the beacon is being created properly. When I do an iw scan on a different pi I am picking up other devices wps data, but not that of this given AP. Ideally I would be able to get the Model Number, Serial Number, Device Type, and Device Name properly populated. On a different note that I haven't tried to investigating any insights into station count and utilization outside of WPS would be great as well. Example scan is here iw-scan.txt.