[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#760712: WEP vs WPA2



Cyril Brulebois <kibi@debian.org> (2014-09-14):
> So, putting my laptop installation aside, and concentrating on a VM
> using KVM with USB pass-through to a USB adapter (USB ID is 0bda:8176,
> that's RTL8188CUS), I've been able to verify (assuming firmwares have
> been made available every time):
>  - wheezy amd64 works with WPA (TKIP) and WPA2 (AES)
>    [ sharing network over a Firefox OS phone with those denominations. ]
>  - wheezy amd64 works with WPA2-PSK/AES
>    [ as advertised by my home router ]
>  - sid amd64 doesn't work with any of those, even if I build an image
>    with wheezy's netcfg and/or wheezy's wpasupplicant-udeb.
> 
> I've also verified that installing over a wired connection lets me
> configure wpa_supplicant and connect to wireless from within the same
> VM, so there's definitely something fishy within d-i, even if I don't
> know what yet.
> 
> Anyway, that doesn't allow me to conclude on the “WEP might be OK”
> topic, but various WPA setups are clearly broken. Let's see whether I
> can get that debugged further tomorrow.

With some flexible value of "tomorrow", it seems I can conclude the
problem is rather on the kernel side than on the userland side. It isn't
too surprising since I had already tested downgrading netcfg and wpa to
wheezy's versions, and that didn't help.

My cross tests were done using:
 - wheezy or sid as a basis
times:
 - 3.2 or 3.16 linux udebs

building a netboot-gtk image in the appropriate chroot (wheezy or sid).

I also included all the firmware files included in the firmware-realtek
package from wheezy (for 3.2) or from sid (for 3.16) to take that out of
the picture.

End results:
 - wheezy and sid with 3.2 work
 - wheezy and sid with 3.16 don't work (card recognized, scanning OK
   but association KO).

I've also checked that installing sid + 3.16 over Ethernet then manually
connecting (wpa_passphrase then wpa_supplicant) worked just fine (that's
been mentioned in my previous mail, but confirming).

I'll now try and compare dmesg from within d-i and from the installed
system to see whether I can spot some differences which could help me
understand what the differences are, and possibly ask kernel maintainers
for help/insight.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


Reply to: