[Prism54-users] Getting stuck when out of range

[Feyd]

On Wed, 02 Jun 2004 11:55:52 +0200
Claas Hilbrecht <claas+maillinglists.prism54-users@jucs-kramkiste.de> wrote:

> --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 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)

Try to increase number of retries, the firmware disassocates too soon when
the signal is weak. `iwconfig <iface> retry limit 14' seems to work best.
The only question is why it refuses to transmit when the connection was
reestablished later.

> 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

I suppose here the link broke?

Feyd