problem getting hostapd and bridging to work

[Dave Tyson <dtyson%anduin.org.uk@localhost>]

I have been trying to set up a simple wireless access point
using rpi model B under NetBSD 10.0-BETA and seem to be failing
miserably. Can someone hit me with a cluebat :-)

Basically I have ethernet coming into the rpi usmsc0 10/100 interface
and a USB D-Link DWA-140 to provide the wireless access point. The two
interfaces are bridged and hostapd is used to do WPA authentication.
The dhcp server sits on the router at the end of the cat5.

/etc/ifconfig.bridge0
create
up
! brconfig bridge0 add usmsc0 add run0

/etc/ifconfig.usmsc0
up
inet 192.168.0.254 netmask 0xffffff00 media autoselect

/etc/ifconfig.run0
apbridge
up

/etc/hostapd.conf
country_code=GB
logger_syslog=-1
logger_syslog_level=1
debug=4
interface=run0
ssid=Penkett2
hw_mode=g
macaddr_acl=0
auth_algs=1
wpa=2
wpa_passphrase=secret-pass
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP

default router is set to 192.168.0.1 and resolver to 8.8.8.8 - these
are only set so I can transfer files.

Everything comes up OK, I have hostapd running with as much debug as I
can get.

A mobile phone connects and authenticates OK, but then fails to get an
IP address. Something seems to be not working on the bridge.

The messages file shows:
Jul 18 17:04:38 ap1 hostapd: Configuration file: /etc/hostapd.conf
Jul 18 17:04:40 ap1 hostapd: run0: interface state UNINITIALIZED-
>COUNTRY_UPDATE
Jul 18 17:04:45 ap1 hostapd: Using interface run0 with hwaddr
9c:d6:43:6a:f0:76 and ssid "Penkett2"
Jul 18 17:04:52 ap1 hostapd: run0: interface state COUNTRY_UPDATE-
>ENABLED
Jul 18 17:04:52 ap1 hostapd: run0: AP-ENABLED 
Jul 18 17:08:02 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 IEEE 802.11:
associated
Jul 18 17:08:02 ap1 hostapd: run0: AP-STA-CONNECTED d6:16:5e:b2:ae:67
Jul 18 17:08:02 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 RADIUS:
starting accounting session A563B597F63F8398
Jul 18 17:08:02 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 WPA: pairwise
key handshake completed (RSN)
Jul 18 17:08:20 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 IEEE 802.11:
disassociated
Jul 18 17:08:20 ap1 hostapd: run0: AP-STA-DISCONNECTED
d6:16:5e:b2:ae:67
Jul 18 17:08:20 ap1 hostapd: ioctl[SIOCS80211, op=20, val=0,
arg_len=7]: No such file or directory
Jul 18 17:08:20 ap1 hostapd: ioctl[SIOCS80211, op=20, val=0,
arg_len=7]: No such file or directory
Jul 18 17:08:21 ap1 hostapd: ioctl[SIOCS80211, op=21, val=0,
arg_len=42]: Invalid argument
Jul 18 17:11:34 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 IEEE 802.11:
associated
Jul 18 17:11:35 ap1 hostapd: run0: AP-STA-CONNECTED d6:16:5e:b2:ae:67
Jul 18 17:11:35 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 RADIUS:
starting accounting session F9049BBD13382057
Jul 18 17:11:35 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 WPA: pairwise
key handshake completed (RSN)
Jul 18 17:11:53 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 IEEE 802.11:
disassociated
Jul 18 17:11:53 ap1 hostapd: run0: AP-STA-DISCONNECTED
d6:16:5e:b2:ae:67
Jul 18 17:11:53 ap1 hostapd: ioctl[SIOCS80211, op=20, val=0,
arg_len=7]: No such file or directory
Jul 18 17:11:53 ap1 hostapd: ioctl[SIOCS80211, op=20, val=0,
arg_len=7]: No such file or directory
Jul 18 17:11:53 ap1 hostapd: ioctl[SIOCS80211, op=21, val=0,
arg_len=42]: Invalid argument

