hostapd 0.6.3 + Madwifi (ng/old/CVS3456) wifi ap hell

Jouni Malinen j at
Mon Apr 7 03:23:21 EDT 2008

On Sun, Apr 06, 2008 at 07:27:11PM +0200, Jef Rechards wrote:

> wlanconfig eth2 create wlandev wifi0 wlanmode ap

> hostapd.conf*
> bridge=wifi0

That is not correct. bridge option is used to set the bridge interface
(created with brctl) if you are using bridging to connect the wireless
and wired interfaces. If you are not using bridging, this option should
not be set in hostapd.conf.

> wpa=1
> #wpa_psk=0ddb70b8d4dec9f8d9922b45d0e3d5f6195d4851f51c669e7c05bd7fdf0b618e
> wpa_key_mgmt=WPA-PSK WPA-EAP
> wpa_pairwise=TKIP CCMP

Are you using WPA-PSK (passphrase) or WPA-EAP (EAP authentication)? The
configuration file here did not include either the PSK/passphrase or
RADIUS configuration. In addition, I would suggest starting with only
one option enabled for wpa_key_mgmt and wpa_pairwise to minimize
complexity before the setup has been found to work properly.

> After starting hostapd i can see the wifi AP fine(can even see its secure) 
> , and even try to connect.
> Whenever i proceed to connect it will disconnect after a while (ia 20 sec)
> *hostapd output*/ (for -dd  output see

This debug output does not match with the configuration file you
included in the message.. Anyway, as far as hostapd is concerned,
everything seemed to work fine. Authentication was completed
successfully and the client just seemed to have decided to disassociate.
In other words, you will need to take a closer look at the client to
figure out why it disassociates here; hostapd did not ask the client to
be disconnected here.

Jouni Malinen                                            PGP id EFC895FA

More information about the HostAP mailing list