From: Marcel Holtmann <marcel@holtmann.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] add support for showing power constraint IE
Date: Mon, 04 May 2009 10:07:43 -0700 [thread overview]
Message-ID: <1241456863.2903.29.camel@localhost.localdomain> (raw)
In-Reply-To: <1241456088.8683.62.camel@johannes.local>
Hi Johannes,
> > just re-based and added the patch for the WPA/RSN length checks. So we
> > should be good now in this area.
>
> Thanks, applied, and really pushed out now.
>
> Do you think I should cut a new release with all the shiny new parsing
> code, or will you work on more :)
the only thing that bugs me is this:
BSS 00:1c:f0:xx:xx:xx (on wlan0)
TSF: 3332683470455 usec (38d, 13:44:43)
freq: 2422
beacon interval: 100
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -36.00 dBm
SSID: Big in Japan
Supported rates: 1.0* 2.0* 5.5* 11.0*
DS Paramater set: channel 3
Country: CA (in/outdoor), data: 01 0b 1b
ERP: <no flags>
Extended supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 0x0000
WMM: parameter: 01 00 00 03 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00
Vendor specific: OUI 00:90:4c, data: 33 0c 10 1f ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Vendor specific: OUI 00:90:4c, data: 34 03 00 05 00 00 00 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Unknown IE (45): 0c 10 1f ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00
Unknown IE (61): 03 00 01 00 00 00 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPS: * Version: 1.0
* Manufacturer: D-Link Systems
* Model: DIR-615
* Device name: Wireless N Router
* Config methods: Label
I didn't find any specs to decode IE 45 and 61 since all of them mark
these as reserved. Not sure if these are defined in future specs or if
they are deprecated IE. And it seems its data is similar to what is in
the vendor specific elements.
The other one that keeps showing up in my area is:
Unknown IE (47): 06
And I do have some other vendor specific ones, that I don't really care
about and we might even never know what they are:
Vendor specific: OUI 00:03:7f, data: 01 01 00 17 00 00
Vendor specific: OUI 00:03:7f, data: 02 01 01 4d 00 03 a4 00 00
Vendor specific: OUI 00:03:2f, data: 01 00 01
However, as I said before, I am quite happy now since the provided
information by iw are now the same as I get with iwlist. Actually iw has
now superior decoding capabilities and is more useful. There is still
room for improvement, but I think cutting a new release is not a bad
idea.
Regards
Marcel
next prev parent reply other threads:[~2009-05-04 17:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 16:06 [PATCH] add support for showing power constraint IE Marcel Holtmann
2009-05-04 16:10 ` Johannes Berg
2009-05-04 16:35 ` Marcel Holtmann
2009-05-04 16:38 ` Johannes Berg
2009-05-04 16:50 ` Marcel Holtmann
2009-05-04 16:54 ` Johannes Berg
2009-05-04 17:07 ` Marcel Holtmann [this message]
2009-05-04 17:35 ` Johannes Berg
2009-05-04 17:48 ` Marcel Holtmann
2009-05-04 18:03 ` Johannes Berg
2009-05-04 18:06 ` Johannes Berg
2009-05-04 19:03 ` Marcel Holtmann
2009-05-04 17:23 ` Marcel Holtmann
2009-05-04 18:10 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1241456863.2903.29.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox