Re: 2.6.18-git9 wireless fixes break ipw2200 association to AP with WPA

[Jean Tourrilhes]

On Sat, Sep 30, 2006 at 12:04:31AM +0200, Alessandro Suardi wrote:
> On 9/29/06, Jean Tourrilhes <jt@xxxxxxxxxx> wrote:
> >>
> >> [asuardi@sandman ~]$ rpm -q wireless-tools
> >> wireless-tools-28-0.pre13.5.1
> >
> >        That's too old, the cutoff is 27-pre15.
> 
> Are you sure ? For how I read it, 28-0.pre13.5.1 is more recent
> than 27-pre15, not older.

	Sorry, I'm mixing up my numbers.
	The cutoff for the ESSID fix is 28-pre15, so your version is
just a little bit older. I'm mixing up with the iwpoint cutoff which
was 27-pre25.

> So I guess there's an actual bug that doesn't depend on the
> wireless-tools. Or maybe it's wpa_supplicant that has to be
> upgraded ?

	I don't have the start of the thread, so I don't know the
exact failure mode. If you are using wpa_supplicant, it bypasses the
wireless tools so it would have to be updated.
	Note that I've been pestering Jouni about the fact that he had
to update wpa_supplicant for that since last May, when Jouni himself
asked me to change the ESSID API. Ironic, isn't it ?
	The epitest.fi site seems unfortunately down...

> >        On the other hand, FC6, which is in beta, contains already the
> >proper version of the tools. I have been monitoring the various distro
> >in the last few months before sending those WE-21 patches, and all
> >major distro have WT-28 in the pipeline.
> 
> Even if so, wireless-tools would be the only package I have to
> build out of the FC5 distribution to keep up with the latest -git
> snapshot of the Torvalds kernel... I'm not especially troubled
> with this anyway. Perhaps you could push the Fedora folks to
> be a bit more up-to-date with wireless-tools in their current
> main version ?

	The FC people are busy.

> Still listening on how to further research the issue... many thanks
> in the meantime, ciao,
> 
> --alessandro

	Jean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/