On Saturday 27 December 2008 23:08:14 Jouni Malinen wrote: > On Sat, Dec 27, 2008 at 10:08:20PM +0100, Michael Buesch wrote: > > Please take a look at the following log: > > http://bu3sch.de/misc/crda.JPG > > > > Note the ordering of the events. > > Hostapd starts up and tells the kernel what country we're in. > > Then the kernel calls CRDA, _but_ hostapd goes on with its business > > before CRDA has finished its work. > > Yes, because the netlink message was completed and hostapd assumes > everything is ready at that point. Ignoring the complexity in the kernel > (+ CRDA as a helper), this looks like reasonable expectation to make for > NL80211_CMD_REQ_SET_REG operation. There is no other mechanism that > would notify hostapd (or any other program setting country for that > matter) when the operation was actually fully completed and polling for > channel changes up to a timeout is not very appealing either. > > Unfortunately, I don't see an easy fix for this. cfg80211 would somehow > need to block sending of the NL80211_CMD_REQ_SET_REG response until CRDA > has completed doing whatever it is going to do (is that even something > that cfg80211 knows when the final step was completed?).. I haven't > taken a look at all the details, but I've asked for this kind of wait in > the past and at least it did not seem to be trivial to add since this > has not been fixed yet ;-). Ok, thanks for the explanation. For now I added a workaround to the initscript that starts hostapd which sets the regulatory and waits a seconds before starting hostapd. iw reg set DE sleep 1 # start hostapd... -- Greetings, Michael. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
