Bug#376651: [pkg-wpa-devel] Bug#376651: wrong default wpasupplicant driver (uses wired isntead of wext)

Kel Modderman kelrin at tpg.com.au
Tue Jul 4 08:22:43 UTC 2006


Reinhard Tartler wrote:
> On Tue, Jul 04, 2006 at 05:26:40AM +0200, Jacobo221 wrote:
>   
>> init_wpa_supplicant() in /etc/network/if-pre-up.d/wpasupplicant should
>> not default to "wired" when $IFACE isn't in /proc/net/wireless'
>> contents because the first time the interface is set up after a boot
>> $IFACE might not yet be in /proc/net/wireless since the wpasupplicant
>> script is run from if-pre-up.d and, therefore, the interface has never
>> yet been set up.
>>     
>
> Which network driver is this? I'd like to report a bug about this. Why
> shouldn't a driver not advertise that it handles a wireless device until
> it is 'up'?
>
>   
>> The current result here is taht, when booting uo, the first time i set
>> up the interface, it gets driver "wired". From then on, it gets "wext"
>> (which is what should always be expected).
>>     
>
> And that this behavior breaks tools like network-manager as well.
>
>   
>> The solution, of course, is to set "wpa-driver wext", but since the
>> docs say "the default is wext", either the docs are fixed, or the
>> script has to be slightly modified.
>>     
>
> No, the solution is to fix the driver.
>
>   

I agree about fixing drivers reporting their stuff to userspace.

FYI, I could easily reproduce this when activating a madwifi VAP from 
within an interfaces stanza (the interface does not have to exist before 
hand).

Plus, the grep of /proc/net/wireless is not _really_ that useful.

Kel.




More information about the Pkg-wpa-devel mailing list