dscape doesn't auto associate

dscape doesn't auto associate

[Jon Smirl]

I have to manually associate the dscape stack with my AP. Is this way
the code is supposed to work? Everything works ok after the manual
association.

Is there documentation for this stack? Any special utilities for it?
I'd like to get my devices operating in master mode.

-- 
Jon Smirl
jonsmirl@gmail.com

Re: dscape doesn't auto associate

[Johannes Berg]

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

On Tue, 2007-01-23 at 18:23 -0500, Jon Smirl wrote:
> I have to manually associate the dscape stack with my AP. Is this way
> the code is supposed to work? Everything works ok after the manual
> association.

Yeah, you currently need to set the channel, BSSID and finally the SSID
to get it to associate.

> Is there documentation for this stack?

Not much really. devicescape has some on their website.

> Any special utilities for it?

Nope.

> I'd like to get my devices operating in master mode.

You don't need to associate then ;) But I can't really tell you exactly
how it's done. If you figure it out, add it to wireless.sipsolutions.net
(will become linuxwireless.org) somewhere -- we can rearrange the
material later.

johannes

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

Re: dscape doesn't auto associate

[Michael Wu]

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

On Tuesday 23 January 2007 18:23, Jon Smirl wrote:
> I have to manually associate the dscape stack with my AP. Is this way
> the code is supposed to work? Everything works ok after the manual
> association.
>
It's suppose to work with wpa_supplicant which sets every parameter. 
NetworkManager uses wpa_supplicant so configuration can be pretty easy.

If you really want to manually associate, set the channel, (e)ssid, and 
encryption (if any) in any order, and then set the bssid (ap) last. There 
will be patches to allow association by just setting the SSID for backwards 
compatibility with configuration scripts.

-Michael Wu

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

Re: dscape doesn't auto associate

[Jon Smirl]

On 1/23/07, Michael Wu <flamingice@sourmilk.net> wrote:
> On Tuesday 23 January 2007 18:23, Jon Smirl wrote:
> > I have to manually associate the dscape stack with my AP. Is this way
> > the code is supposed to work? Everything works ok after the manual
> > association.
> >
> It's suppose to work with wpa_supplicant which sets every parameter.
> NetworkManager uses wpa_supplicant so configuration can be pretty easy.

Something isn't working right with NetworkManager for me. I have both
zd1211 and rt2570 devices and neither will start automatically but I
can get the going manually.

I'll try running NetworkManager in the debugger and see if I can
figure out what is failing. NetworkManager is working ok for me on
non-dscape devices.

As for running as an AP:
rt2570 will start in Master mode
zd1211 refused to set Master mode

zd1211 has this problem too:
Error for wireless request "Set Encode" (8B2A) :
    SET failed on device wlan1 ; Invalid argument.

> If you really want to manually associate, set the channel, (e)ssid, and
> encryption (if any) in any order, and then set the bssid (ap) last. There
> will be patches to allow association by just setting the SSID for backwards
> compatibility with configuration scripts.
>
> -Michael Wu
>
>
>


-- 
Jon Smirl
jonsmirl@gmail.com

Re: dscape doesn't auto associate

[Jon Smirl]

On 1/23/07, Michael Wu <flamingice@sourmilk.net> wrote:
> On Tuesday 23 January 2007 18:23, Jon Smirl wrote:
> > I have to manually associate the dscape stack with my AP. Is this way
> > the code is supposed to work? Everything works ok after the manual
> > association.
> >
> It's suppose to work with wpa_supplicant which sets every parameter.
> NetworkManager uses wpa_supplicant so configuration can be pretty easy.

Speaking of wpa_supplicant I've been unable to get to main site
according to wikipedia for over a week. Has this project moved
elsewhere?

http://hostap.epitest.fi/wpa_supplicant

> If you really want to manually associate, set the channel, (e)ssid, and
> encryption (if any) in any order, and then set the bssid (ap) last. There
> will be patches to allow association by just setting the SSID for backwards
> compatibility with configuration scripts.
>
> -Michael Wu
>
>
>


-- 
Jon Smirl
jonsmirl@gmail.com

Re: dscape doesn't auto associate

[Michael Wu]

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

On Tuesday 23 January 2007 20:48, Jon Smirl wrote:
> As for running as an AP:
> rt2570 will start in Master mode
> zd1211 refused to set Master mode
>
No master mode support in zd1211 yet - I haven't had time (and the other two 
developers don't work on the d80211 version yet). Only client mode is 
currently supported.

-Michael Wu

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

Re: dscape doesn't auto associate

[Michael Wu]

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

On Tuesday 23 January 2007 20:48, Jon Smirl wrote:
> I'll try running NetworkManager in the debugger and see if I can
> figure out what is failing. NetworkManager is working ok for me on
> non-dscape devices.
>
Dan, any idea what's happening?

FWIW, I'm running NetworkManager 0.6.2 (from SuSE 10.1) with wpa_supplicant 
0.5.7.

> zd1211 has this problem too:
> Error for wireless request "Set Encode" (8B2A) :
>     SET failed on device wlan1 ; Invalid argument.
>
Shouldn't happen if it works for rt2570. Both use software encryption.

-Michael Wu

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

Re: dscape doesn't auto associate

[Marcus Better]

Jon Smirl wrote:
> Has this project moved elsewhere?
> 
> http://hostap.epitest.fi/wpa_supplicant

Apparently it's down at this moment:

  http://permalink.gmane.org/gmane.linux.drivers.hostap/15287

Re: dscape doesn't auto associate

[Dan Williams]

On Tue, 2007-01-23 at 20:48 -0500, Jon Smirl wrote:
> On 1/23/07, Michael Wu <flamingice@sourmilk.net> wrote:
> > On Tuesday 23 January 2007 18:23, Jon Smirl wrote:
> > > I have to manually associate the dscape stack with my AP. Is this way
> > > the code is supposed to work? Everything works ok after the manual
> > > association.
> > >
> > It's suppose to work with wpa_supplicant which sets every parameter.
> > NetworkManager uses wpa_supplicant so configuration can be pretty easy.
> 
> Something isn't working right with NetworkManager for me. I have both
> zd1211 and rt2570 devices and neither will start automatically but I
> can get the going manually.
> 
> I'll try running NetworkManager in the debugger and see if I can
> figure out what is failing. NetworkManager is working ok for me on
> non-dscape devices.
> 
> As for running as an AP:
> rt2570 will start in Master mode
> zd1211 refused to set Master mode
> 
> zd1211 has this problem too:
> Error for wireless request "Set Encode" (8B2A) :
>     SET failed on device wlan1 ; Invalid argument.

If you get this error in the _NM_ logs, it's likely just trying to clear
out the key, and you can probably ignore it.  If you get this error from
wpa_supplicant, it's probably a driver issue.

Can you send me some logs privately?  I think SUSE directs the NM logs
somewhere like /var/log/NetworkManager.log.  Stop NM as a service, get
root, then "NetworkManager --no-daemon" and redirect the output to a
file if you don't want to track down the logs themselves.

Cheers,
Dan

> > If you really want to manually associate, set the channel, (e)ssid, and
> > encryption (if any) in any order, and then set the bssid (ap) last. There
> > will be patches to allow association by just setting the SSID for backwards
> > compatibility with configuration scripts.
> >
> > -Michael Wu
> >
> >
> >
> 

Re: dscape doesn't auto associate

[Larry Finger]

Dan Williams wrote:
> 
> If you get this error in the _NM_ logs, it's likely just trying to clear
> out the key, and you can probably ignore it.  If you get this error from
> wpa_supplicant, it's probably a driver issue.
> 
> Can you send me some logs privately?  I think SUSE directs the NM logs
> somewhere like /var/log/NetworkManager.log.  Stop NM as a service, get
> root, then "NetworkManager --no-daemon" and redirect the output to a
> file if you don't want to track down the logs themselves.

The log is in /var/log/NetworkManager on openSUSE 10.2.

Using bcm43xx-softmac, the returned frequency is 0. Any suggestions on where I should look to get
the proper frequency or channel data?

Larry