Re: Please somebody explain this

Joerg Albert <[email protected]>
Newsgroups gmane.linux.drivers.at76c503a.user
Message-ID <[email protected]>
Hi Ivica,

On Tue, 27 Jan 2004, Ivica [iso-8859-2] Bo?uli? wrote:

> Please can somebody explain this lines
>
> Jan 27 10:46:47 ivica kernel: at76c503.c: 0xd8a40780: bssid 00:10:e7:b5:01:95
> channel 7 ssid IIDSplit (49494453706C6974) capa x0015 rates 82 84 0B 16 rssi
> 0 link 0 noise 0
> ...

> This is what I dont know
>
> capa x0041
> capa x0001
> capa x0031

Capabilities broadcasted in the beacon of the BSS:
bit0 set - ESS (i.e. this is an access point)
bit1 set - IBSS (i.e. an ad-hoc IBSS)
bit4 set - WEP enabled
bit5 set - short preamble used
bit6 set - no idea, maybe PBCC modulation

> rates 82 84 8B 96 and
> rates 82 84 0B 16 2C

The supported rates of the (I)BSS: bit 7 set means this is a basic rate
(i.e. it _must_ be supported by the client), bit6-0 is the rate in units
of 500 Kbit/s, e.g.
82 - basic rate 1 MBit/s
96 - basic rate 11 MBit/s
0B - optional rate 5.5 MBit/s

Capability and rate coding is defined in the 802.11 standard.

> timeout 2000

This is the parameter JoinFailureTimeout of the JoinRequest command to the
firmware, I guess the firmware will timeout in that many ms (e.g. if the
BSS disappeared meanwhile).

> ssid HTmobile (48546D6F62696C65)
> ssid WIREGEN (5749524547454E)

The numbers in (..) are the ASCII codes of the ssid printed before,
in case someone has non-printable chars in the ssid.

> Is there any utility to make this info human readable?

no, only your eyes reading the driver's source code ;-)

I've added these lines for debugging purpose only, a normal user
shouldn't bother about them. The rates are explained on
the support page of the website.

BTW, the BSS table is output twice into syslog:
first after an active scan with ANY ssid and second after an active scan
with the configured ssid. Results are merged to get a better overview on
the environment.

 /Jörg
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.