[Voyage-linux] Problem starting hostapd using Voyage 0.6.1 and madwifi driver on Alix.2d3

[Gustin Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kelly Hogan wrote:
> You need to define the bridge as part of the hostapd.conf
> 
> ie:
> 
> interface=ath0
> bridge=br0
> 
> otherwise driver will not pass traffic through the bridge and
> initialization will fail.
> 
This should only matter if the wireless device is part of a bridge.
- From the configs that he posted, it does not look like ath0 is part of a
bridge (it has a different IP from the bridged interface).  For this
setting to work, you also need to add ath0 to your bridge
br0.

Ath0 at that point will not need it's own IP.

Also, kismet is showing your AP as unsecured because hostap is not
running.  If hostap is not running, then kismet is not detecting
encrypted frames.

Here are my configs:
** note, I have two physical devices in my ALix, which is why the
bridged device is ath1

## /etc/network/interfaces ##
# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
# /usr/share/doc/ifupdown/examples for more information.
auto lo
iface lo inet loopback

auto ath1
iface ath1 inet manual
pre-up wlanconfig ath1 destroy || true
# set up the ath1 device in AP mode before bringing up the interface
(unless you're using AutoCreate)
pre-up wlanconfig ath1 create wlandev wifi1 wlanmode ap
# remove the ath1 device when bringing the interface down
post-down wlanconfig ath1 destroy
        up iwconfig ath1 essid whytebread5 rate 54M channel 11
        up ip link set ath1 up

auto br0
iface br0 inet static
# Assign your IP address, subnet and mask, broadcast address, and
default gateway
    address 192.168.1.4
    network 192.168.1.0
    netmask 255.255.255.0
    broadcast 192.168.1.255
    gateway 192.168.1.2
# Bridge eth0 and ath1 with br0.
    bridge_ports eth0 ath1
##EOF##

## /etc/hostapd/hostapd.conf ##

# based on howto at http://www.linux.com/articles/55617
interface=ath1
bridge=br0
driver=madwifi
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=2
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=mySSID
#macaddr_acl=1
#accept_mac_file=/etc/hostapd/accept
auth_algs=3
eapol_key_index_workaround=0
eap_server=0
wpa=1
wpa_psk_file=/etc/hostapd/hostapd.wpa_psk
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP
wpa_group_rekey=600
wpa_gmk_rekey=86400

##EOF##

The file /etc/hostapd/hostapd.wpa_psk just contains MAC addresses and
keys (the PSK I get from running wpa_passphrase).  A simpler option
might be to use "wpa_passphrase=someasciipassphrase" in your hostapd.conf

Also, when making changes to hostapd.conf, don't forget to restart it
with "/etc/init.d/hostapd restart"

Hth,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkniN6wACgkQwRXgH3rKGfNUPgCdGvViHbRsaWITxF/A9LFzDrE1
ztgAn0rw9rJCR36mFHXWTgtaMmSdpm6o
=nZ11
-----END PGP SIGNATURE-----