Search Linux Wireless

Re: timeout problems with certain APs and b43

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Nov 23, 2007 4:21 PM, Rafael J. Wysocki <rjw@xxxxxxx> wrote:
> On Friday, 23 of November 2007, Johannes Berg wrote:
> >
>
> > > > > on certain APs, the internet works for a long time then stops, and I
> > > > > get authentication time outs, why?  It usually works again if I reset
> > > > > the AP itself, which i should not have to do and don't have to if in
> > > > > XP....
> > > >
> > > > > wlan0: Initial auth_alg=0
> > > > > wlan0: authenticate with AP 00:0f:66:53:3e:24
> > > > > wlan0: authenticate with AP 00:0f:66:53:3e:24
> > > > > wlan0: authenticate with AP 00:0f:66:53:3e:24
> > > > > wlan0: authentication with AP 00:0f:66:53:3e:24 timed out
> > > >
> > > > Does it help to reload the b43 module? I think I have seen this problem
> > > > before but always associated it with suspend/resume rather than a long
> > > > time elapsing, I also thought it was due to bad power recalibration.
> > >
> > > It seems that I can reproduce something similar on demand with an SMC wireless
> > > router by moving my box sufficiently far away from it. :-)
> >
> > Well, yeah, that's expected though, you lose signal at some point. Not
> > expected is that it happens without moving anything. Unless the
> > calibration code is wrong which wouldn't really surprise me either.
>
> In my case, everything works just fine when the box is 6 meters away from the
> AP (including a thick wall in between), but when I move it another 5-6 meters
> away from the AP, things break down ...
>
> I'd expect it to work at longer distances, but well. :-)
>
> Greetings,
> Rafael
>



wlan0     IEEE 802.11g  ESSID:"Network4Home"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:0F:66:53:3E:24
          Bit Rate=1 Mb/s   Tx-Power=27 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B
          Link Quality=68/100  Signal level=-58 dBm  Noise level=-69 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


I'd say 68/100 is a good signal strength.  I do use suspend/resume a
lot, but sometimes only a reboot of the laptop or the AP seems to get
it working normally again.
-
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux