Intel® Makers
Intel® Edison, Intel® Joule™, Intel® Curie™, Intel® Galileo
Welcome - This is a Peer-to-Peer Forum only. Intel has discontinued these products but you may find support from other customers on this Forum
9873 Discussions

5 GHz AP with hostapd and flexible regulatory domain

Community Manager


After being able to build the standard Yocto Image (iot-devkit-yp-poky-edison-20160606) including crda, python-m2crypto, and iw package, I will create an 5 GHz AP using hostapd.

I use hostapd with 2.4 GHz and it works fine for me.

I created the following file in /etc/udev/rules.d/regulatory.rules

KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/sbin/crda"

I can not set the regulatory domain with hostapd. So 5 GHz is not working in AP mode. I also can not set the reg domain with crda using echo COUNTRY=DE.

I can use iw to set the reg domain. It seems that this is not working correct because the domain is not set when reading the domain with crda. After a restart it is also not set in iw.

It looks that I have the same problem like mhahn seen in the thread . Could you solve that issue?



0 Kudos
3 Replies

maybe my workaround which I put in the other thread as well could help you?

"Meanwhile I rebuilt the kernel with CONFIG_CFG80211_INTERNAL_REGDB to have a solution for now. Hence I now can set the country reg via iw. Still would like to understand why crda doesn't work on my side and maybe find a success story with BKM for the Edison Yocto image"

Community Manager

Hello mhahn,

unfortunately this is no solution for me. I do need the flexibility to change the reg domain and use hostapd to configure my access point.

Community Manager

Hello Nils,



Thanks for reaching out!



I've never tried to do this with my Edison, nevertheless, I was able to find a user that was able to set a 5GHz AP in his Edison. You can find details about this in Perhaps this is of help.



Regarding the issues with the regulatory domain, I haven't been able to find anything useful. I did find this which makes the issue seem to related to either the network card driver or the kernel. However, I'm not sure if the same can be happening to Edison but I thought that it can't hurt to mention it.



I hope this information helps you,


Pedro M.