From: Jean Tourrilhes <jt@hpl.hp.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Larry Finger <Larry.Finger@lwfinger.net>, Jouni Malinen <j@w1.fi>,
Jouni Malinen <jouni.malinen@atheros.com>,
wireless <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
John Linville <linville@tuxdriver.com>
Subject: Re: Regression in 2.6.27-git from commit 43ac2ca3840f64
Date: Wed, 22 Oct 2008 11:00:12 -0700 [thread overview]
Message-ID: <20081022180012.GA6089@bougret.hpl.hp.com> (raw)
In-Reply-To: <1224697587.30459.37.camel@johannes.berg>
On Wed, Oct 22, 2008 at 07:46:27PM +0200, Johannes Berg wrote:
> On Wed, 2008-10-22 at 10:37 -0700, Jean Tourrilhes wrote:
>
> > If you want me to understand what it's about, you may want to
> > give me a bit more context.
>
> Sorry. Basically, Larry is saying that due to a kernel change, iwlist
> will print out things like
> IE: Unknown: 0017465249545A21426F7820466F6E20574C414E2037313133
> IE: Unknown: 010482848B96
> IE: Unknown: 030106
> IE: Unknown: 2A0106
> IE: IEEE 802.11i/WPA2 Version 1
> Group Cipher : TKIP
> Pairwise Ciphers (1) : CCMP
> Authentication Suites (1) : PSK
> IE: Unknown: 32080C1218243048606C
> IE: WPA Version 1
> Group Cipher : TKIP
> Pairwise Ciphers (1) : TKIP
> Authentication Suites (1) : PSK
> IE: Unknown: DD0A0800280101000200FF0F
> IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
>
>
> where all the IE: Unknown lines are unexpected.
Unexpected, but not broken. That's good.
> > Alternatively, just send me a patch for Wireless Tools, and
> > I'll put it in the next release. Wireless Tools is still maintained
> > and I still do releases, even if I don't put much cycles into it.
>
> The problem is that we don't quite know what to do about them :)
We are not supposed to "do" anything, but to show the
underlying data in a user friendly way. I can't believe that we could
not parse this data properly, we manage to parse other IEs
correctly. If you are debugging a problem with wpa_supplicant, or a
Access Point issue, what would *you* want to see there.
> johannes
Have fun...
Jean
prev parent reply other threads:[~2008-10-22 18:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 16:01 Larry Finger
2008-10-21 21:30 ` Johannes Berg
2008-10-22 2:34 ` Larry Finger
2008-10-22 7:23 ` Johannes Berg
2008-10-21 21:37 ` John W. Linville
2008-10-22 2:45 ` Larry Finger
2008-10-22 7:28 ` Jouni Malinen
2008-10-22 16:47 ` Larry Finger
2008-10-22 17:04 ` Jouni Malinen
2008-10-22 17:06 ` Johannes Berg
2008-10-22 17:37 ` Jean Tourrilhes
2008-10-22 17:46 ` Johannes Berg
2008-10-22 18:00 ` Jean Tourrilhes [this message]
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=20081022180012.GA6089@bougret.hpl.hp.com \
--to=jt@hpl.hp.com \
--cc=Larry.Finger@lwfinger.net \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=jouni.malinen@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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
all inboxes | Powered by JetHome®