Re: Getting stuck when out of range
Claas Hilbrecht <[email protected]>
| Newsgroups | gmane.linux.drivers.prism54.user |
|---|---|
| Message-ID | <59A7DC25958B342B30A38150@[192.168.1.22]> |
--Am Mittwoch, 2. Juni 2004 09:24 +0200 Feyd <[email protected]> schrieb: > What does dmesg and iwevent on both ap (or an equivalent there) and client > say when it happens? This is test with "Encryption key:off". As previously noted it takes more time to "break" the link. greebo: 09:52:56.564600 eth3 Custom driver event:Disassociate request from 00:04:E2:64:9F:37 (08) 09:52:56.824159 eth3 Custom driver event:Authenticate request from 00:04:E2:64:9F:37 : ACCEPTED (00) 09:52:56.825300 eth3 Custom driver event:Authenticate request from 00:04:E2:64:9F:37 : ACCEPTED (00) 09:53:00.030744 eth3 Custom driver event:Authenticate request from 00:04:E2:64:9F:37 : ACCEPTED (00) 09:53:00.031711 eth3 Custom driver event:Authenticate request from 00:04:E2:64:9F:37 : ACCEPTED (00) 09:53:00.032856 eth3 Custom driver event:Associate request from 00:04:E2:64:9F:37 : ACCEPTED (00) 09:53:00.033995 eth3 Custom driver event:Associate request from 00:04:E2:64:9F:37 : ACCEPTED (00) fli4l: 09:52:59.891625 eth2 Custom driver event:Authenticate request to 00:04:E2:64:9F:4F : REJECTED (10) 09:53:00.626477 eth2 Custom driver event:Link lost 09:53:02.588306 eth2 Custom driver event:Authenticate request to 00:04:E2:64:9F:4F : ACCEPTED (00) 09:53:02.590658 eth2 Custom driver event:Associate request to 00:04:E2:64:9F:4F : ACCEPTED (00) 09:53:02.591463 eth2 New Access Point/Cell address:00:04:E2:64:9F:4F -- Claas Hilbrecht http://www.jucs-kramkiste.de