> I expect that softmac should be listening to the driver as to whether this
> capability is available;
> however, I'm now up and running once again.
Yeah, I think a patch was floating around too!
johannes
signature.asc
Description: This is a digitally signed message part
Johannes Berg wrote:
On Fri, 2006-06-09 at 10:31 -0500, Larry Finger wrote:
Do you mean a special dump, or is the kernel debug output and wpa_supplicant
debug output sufficient?
I was thinking of packet dumps but earlier you said you couldn't create
any so I'm out of ideas for now.
I was f
Johannes Berg wrote:
On Fri, 2006-06-09 at 10:31 -0500, Larry Finger wrote:
Do you mean a special dump, or is the kernel debug output and wpa_supplicant
debug output sufficient?
I was thinking of packet dumps but earlier you said you couldn't create
any so I'm out of ideas for now.
Actuall
On Fri, 2006-06-09 at 10:31 -0500, Larry Finger wrote:
> Do you mean a special dump, or is the kernel debug output and wpa_supplicant
> debug output sufficient?
I was thinking of packet dumps but earlier you said you couldn't create
any so I'm out of ideas for now.
johannes
signature.asc
Desc
Johannes Berg wrote:
On Wed, 2006-06-07 at 13:12 -0500, Larry Finger wrote:
but why doesn't it work?
No idea. If we had a dump maybe we could tell :/
Do you mean a special dump, or is the kernel debug output and wpa_supplicant
debug output sufficient?
Larry
-
To unsubscribe from this list:
On Wed, 2006-06-07 at 13:12 -0500, Larry Finger wrote:
> > (ie, add the "hh" before the x to tell the print that it's a char)
> >
> That doesn't work - the result is
>
> %hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx
Looks like the kernel doesn't support that modifier.
Dan Williams wrote:
Weird, does the kernel not do something that fprintf() _does_ do here?
I tested with a short C program that mimics the behavior of this chunk
of code, and "%.2x" didn't work, but "%.2hhx" certainly did. "hh" is
supposed to mean "A following integer conversion corresponds to a
On Wed, 2006-06-07 at 13:12 -0500, Larry Finger wrote:
> Dan Williams wrote:
> >
> > from ieee80211softmac_wx.c: ieee80211softmac_wx_set_genie()
> >
> > memcpy(mac->wpa.IE, extra, wrqu->data.length);
> > dprintk(KERN_INFO PFX "generic IE set to ");
> >
Dan Williams wrote:
On Wed, 2006-06-07 at 17:57 +0200, Johannes Berg wrote:
On Wed, 2006-06-07 at 17:51 +0200, Johannes Berg wrote:
Well, it should be shown in the 802.11i spec too.
I suppose that it is the association request, and needs to contain the
RSN described in 7.3.2.25 as per 7.2.3.4
On Wed, 2006-06-07 at 17:57 +0200, Johannes Berg wrote:
> On Wed, 2006-06-07 at 17:51 +0200, Johannes Berg wrote:
>
> > Well, it should be shown in the 802.11i spec too.
>
> I suppose that it is the association request, and needs to contain the
> RSN described in 7.3.2.25 as per 7.2.3.4 in 802.11
Johannes Berg wrote:
On Wed, 2006-06-07 at 09:01 -0700, Sam Leffler wrote:
Beware of the order of IE's in the management frames; some AP's are
touchy about this.
Uh oh. I have no idea where the ieee80211 layer sticks that one,
probably at the end.
I moved the WPA IE from the end forward wit
Johannes Berg wrote:
On Wed, 2006-06-07 at 09:01 -0700, Sam Leffler wrote:
Beware of the order of IE's in the management frames; some AP's are
touchy about this.
Uh oh. I have no idea where the ieee80211 layer sticks that one,
probably at the end.
I can verify that. I'm currently building a
Sam Leffler wrote:
Beware of the order of IE's in the management frames; some AP's are
touchy about this.
That may be the cause here as the behavior when I changed AP's from the Linux-based model to one
with VXWorks.
Larry
-
To unsubscribe from this list: send the line "unsubscribe netdev" i
On Wed, 2006-06-07 at 09:01 -0700, Sam Leffler wrote:
> Beware of the order of IE's in the management frames; some AP's are
> touchy about this.
Uh oh. I have no idea where the ieee80211 layer sticks that one,
probably at the end.
johannes
signature.asc
Description: This is a digitally signed
Johannes Berg wrote:
> On Wed, 2006-06-07 at 10:47 -0500, Larry Finger wrote:
>
>> I have a little more information on what is happening.
>
> Great.
>
>> In IEEE Std 802.11i-2004, which defines the
>> WPA protocol, Figure 11a shows the sequence of exchanges needed to
>> associate. Both bcm43x
On Wed, 2006-06-07 at 17:51 +0200, Johannes Berg wrote:
> Well, it should be shown in the 802.11i spec too.
I suppose that it is the association request, and needs to contain the
RSN described in 7.3.2.25 as per 7.2.3.4 in 802.11i. This is, afaik, the
'generic IE' that is added with the wext. Now
On Wed, 2006-06-07 at 10:47 -0500, Larry Finger wrote:
> I have a little more information on what is happening.
Great.
> In IEEE Std 802.11i-2004, which defines the
> WPA protocol, Figure 11a shows the sequence of exchanges needed to associate.
> Both bcm43xx-softmac
> and ndiswrapper go thr
Johannes Berg wrote:
generic IE is what the wext is called, it is the IE that wpa_supplicant
sets. Not sure what's going on though, I know next to nothing about wpa.
I have a little more information on what is happening. In IEEE Std 802.11i-2004, which defines the
WPA protocol, Figure 11a sho
On Tue, 2006-06-06 at 14:24 -0500, Larry Finger wrote:
> Jun 6 13:34:10 larrylap kernel: SoftMAC: generic IE set to
> ffdd160050fff2010150fff2020150fff2020150fff202
> Why does SoftMAC set a generic IE rather than get one from wpa_supplicant? I
> would appreciate
19 matches
Mail list logo