On Saturday 18 November 2006 05:18, chunkeey@web.de wrote:

Am Samstag, 18. November 2006 05:27 schrieben Sie:

quoted

OK, i'll try installing kismet on another laptop. For now that's what I
have from iwevent:

[root@core ~]# cat iwevents.bad
21:30:52.185823   eth1     Set Mode:Managed

where's Set Encryption key:****-****-****-****-****-****-**   Security 
mode:restricted ? was the key set?

quoted

21:30:52.226100   eth1     Set ESSID:"ALCT76_68b"
21:30:54.505039   eth1     Authenticate request to XY [00 0D 0002]
21:30:56.300128   eth1     Authenticate request to XY [00 0D 0002]

ok, the error code is 0D (=unsupported Authentication Algorithm).

quoted

[root@core ~]# cat iwevents.good
21:50:50.575630   eth1     Set Mode:Managed
21:50:50.604998   eth1     Set Encryption
key:****-****-****-****-****-****-**   Security mode:restricted
21:50:50.616502   eth1     Set ESSID:"ALCT76_68b"
21:50:52.880361   eth1     Authenticate request to XY : [00  00 0002]
21:50:52.882638   eth1     Associate request to XY : [00 00 0002]
21:50:52.883625   eth1     New Access Point/Cell address:XY

are your wireless-tools( iwconfig, iwevent, iwlist...) up to date? they've to 
be atleast Version 21!

Hmm, something funky is going on with my hotplug scripts - if I rerun
ifup eth1 after inserting the card it associates just fine. Sorry for
the false alarm, the drivers seems to be working fine.

Still not sure why old driver does not need second "ifup"...

-- 
Dmitry