wireless: host access point w/ WAP help!

Nerius Landys nlandys at gmail.com
Mon Sep 7 00:27:09 UTC 2009


I am following the Handbook instructions for setting up a FreeBSD
wireless host access point:
http://www.freebsd.org/doc/en/books/handbook/network-wireless.html

root at speedy# dmesg | grep ath
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath0: <Atheros 5212> mem 0xff8f0000-0xff8fffff irq 21 at device 0.0 on pci1
ath0: [ITHREAD]
ath0: WARNING: using obsoleted if_watchdog interface
ath0: Ethernet address: 00:02:6f:61:e6:7d
ath0: mac 7.9 phy 4.5 radio 5.6
ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x490
hal flags 0x150), hal status 12

root at speedy# ifconfig ath0 list caps
ath0=6783edcf<WEP,TKIP,AES,AES_CCM,FF,TURBOP,IBSS,HOSTAP,AHDEMO,TXPMGT,SHSLOT,SHPREAMBLE,MONITOR,TKIPMIC,WPA1,WPA2,BURST,WME,BGSCAN,TXFRAG>


I am able to set up an access point with no authentication or
encryption.  I verified this by connecting to my FreeBSD router from a
Windows [wireless] laptop computer over SSH.

It seems that the minute I try to turn WAP on (based on the
instructions in the Handbook), things stop working.

The steps I follow to enable WAP (after verifying that the host access
point is working without encryption) are based on the instructions in
the Handbook, and are as follows:

1. Create /etc/hostapd.conf:

interface=ath0
debug=1
ctrl_interface=/var/run/hostapd
ctrl_interface_group=wheel
ssid=speedy.i
wpa=1
wpa_passphrase=xxx3xxx3
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP TKIP


2. Add this line to /etc/rc.conf:

hostapd_enable="YES"


3. Execute "/etc/rc.d/hostapd forcestart".
I realize this is only needed for changes to take effect before
rebooting the system.


I also tried rebooting (with the line in rc.conf) but the results are
the same.  With WAP "enabled" (following the three steps above), my
Windows laptop does not scan to find the "speedy.i" access point.
Also, here are some things output by "ifconfig ath0" before and after
I follow these steps to enable WAP:

BEFORE ENABLING WAP (without hostapd):

nlandys at speedy# ifconfig ath0
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	ether 00:02:6f:61:e6:7d
	inet 192.168.1.254 netmask 0xffffff00 broadcast 192.168.1.255
	media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
	status: associated
	ssid speedy.i channel 1 (2412 Mhz 11g) bssid 00:02:6f:61:e6:7d
	authmode OPEN privacy OFF txpower 31.5 scanvalid 60 bgscan
	bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 roam:rate11g 5
	protmode CTS burst dtimperiod 1


AFTER ENABLING WAP (with hostapd):

root at speedy# ifconfig ath0
ath0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
	ether 00:02:6f:61:e6:7d
	inet 192.168.1.254 netmask 0xffffff00 broadcast 192.168.1.255
	media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
	status: no carrier
	ssid speedy.i channel 1 (2412 Mhz 11g)
	authmode AUTO privacy OFF txpower 31.5 scanvalid 60 bgscan
	bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 roam:rate11g 5
	protmode CTS burst dtimperiod 1


The output from "ifconfig ath0" above after WAP has been enabled
differs significantly from the sample output in the Handbook.

One more important thing.  I look at processes from top and I see
nothing running that corresponds to hostapd.  Is this a daemon?  I
also did the following:

root at speedy# find /var | grep -i hostapd

And it returns nothing.  Does  /var/run/hostapd need to exist as a
directory for things to work?


More information about the freebsd-questions mailing list