[pkg-wpa-devel] Bug#721865: Bug#721865: hostapd: regdomain updated after channel setting is performed

[Martin Hodges]

On Wednesday 04 September 2013, you wrote:
> Control: tags -1 + moreinfo
>
> Hi
>
> On Wednesday 04 September 2013, Martin Hodges wrote:
> […]
>
> > Dear Maintainer,
> > Stumbled across while migrating the home server from lenny to Wheezy.
> >
> > I live in Norway and few people use channel 13, so I do.
> >
> > Only listing modules in /etc/modules did not help.
> > In addition: Calling 'iw set reg NO' in /etc/network/interfaces under
> > section for wlan0 helped.
> >
> > when the error is present:
> > The call to CRDA seems to comes after the channel setting is performed.
> > Trying to set to CH13 before changing the country to Norway will not work
>
> […]
>
> I haven't quite understood how, and in which order, you're calling
> (explicitly or implicity be system events) crda, could you please
> clarify that a bit?
>
Sorry. 

I originally tried solely to use the 'country_code' option 
in /etc/hostapd/hostapd.conf assuming that it would take care of everything.

> What you'd usually do, is configuring CRDA:
> /etc/default/crda:
> 	REGDOMAIN=NO
>

Why would I need to?

> In addition you'd configure hostapd:
> $DEAMON_CONF (hostapd.conf):
> 	country_code=NO
>

Oh?

> Keep in mind that your kernel also receives external hints to update
> and intersect the active regulatory domain, be it by your device's
> EEPROM/ OTP (this is particularly valid for Atheros devices[1]) 

Yes. I've been down that road. I had to edit the EEPROM contents on the 
Atheros card I had been using.

I am trying to use a PCIE rt2800 card.

> or that 
> is might even receive country IEs (IEEE 802.11d) from access points
> nearby. So it is a bit hard to guess what goes wrong on your system,
> without further information. Fortunately dmesg usually tells a pretty
> good story about all regulatory hints received and how they arrived.
>
> Useful information to debug this:

> - full dmesg output since the system booted
Attached.

> - /sbin/iw reg get
country NO:
        (2402 - 2482 @ 40), (N/A, 20)
        (5170 - 5250 @ 40), (N/A, 20)
        (5250 - 5330 @ 40), (N/A, 20), DFS
        (5490 - 5710 @ 40), (N/A, 27), DFS


> - /sbin/iw list

Attached


>
> Regards
> 	Stefan Lippers-Hollmann
>
> [1]	http://wireless.kernel.org/en/users/Drivers/ath#Regulatory

The output from syslog was useful as it showed the relation between the 
loading of the wireless module, the error messages from hostapd -then the 
setting of the reg_domain of the wireless card.

Attached an excerpt concerning these events.


-- 
M
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.txt
Type: application/x-kdeuser1
Size: 57600 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-wpa-devel/attachments/20130905/845cadef/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: iw_list.txt
Type: application/x-kdeuser1
Size: 2990 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-wpa-devel/attachments/20130905/845cadef/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: syslog.txt
Type: application/x-kdeuser1
Size: 12428 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-wpa-devel/attachments/20130905/845cadef/attachment-0005.bin>