tcpdump shows:
ap1# tcpdump -i run0
tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
listening on run0, link-type EN10MB (Ethernet), capture size 262144
bytes
17:11:34.716656 EAPOL key (3) v2, len 95
17:11:34.724503 EAPOL key (3) v1, len 117
17:11:34.827149 EAPOL key (3) v2, len 157
17:11:35.209920 EAPOL key (3) v1, len 95
17:11:35.311142 IP6 :: > ff02::1:ffc9:f4cb: ICMP6, neighbor
solicitation, who has fe80::2d01:bf18:cc9:f4cb, length 24
17:11:35.311381 IP6 :: > ff02::1:ffc9:f4cb: ICMP6, neighbor
solicitation, who has fe80::2d01:bf18:cc9:f4cb, length 24
17:11:35.321774 IP6 :: > ff02::16: HBH ICMP6, multicast listener report
v2, 4 group record(s), length 88
17:11:35.322028 IP6 :: > ff02::16: HBH ICMP6, multicast listener report
v2, 4 group record(s), length 88
17:11:35.501651 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from d6:16:5e:b2:ae:67 (oui Unknown), length 298
17:11:35.501943 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from d6:16:5e:b2:ae:67 (oui Unknown), length 298
17:11:35.502940 ARP, Request who-has 192.168.0.131 tell 192.168.0.1,
length 50
17:11:36.085475 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::16: HBH ICMP6,
multicast listener report v2, 1 group record(s), length 28
17:11:36.085737 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::16: HBH ICMP6,
multicast listener report v2, 1 group record(s), length 28
17:11:36.087751 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::2: ICMP6, router
solicitation, length 16
17:11:36.088005 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::2: ICMP6, router
solicitation, length 16
17:11:36.129132 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::16: HBH ICMP6,
multicast listener report v2, 4 group record(s), length 88
17:11:36.129426 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::16: HBH ICMP6,
multicast listener report v2, 4 group record(s), length 88
17:11:36.487102 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from d6:16:5e:b2:ae:67 (oui Unknown), length 298
17:11:36.487406 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from d6:16:5e:b2:ae:67 (oui Unknown), length 298
17:11:36.563112 ARP, Request who-has 192.168.0.131 tell 192.168.0.1,
length 50
17:11:37.109476 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::16: HBH ICMP6,
multicast listener report v2, 1 group record(s), length 28
17:11:37.109741 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::16: HBH ICMP6,
multicast listener report v2, 1 group record(s), length 28
17:11:37.603121 ARP, Request who-has 192.168.0.131 tell 192.168.0.1,
length 50
17:11:38.507063 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from d6:16:5e:b2:ae:67 (oui Unknown), length 298
17:11:38.507349 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from d6:16:5e:b2:ae:67 (oui Unknown), length 298
17:11:40.373684 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::2: ICMP6, router
solicitation, length 16
17:11:40.373942 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::2: ICMP6, router
solicitation, length 16
17:11:42.727146 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from d6:16:5e:b2:ae:67 (oui Unknown), length 298
17:11:42.727431 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from d6:16:5e:b2:ae:67 (oui Unknown), length 298
17:11:49.084884 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::2: ICMP6, router
solicitation, length 16
17:11:49.085146 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::2: ICMP6, router
solicitation, length 16
17:11:50.064140 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from d6:16:5e:b2:ae:67 (oui Unknown), length 298
17:11:50.064425 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from d6:16:5e:b2:ae:67 (oui Unknown), length 298
17:11:57.091904 0e:08:7c:9c:5c:af (oui Unknown) > Broadcast Null
Unnumbered, xid, Flags [Response], length 50: 01 00
17:11:57.426901 ARP, Request who-has 192.168.0.1 tell 192.168.0.89,
length 50
17:11:57.494173 ARP, Request who-has 192.168.0.1 tell 192.168.0.89,
length 50
17:12:02.287265 34:38:b7:1c:76:ba (oui Unknown) > Broadcast Null
Unnumbered, xid, Flags [Response], length 50: 01 00
^C
37 packets captured
37 packets received by filter
0 packets dropped by kernel

So the wireless interface is seeing the requests from the phone, but
it's not seeing anything back from the bridge. It like the bridge is
not forwarding the traffic properly - yet it seems to be up and
running.

if I change usmsc0 to get an address via dhcp then that works OK, so I
know the dhcp side is working OK. I must be doing something stupid -
what is it :-)

Dave