Hi Manuel,

Manuel Gebauer wrote:

> Below is a session to demonstrate the essid-setting-problem. Look out for the
> garbled names like 'gÆisQÿJì)ͺ«òûãF|ÂTø3'. The
> ipw2200-version from kernel-source-3.0.0 in comparision did not show this
> problem.

What did the 3.0.y kernel do instead?

It looks to me like the ESSID gets reset to "intranet" once it is time to
associate. Could you further explain the symptoms and how they differ
from the expected behavior?

Can you reproduce this using wpa_supplicant directly on the command
line? (That just makes reproduction recipes a little easier to
understand.) Even better would be if you can reproduce this on a WEP
network with "ip" from the iproute package and "iw" from iw:

ip link set eth1 up
iw dev eth1 scan
iw dev eth1 connect -w <essid> key <key>
ip link set eth1 down

Full "dmesg" output from booting up an affected kernel would also be
interesting.

More hints, such as how to get an iw event log, are at [1].

Thanks and hope that helps,
Jonathan

[1] http://linuxwireless.org/en/users/Documentation/Reporting_bugs



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111224201002.GE25883@elie.Belkin">http://lists.debian.org/20111224201002.GE25883@elie.Belkin

Hi,

> What did the 3.0.y kernel do instead?

Kernel 3.0.0 does not garble the essid upon ifdown.

> It looks to me like the ESSID gets reset to "intranet" once it is time to
> associate. Could you further explain the symptoms and how they differ
> from the expected behavior?

Nagh, it's not clear to me what happens.

I did six sessions: Both with kernels 3.0.0 and 3.1.5, both with wep
and wpa, and the wpa sessions both with "low level" tools and with
ifup/ifdown. I found the iw commands were not supported -- maybe a
driver specificum or something that goes beyond the limits of my
experience.

In summary:

kernel 3.0.0, WEP, iwconfig: works
kernel 3.0.0, WPA, iwconfig: works
kernel 3.0.0, WPA, ifupdown: works
kernel 3.1.5, WEP, iwconfig: works
kernel 3.1.5, WPA, iwconfig: works!
kernel 3.1.5, WPA, ifupdown: garbeld essid problem

So in the end it looks like if the manner of ifdown to bring the
interface down somehow conflicts with the 3.1.5 version of the ipw2200
driver.

Find attached the six sessions, corresponding sylogs with iw event
enabled, dmesgs of both kernels and corresponding kernel configs.

Regards,

Manuel
--
Hintergasse 2, 37345 Silkerode
Fon: +49 36072 88982
Mobil: +49 151 58822651
IM: myops@jabber.org

Manuel Gebauer wrote:

> Kernel 3.0.0 does not garble the essid upon ifdown.

I see.

Ok, two more details:

- after you run "ifdown eth1", is the interface shown by "ip link" as
UP or DOWN? (If the latter, it seems to me that the scrambled essid
would be harmless, even if annoying.)

- what are the version numbers of the ifupdown and wpasupplicant
packages? "dpkg-query -W ifupdown wpasupplicant" should say.

[...]
> kernel 3.0.0, WEP, iwconfig: works
> kernel 3.0.0, WPA, iwconfig: works
> kernel 3.0.0, WPA, ifupdown: works
> kernel 3.1.5, WEP, iwconfig: works
> kernel 3.1.5, WPA, iwconfig: works!
> kernel 3.1.5, WPA, ifupdown: garbeld essid problem

Thanks very much for this summary and the logs.

Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111225082024.GB10805@elie.Belkin">http://lists.debian.org/20111225082024.GB10805@elie.Belkin