On Fri, Nov 18, 2011 at 12:33 PM, Ryan Sommers <[email protected]> wrote: > I just recently got a Alix board and have setup a pfSense > router/gateway/firewall/vpn/access point box. I'm having an odd issue > with the "access point" side of that however. > > I originally thought the authentication and encryption were the issue, > however, for reasons I mention below, it now appears that something is > causing hostapd to not function properly when come out of a fresh > reboot. > > When I boot my pfSense box all the wireless settings appear to be > working fine and I see hostapd running. However, if a client tries to > associate with the network it is immediately disconnected again. When > this occurs, these are the messages I see in system.log > > Nov 18 10:43:58 pfSense hostapd: ath0_wlan0: STA 00:c0:ca:33:91:dd > IEEE 802.11: associated > Nov 18 10:44:03 pfSense hostapd: ath0_wlan0: STA 00:c0:ca:33:91:dd > IEEE 802.11: deassociated > > When I was attempting to debug this issue, I found that all I had to > do was the following commands after a fresh reboot and everything > began working: > > pkill -f "hostapd .*ath0_wlan0" > /usr/sbin/hostapd -B /var/etc/hostapd_ath0_wlan0.conf > > After that, clients can connect and stay connected just fine. I don't > find any messages (error or otherwise) before issuing these commands, > so I'm not exactly sure why hostapd doesn't start correctly when the > system boots. > > Anyone know of a reason for this to be happening? Or is there > something I can do to further diagnose the issue? >
There anything atypical you're doing? If that were a general issue, my wireless wouldn't work at boot time, and we'd have heard about it from a lot of others. _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
