Madwifi + wpa_supplicant (cannot get IP)

Carlos Moffat carlos.lst at eldiabloenlosdetalles.net
Wed Nov 29 20:40:14 EST 2006


On Wed, 2006-11-29 at 16:43 -0800, Derek Chan wrote:
> On Wed, Nov 29, 2006 at 06:55:17PM -0500, Carlos Moffat wrote:
> > > Starting AP scan (broadcast SSID)
> > > Trying to get current scan results first without requesting a new scan
> > > to speed up initial association
> > > Received 0 bytes of scan results (0 BSSes)
> > > Scan results: 0
> > > Selecting BSS from priority group 0
> > > No suitable AP found.
> > > Setting scan request: 0 sec 0 usec
> > > Starting AP scan (broadcast SSID)
> > > Scan timeout - try to get results
> > > Received 128 bytes of scan results (1 BSSes)
> > > Scan results: 1
> > > Selecting BSS from priority group 0
> > > 0: 00:0f:66:8a:f6:7b ssid='Patagonia' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> > >    skip - no WPA/RSN IE
> > >    selected non-WPA AP 00:0f:66:8a:f6:7b ssid='Patagonia'
> 
>       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> I'm pretty new to this stuff, but it doesn't look like this is a WPA-enabled
> access point.  Or if it is, it's not broadcasting the right flags.
> 
> Hope this helps?
> 
>  - Derek

Hi Derek, 

You're right, is not. I'm trying to get wpa_supplicant to work 'cause
Network-Manager uses it for all connection, independent of whether you
need WPA or not. This seems like a good idea, except that now I have
moving part to worry about. I don't know where to file a bug, 'cause I
don't know if the problem is with Madwifi or wpa_supplicant (NM seems to
be innocent)

Again, I'd really appreciate any help or pointers about how to debug
this.

Thanks,
Carlos






More information about the HostAP mailing list