public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
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:48:15 -0700	[thread overview]
Message-ID: <1241459295.2903.40.camel@localhost.localdomain> (raw)
In-Reply-To: <1241458558.8683.84.camel@johannes.local>

Hi Johannes,

> > 	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.
> 
> Both are HT.

do we have the specs somewhere then I might can give it a try. Also WMM
needs some improvements.

> > The other one that keeps showing up in my area is:
> > 
> > 	Unknown IE (47): 06
> 
> "Broadcom proprietary" -- seems it would make sense to ignore that.

Since it not showing up until you give -u there is no need to ignore it,
but where do you find that this is Broadcom proprietary and why the f*
they get to use an official IE number?

> > 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
> 
> You can check wireshark, sometimes it has something useful. I think
> there are pre-wifi HT IEs too in some vendor IE, might be one of these.
> 
> https://mentor.ieee.org/802.11/documents?x_dcn=31&x_year=2009 is useful
> too (at least for 2009, for next year somebody will have to find the DCN
> again)

I found an indication of what bit 1 of extended capabilities means. I do
have seen an AP with that somewhere around :)

Regards

Marcel



  reply	other threads:[~2009-05-04 17:48 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
2009-05-04 17:35             ` Johannes Berg
2009-05-04 17:48               ` Marcel Holtmann [this message]
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=1241459295.2903.40.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