Re: [RFC PATCH] softmac: (v2) send WEXT assoc/disassoc events to userspace

Re: [RFC PATCH] softmac: (v2) send WEXT assoc/disassoc events to userspace

[Larry Finger]

Dan Williams wrote:
> Completely untested, not entirely sure it compiles.  For whatever
> reason, softmac is sending custom events to userspace already, but it
> should _really_ be sending the right WEXT events instead.  Comments?  If
> this looks good, please apply it.
> 
> Signed-off-by: Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> 

V2 compiles cleanly. It still doesn't authenticate with my WRT54G V5, but that must be another problem.

Larry

Re: [RFC PATCH] softmac: (v2) send WEXT assoc/disassoc events to userspace

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 498 bytes --]

On Thu, 2006-03-09 at 15:41 -0500, Dan Williams wrote:

> Can you grab a debug log from wpa_supplicant?  Run wpa_supplicant with
> the args "-ddd", and _don't_ run it as a daemon.  Mail the output to me
> if you don't want it to go to everyone on the cc list (might include
> SSIDs and such).  That should allow us to figure out exactly where
> wpa_supplicant and/or the driver are having issues.

Did this ever happen? I'm currently trying to collect all the pending
patches

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]

Re: [RFC PATCH] softmac: (v2) send WEXT assoc/disassoc events to userspace

[Hans Fugal]

[-- Attachment #1: Type: text/plain, Size: 527 bytes --]

With the patch, wpa_supplicant is able to work properly for WEP and
plaintext as tested with my bcm4306 (iBook), and the latest git.

However, and this may not be related, I still must issue an 

    ip link set up eth1

after loading the bcm43xx module but before starting wpa_supplicant or
it will not work. 

-- 
Hans Fugal ; http://hans.fugal.net
 
There's nothing remarkable about it. All one has to do is hit the 
right keys at the right time and the instrument plays itself.
    -- Johann Sebastian Bach

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [RFC PATCH] softmac: (v2) send WEXT assoc/disassoc events to userspace

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 576 bytes --]

On Thu, 2006-04-13 at 19:05 -0600, Hans Fugal wrote:
> With the patch, wpa_supplicant is able to work properly for WEP and
> plaintext as tested with my bcm4306 (iBook), and the latest git.

Thanks, great. I have network-manager up and running too now (finally!)

> However, and this may not be related, I still must issue an 
> 
>     ip link set up eth1
> 
> after loading the bcm43xx module but before starting wpa_supplicant or
> it will not work. 

Right, that is expected behaviour right now until we come up with how to
handle this properly.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]

softmac: semantics of SIOCSIWFREQ

[Ulrich Kunitz]

Hi,

I'm just reviewing the zd1211 code and I'm wondering about the
semantics of SIOCSIWFREQ and actually, what is good for. It looks
like that softmac's set_channel can be called at any time and will
ignore any settings of SIOCSIWFREQ even it is has been given the
flag IW_FREQ_FIXED. 

Following questions come to mind:

- Is SIOCSIWFREQ allowed while associated?
- If the flag IW_FREQ_FIXED is set, should all activitity
  including scanning only be allowed on this frequency? (Actually
  a better would even be to work with channel/frequency sets.
  These sets would make a lot of sense for parallel scanning
  whith more than one device.)
- Is there any use of the control, if the frequency is not fixed?

SIOCSIWFREQ and SIOCGIWFREQ appear to be good candidates to be
included in the softmac. If I would have a rough idea, what the
semantics should be, I would even volunteer to implement it. 

Uli

-- 
Ulrich Kunitz - kune@deine-taler.de