Re: problems with SMC 2632W in hostap mode

To confuse things more, I've reverted to bridging, just to
see if the problem might have gone away.  (It didn't, of course.)
Here's what the machine looks like now:  

- userland ppp is talking pppoe with a DSL modem over xl0
- wi0, rl0 and rl1 are all bridged together, and rl1 has IP
  number 10.0.0.1

xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=3<rxcsum,txcsum>
	inet6 fe80::250:daff:fe5f:f9c2%xl0 prefixlen 64 scopeid 0x1 
	ether 00:50:da:5f:f9:c2
	media: Ethernet autoselect (10baseT/UTP)
	status: active
wi0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	inet6 fe80::204:e2ff:fe57:80f6%wi0 prefixlen 64 scopeid 0x2 
	ether 00:04:e2:57:80:f6
	media: IEEE 802.11 Wireless Ethernet autoselect <hostap> (DS/2Mbps <hostap>)
	status: associated
	ssid john_f_kennedy_international 1:john_f_kennedy_international
	stationname brb
	channel 11 authmode OPEN powersavemode OFF powersavesleep 100
	wepmode OFF weptxkey 1
rl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	inet6 fe80::205:5dff:fe45:f30e%rl0 prefixlen 64 scopeid 0x3 
	ether 00:05:5d:45:f3:0e
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
rl1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	inet6 fe80::205:5dff:fe45:ffd0%rl1 prefixlen 64 scopeid 0x4 
	inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
	ether 00:05:5d:45:ff:d0
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
faith0: flags=8002<BROADCAST,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	inet6 ::1 prefixlen 128 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 
	inet 127.0.0.1 netmask 0xff000000 
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1492
	inet 66.32.185.224 --> 66.32.185.1 netmask 0xffffffff 
	Opened by PID 55

Just in case I've got my bridging settings wrong:

net.link.ether.bridge_cfg: wi0,rl0,rl1
net.link.ether.bridge: 1
net.link.ether.bridge_ipfw: 0
net.link.ether.bridge_ipf: 0
net.link.ether.bridge_ipfw_drop: 0
net.link.ether.bridge_ipfw_collisions: 0

I don't know if it's relevant, but here is what the kernel thinks
about the NICs:

Dec 22 00:51:42 brooklyn-bridge /kernel: xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x1800-0x187f mem 0xf4009000-0xf400907f irq 11 at device 13.0 on pci0
Dec 22 00:51:42 brooklyn-bridge /kernel: xl0: Ethernet address: 00:50:da:5f:f9:c2
Dec 22 00:51:42 brooklyn-bridge /kernel: miibus0: <MII bus> on xl0
Dec 22 00:51:42 brooklyn-bridge /kernel: xlphy0: <3c905C 10/100 internal PHY> on miibus0
Dec 22 00:51:42 brooklyn-bridge /kernel: xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Dec 22 00:51:42 brooklyn-bridge /kernel: wi0: <PRISM2STA WaveLAN> port 0x1c00-0x1c3f,0x1880-0x18ff mem 0xf4008000-0xf4008fff irq 10 at device 14.0 on pci0
Dec 22 00:51:42 brooklyn-bridge /kernel: wi0: 802.11 address: 00:04:e2:57:80:f6
Dec 22 00:51:42 brooklyn-bridge /kernel: wi0: using RF:PRISM2 MAC:HFA3841 CARD:HWB3163 rev.A
Dec 22 00:51:42 brooklyn-bridge /kernel: wi0: Intersil Firmware: Primary 0.03.00, Station 0.08.03
Dec 22 00:51:42 brooklyn-bridge /kernel: rl0: <D-Link DFE-530TX+ 10/100BaseTX> port 0x1000-0x10ff mem 0xf4009400-0xf40094ff irq 15 at device 15.0 on pci0
Dec 22 00:51:42 brooklyn-bridge /kernel: rl0: Ethernet address: 00:05:5d:45:f3:0e
Dec 22 00:51:42 brooklyn-bridge /kernel: miibus1: <MII bus> on rl0
Dec 22 00:51:42 brooklyn-bridge /kernel: rlphy0: <RealTek internal media interface> on miibus1
Dec 22 00:51:42 brooklyn-bridge /kernel: rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Dec 22 00:51:42 brooklyn-bridge /kernel: rl1: <D-Link DFE-530TX+ 10/100BaseTX> port 0x1400-0x14ff mem 0xf4009800-0xf40098ff irq 9 at device 16.0 on pci0
Dec 22 00:51:42 brooklyn-bridge /kernel: rl1: Ethernet address: 00:05:5d:45:ff:d0
Dec 22 00:51:42 brooklyn-bridge /kernel: miibus2: <MII bus> on rl1
Dec 22 00:51:42 brooklyn-bridge /kernel: rlphy1: <RealTek internal media interface> on miibus2
Dec 22 00:51:42 brooklyn-bridge /kernel: rlphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
D

If I assign one of the clients 10.0.0.12 and try to ping 10.0.0.1
from the client, here's what tcpdump -i wi0 on the AP machine
says:

11:00:53.542001 arp who-has 10.0.0.1 tell 10.0.0.12
11:00:53.542163 arp who-has 10.0.0.1 tell 10.0.0.12
11:00:53.542345 arp reply 10.0.0.1 is-at 0:4:e2:57:80:f6
11:00:54.534133 arp who-has 10.0.0.1 tell 10.0.0.12
11:00:54.534298 arp who-has 10.0.0.1 tell 10.0.0.12
11:00:54.534468 arp reply 10.0.0.1 is-at 0:4:e2:57:80:f6
...

But the client doesn't see any of the arp replies.  Furthermore
the client only sees one arp who-has per second, I'm puzzled why
the AP sees two.  The client works fine at work, so I don't think
I have to suspect that it's the client that's at fault.

Something else that confuses me is that if I run dhclient on one
of the client machines and the dhcpd on the AP machine sends back
a DHCPNAK, the client actually receives the DHCPNAK.  It doesn't
receive anything after that, though.

Let me know what to try next.

Thanks,
Johannes

To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-mobile" in the body of the message