[Prism54-users] Getting stuck when out of range
Claas Hilbrecht
claas+maillinglists.prism54-users@jucs-kramkiste.de
Wed, 02 Jun 2004 14:25:38 +0200
--Am Mittwoch, 2. Juni 2004 13:24 +0200 Feyd <feyd@seznam.cz> schrieb:
> Im afraid -85dBm is too low, sensitivity for 1Mb/s is -86. I still have
> quite a lot disassociations with -70 on 2Mb/s. But the link works ok
Is there any documentation about these values?
> when it is reestablished. Try to recompile the driver with higher
> VERBOSE, may be you will find something.
I just want to grab the latest driver. But it seems that the tarball export
stops at 2004-05-28. Now I will use 2004-05-20 now.
This is what happends with VERBOSE=0x02. Note that this time the automatic
ifdown/ifup is disabled. I assume the debug level for VERBOSE is too low?
fli4l:
12:22:28.135450 eth2 Custom driver event:Authenticate request to
00:04:E2:64:9F:4F : REJECTED (10)
12:22:29.161945 eth2 Custom driver event:Link lost
12:22:29.931763 eth2 Custom driver event:Authenticate request to
00:04:E2:64:9F:4F : REJECTED (10)
12:22:31.725405 eth2 Custom driver event:Authenticate request to
00:04:E2:64:9F:4F : REJECTED (10)
12:22:45.043280 eth2 Custom driver event:Authenticate request to
00:04:E2:64:9F:4F : REJECTED (10)
12:22:46.838257 eth2 Custom driver event:Authenticate request to
00:04:E2:64:9F:4F : REJECTED (10)
12:22:48.633290 eth2 Custom driver event:Authenticate request to
00:04:E2:64:9F:4F : REJECTED (10)
12:22:50.428406 eth2 Custom driver event:Authenticate request to
00:04:E2:64:9F:4F : REJECTED (10)
12:23:02.288067 eth2 Custom driver event:Authenticate request to
00:04:E2:64:9F:4F : REJECTED (10)
12:23:05.540858 eth2 Custom driver event:Authenticate request to
00:04:E2:64:9F:4F : REJECTED (10)
12:23:07.335835 eth2 Custom driver event:Authenticate request to
00:04:E2:64:9F:4F : REJECTED (10)
12:23:09.130871 eth2 Custom driver event:Authenticate request to
00:04:E2:64:9F:4F : REJECTED (10)
12:23:10.926027 eth2 Custom driver event:Authenticate request to
00:04:E2:64:9F:4F : REJECTED (10)
Jun 2 14:21:11 fli4l kernel: Wake up handler trigger the device
Jun 2 14:22:41 fli4l kernel: TRAP: oid 0x18000001, device 20, flags 0x0
length 12
Jun 2 14:22:42 fli4l kernel: TRAP: oid 0x1, device 20, flags 0x0 length 4
Jun 2 14:22:43 fli4l kernel: TRAP: oid 0x18000001, device 20, flags 0x0
length 12
Jun 2 14:22:48 fli4l kernel: TRAP: oid 0x18000001, device 20, flags 0x0
length 12
Jun 2 14:22:48 fli4l kernel: Wake up handler trigger the device
Jun 2 14:22:57 fli4l kernel: Wake up handler trigger the device
Jun 2 14:22:58 fli4l kernel: TRAP: oid 0x18000001, device 20, flags 0x0
length 12
Jun 2 14:23:15 fli4l last message repeated 3 times
Jun 2 14:23:15 fli4l kernel: Wake up handler trigger the device
Jun 2 14:23:15 fli4l kernel: TRAP: oid 0x18000001, device 20, flags 0x0
length 12
Jun 2 14:24:12 fli4l last message repeated 4 times
Jun 2 14:24:15 fli4l kernel: Wake up handler trigger the device
Jun 2 14:24:15 fli4l kernel: TRAP: oid 0x18000001, device 20, flags 0x0
length 12
Jun 2 14:24:25 fli4l kernel: TRAP: oid 0x18000001, device 20, flags 0x0
length 12
greebo:
12:22:24.853371 eth3 Custom driver event:Disassociate request from
00:04:E2:64:9F:37 (08)
12:22:25.112956 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:25.624515 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:25.625534 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:26.907995 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:27.420685 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : REJECTED (10)
12:22:27.421290 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:27.422451 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:28.703049 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:29.214620 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:29.215645 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:42.021010 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:42.532594 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:42.533560 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:43.815992 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:44.327552 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:44.328569 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:45.611032 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:46.122595 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:46.123620 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:47.435252 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:47.917709 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:47.918696 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:49.201137 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:49.712696 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
12:22:49.713722 eth3 Custom driver event:Authenticate request from
00:04:E2:64:9F:37 : ACCEPTED (00)
--
Claas Hilbrecht
http://www.jucs-kramkiste.de