On Mon, 2014-09-15 at 23:08 +0200, Stefan Lippers-Hollmann wrote: > Hi > > On Monday 15 September 2014, Cyril Brulebois wrote: > > Stefan Lippers-Hollmann <s.L-H@gmx.de> (2014-09-15): > [...] > > Seeing that the actual problem are missing kernel modules for > CCMP (AES), and probably TKIP as well, I'll concentrate on your > new questions only > > > Based on your answer, I'm wondering whether there might be some CONFIG_* > > differences between wpasupplicant and its udeb, which might explain? > > There are significant CONFIG_* differences between the regular > wpasupplicant and wpasupplicant-udeb, both to get it smaller and to > avoid dependencies on packages not providing udebs, but the udeb > should support: > > - no encryption > - WEP64 > - WEP128 > - WPAPSK v1 TKIP/ CCMP > - WPAPSK2 TKIP/ CCMP > > More advanced setups, like IEEE8021X (using certificates and per-user > encryption, e.g. eduroam and other commercial setups), smartcards and > are not supported by the udeb (nor would netcfg know how to configure > these). WPS would also be nice to have. [...] > This reminds me, without regulatory domain support (iw(semi-optional), > crda, wireless-regdb) only the channels allowed for world-roaming > (slightly depending on what the individual wlan drivers and firmwares > understand under world-roaming) would be available, which means channel > 1-11 (no access to 12/13) and very little, if anything, in the 5 GHz > band. I started to worry about this too. The built-in world regulatory domain allows *passive* use of channels 12-13 and other channels that are not permitted in all countries. That is, the kernel will allow passively scanning on those channels and connecting to an AP, on the assumption that the AP is following the local rules. But I'm prepared to believe that this doesn't work when using wext, or requires wext configuration to be done in a different order than netcfg and wpa_supplicant currently use. Ben. -- Ben Hutchings Make three consecutive correct guesses and you will be considered an expert.
Attachment:
signature.asc
Description: This is a digitally signed message part