On Thu, Sep 27, 2007 at 10:35:35PM -0000, Rolla Selbak wrote:
>
> "reason 1" is AP specific so only the AP develop know what this error mean. But looking at the log I see Txpower error and it might need more investigation here.
>
> May we have information here like:
>
> What type of AP used?
> Did this happen after leaving connection idle for some time? How much time?
> Did you try to reconnect to AP manually again after the problem? Or do you have to reload the driver again?
The AP was a Linksys; I am no longer at that location and cannot confirm the
exact model. This happened during regular usage, which included idle
periods but not extensive ones. I tried "iwconfig ap off" and
re-associating using Network Manager, neither of which worked. Only
reloading the driver got me back online.
On Thu, Sep 27, 2007 at 10:35:35PM -0000, Rolla Selbak wrote:
>
> "reason 1" is AP specific so only the AP develop know what this error mean. But looking at the log I see Txpower error and it might need more investigation here.
>
> May we have information here like:
>
> What type of AP used?
> Did this happen after leaving connection idle for some time? How much time?
> Did you try to reconnect to AP manually again after the problem? Or do you have to reload the driver again?
The AP was a Linksys; I am no longer at that location and cannot confirm the
exact model. This happened during regular usage, which included idle
periods but not extensive ones. I tried "iwconfig ap off" and
re-associating using Network Manager, neither of which worked. Only
reloading the driver got me back online.
--
- mdz