netdev - Re: dscape doesn't auto associate

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9e4733910701231808l451453ak16de4d1745b08209@mail.gmail.com>
Date:	Tue, 23 Jan 2007 21:08:34 -0500
From:	"Jon Smirl" <jonsmirl@...il.com>
To:	"Michael Wu" <flamingice@...rmilk.net>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: dscape doesn't auto associate

On 1/23/07, Michael Wu <flamingice@...rmilk.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@...il.com
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html