On Monday 24 October 2005 12:33 pm, Konstantin KABASSANOV wrote:
> Hi,
>
> Using an atheros interface in ad-hoc mode I get the following information
> with "wlanctl -a" concerning the host interface:
>
> ath0: mac 00:02:6f:20:f7:ed bss 02:02:6f:20:f7:ed
>         node flags 0000
>         ess <TEST123>
>         chan 36 freq 5180MHz flags 0140<ofdm,5GHz>
>         capabilities 0002<ibss>
>         beacon-interval 100 TU tsft 0 us
>         rates [*6.0] 9.0 *12.0 18.0 *24.0 36.0 48.0 54.0
>         assoc-id 0 assoc-failed 0 inactivity 300s
>         rssi 23 txseq 2 rxseq 864
>
>
> Perhaps ifconfig ath0 displays the following:
>
> ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         ssid TEST123
>         powersave off
>         bssid 02:02:6f:20:f7:e7 chan 36
>         address: 00:02:6f:20:f7:ed
>         media: IEEE802.11 autoselect mode 11a adhoc
>         status: active
>         inet6 fe80::202:6fff:fe20:f7ed%ath0 prefixlen 64 scopeid 0x1
>
> So I wonder if it is normal to have such different results about the bss...
> In fact the correct bssid is the last one... So why does wlanctl report it
> incorrectly? BTW, why does it display the default rate to be [*6.0]?

The BSSIDs in both are the same, however the MAC and BSSID aren't the same; is 
this what you are wondering about? When I've looked at my Kismet logs I've 
noticed that some (mostly Netgear) access points will sometimes broadcast or 
receive an address with 0x02 in the first octet.

	Jonathan Kollasch