Re: reproducible association with wrong essid, iwl3945

[Helge Hafting <helgehaf@mail.aitel.hist.no>]

Dan Williams wrote:
> On Mon, 2008-03-10 at 11:08 +0100, Helge Hafting wrote:
>   
>> Get a normal association so the network works. (WEP encryption)
>> $ iwconfig wlan0 nonexistent_essid key s:correct_key
>>
>> The network keeps working!  I would expect the driver to look
>> for an access point with the different essid, and fail
>> if no such access point exists.
>> Two different networks with the same encryption string is possible, 
>> after all.
>>     
>
> Should definitely fail, disassociate, and send the SIOCSIWAP event with
> 00:00:00:00:00:00 via wireless_send_event().
>
>   
Instead it works for hours - but if I try wireshark it
puts the interface in promiscuous mode - and sets it normal again
when the sniffing is done. Then the network dies, perhaps the
inerface state change also took the wrong essid into account. Or
maybe it just didn't like the switch from promiscuous mode.

Running with the wrong essid will sometimes cause
slow networking with lots of "too short packets" rejected.



Helge Hafting