[Prism54-users] Getting stuck when out of range

Claas Hilbrecht claas+maillinglists.prism54-users@jucs-kramkiste.de
Wed, 02 Jun 2004 11:18:37 +0200


--Am Mittwoch, 2. Juni 2004 09:24 +0200 Feyd <feyd@seznam.cz> schrieb:

> What does dmesg and iwevent on both ap (or an equivalent there) and client
> say when it happens?

This is the iwevent output. dmesg says nothing about the wireless 
connection. Only the driver reload on fli4l is recorded (as posted before). 
greebo is the AP, fli4l is the client.

greebo 2.1.7 # /boot/iwevent
Waiting for Wireless Events...
09:14:18.666039    eth3     Custom driver event:Disassociate request from 
00:04:E2:64:9F:37  (08)
09:14:18.925600    eth3     Custom driver event:Authenticate request from 
00:04:E2:64:9F:37  : ACCEPTED  (00)
09:14:19.437202    eth3     Custom driver event:Authenticate request from 
00:04:E2:64:9F:37  : ACCEPTED  (00)
09:14:19.438228    eth3     Custom driver event:Authenticate request from 
00:04:E2:64:9F:37  : ACCEPTED  (00)
09:14:20.720677    eth3     Custom driver event:Authenticate request from 
00:04:E2:64:9F:37  : ACCEPTED  (00)
09:14:21.232242    eth3     Custom driver event:Authenticate request from 
00:04:E2:64:9F:37  : ACCEPTED  (00)
09:14:21.233269    eth3     Custom driver event:Authenticate request from 
00:04:E2:64:9F:37  : ACCEPTED  (00)
09:14:23.827701    eth3     Custom driver event:Authenticate request from 
00:04:E2:64:9F:37  : ACCEPTED  (00)
09:14:23.832415    eth3     Custom driver event:Authenticate request from 
00:04:E2:64:9F:37  : ACCEPTED  (00)
09:14:23.833846    eth3     Custom driver event:Associate request from 
00:04:E2:64:9F:37  : ACCEPTED  (00)
09:14:23.835005    eth3     Custom driver event:Associate request from 
00:04:E2:64:9F:37  : ACCEPTED  (00)

fli4l 2.1.7 # /boot/iwevent
Waiting for Wireless Events...
09:14:22.005131    eth2     Custom driver event:Authenticate request to 
00:04:E2:64:9F:4F  : REJECTED  (10)
09:14:22.924208    eth2     Custom driver event:Link lost
09:14:23.800097    eth2     Custom driver event:Authenticate request to 
00:04:E2:64:9F:4F  : REJECTED  (10)
09:14:26.400985    eth2     Custom driver event:Authenticate request to 
00:04:E2:64:9F:4F  : ACCEPTED  (00)
09:14:26.403631    eth2     Custom driver event:Associate request to 
00:04:E2:64:9F:4F  : ACCEPTED  (00)
09:14:26.404377    eth2     New Access Point/Cell address:00:04:E2:64:9F:4F

-- 
 Claas Hilbrecht
 http://www.jucs-kramkiste.de