Re: [Madwifi-users] Request help interpreting debug info

[Marc S. <el...@bu...>]

On Sun, May 16, 2004 at 10:44:24PM -0700, Sam Leffler wrote:
> Looks like you specified a desired bssid that's not one of the
> available AP's (note the "!"'s after each item that doesn't match
> something you requested to be matched).

I think there may be a couple of problems.  First, the driver isn't
picking up the announced essid when it changes from Straylight to
StraylightB.  It's easy to workaround, though.

Here's what I'm seeing now from iwconfig.

ath0      IEEE 802.11b  ESSID:""  
          Mode:Managed  Frequency:2.462GHz  Access Point: FF:FF:FF:FF:FF:FF  
          Bit Rate:1Mb/s   Tx-Power:50 dBm   Sensitivity=0/3  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0/94  Signal level:-95 dBm  Noise level:-95 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

and debug

ath0: macaddr          bssid         chan  rssi rate ant flag  wep  essid
 - 00:09:5b:c1:c1:ff 00:09:5b:c1:c1:ff!   1   +51 11M    1  ess   no  "StraylightB"
 - 00:06:25:c0:05:92 00:06:25:c0:05:92!   8    +2 11M    1  ess  wep! 0x000000000000
 - 00:09:5b:6e:d3:96 00:09:5b:6e:d3:96!  11   +11 11M    1  ess   no  0x00000000000000

It isn't asociating even though I'm not specifying an essid.  Even
when I change it to StraylightB, there is still no connection made.