Hi On Monday 15 September 2014, Cyril Brulebois wrote: > Stefan Lippers-Hollmann <[email protected]> (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).
[ o.k., the following three paragraphs have been obsoleted by your
other mail ]
|As a quick test I have bind-mounted the wpa_supplicant binary from
|wpasupplicant-udeb over /sbin/wpa_supplicant of a full installation
|and successfully tested:
|
|# wpa_supplicant -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
|Successfully initialized wpa_supplicant
|wlan0: CTRL-EVENT-SCAN-STARTED
|wlan0: SME: Trying to authenticate with 01:23:45:67:89:ab (SSID='test'
freq=2472 MHz)
|wlan0: Trying to associate with 01:23:45:67:89:ab (SSID='test' freq=2472 MHz)
|wlan0: Associated with 01:23:45:67:89:ab
|wlan0: WPA: Key negotiation completed with 01:23:45:67:89:ab [PTK=CCMP
GTK=CCMP]
|wlan0: CTRL-EVENT-CONNECTED - Connection to 01:23:45:67:89:ab completed [id=4
id_str=test_aes]
|wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=DE
|wlan0: WPA: Group rekeying completed with 01:23:45:67:89:ab [GTK=CCMP]
|
|# wpa_cli status
|Selected interface 'wlan0'
|bssid=01:23:45:67:89:ab
|ssid=test
|id=4
|id_str=test_aes
|mode=station
|pairwise_cipher=CCMP
|group_cipher=CCMP
|key_mgmt=WPA2-PSK
|wpa_state=COMPLETED
|ip_address=10.20.27.0
|address=ba:98:76:54:43:21
|
|This is 802.11bgn, using WPA2PSK and CCMP (AES) encryption with an
|Atheros AR9285 (ath9k) wlan card, so relatively comparable to the
|original submitter (while I have rtl8192du, I currently don't have
|access to any wlan card supported by rtl8192cu). Accordingly the udeb
|config for wpasupplicant (at least on linux) should be fine.
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.
[...]
> > [with my wpa maintainer hat on]
> > Semi-related, I have a pending upload for wpa (wpasupplicant-udeb), can
> > you give me a rough guide when it's safe to upload in order not to
> > interfere with d-i beta2[6]? There are no behavioural changes, besides
> > many bugfixes[7]. If you want to test it for d-i, the packaging is
> > ready (besides the changelog entries) in the normal VCS location[8].
>
> Well currently, as far as I can see/test, WPA support in d-i isn't
> exactly working nicely, so I don't think a wpa upload is going to hurt
> much. Quite the contrary, hopefully.
Thanks, I'll do some final testing (and add CONFIG_DEBUG_SYSLOG=y, as
requested in your other mail) and will try to get the new version
sponsored quickly.
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
