nl80211 on Omega2s.
I would like to used wpa_supplicant and iw for my project, but it seems that nl80211 is not supported on omega. I can not find any alternatives, and I cant find the what is the driver that omega uses.
Thanks for help!
crispyoz last edited by
@gabornagy93 May I ask what you are trying to achieve? There may be other solutions.
Omega uses Warp Core driver developed by Onion to resolve some of the issues with the OpenWrt drivers. You can build your own firmware and use the standard OpenWrt drivers, but it may not be necessary if we can understand your requirements.
Hello! That is exactly my problem. This Warp Core driver is not documented enough I think (at least I can not find a complete documentation about it). For example, I don't want my device to automatically connect/reconnect to a known network.
Is there any documentation available about this Warp Core driver?
I think, from user point of view, it should be possible to use the widely and commonly used interfaces and drivers like the mentioned nl80211.
luz last edited by
@gabornagy93 depending on your application, you could use a stock (or customized) OpenWrt build for the Omega2S, which uses the open source
mt76wifi driver built on the nl80211/cfg80211 architecture.
mt76was unreliable at the time Omega2 came out. It greatly improved over the years, and recently a company with a product based on MT7688 invested some money for getting their
mt76based product through wifi certification, making
mt76super stable and perfomant. It can also work in station (wifi client) mode without being an access point at the same time.
Of course, with stock Openwrt you would not have any of Onion's additions by default. But as the Onion openwrt package feed is open source you could add it into your openwrt build environment, and build/use those packages you'd need. Of course, things depending on the Omega proprietary driver would not work unmodified.
You could also start with the onion openwrt tree and try to replace the proprietary driver by a recent
mt76in there, but I guess that could get much more complicated than the other way around.
For my own (dozens) Omgea2 based projects with thousands of devices in the field I always used stock OpenWrt with some customisation on top. To keep my changes apart from the openwrt tree, so I don't have to fork it, I wrote a untility script that might help others, too.