On Wed, Jun 18, 2003 at 09:36:17AM -0600, brook@biology.nmsu.edu wrote:
> [...]
> 
> Pings from the wireless host to the gateway yield the following arp
> traffic (selected from a long list of essentially identical packets),
> but no entries in the arp table on the wireless host.  Note that the
> wired host examining the network traffic is not the gateway being
> pinged.
> 
> wireless host: tcpdump -n -e -i wi0 
> 08:50:09.430209 0:2:2d:7b:17:c3 ff:ff:ff:ff:ff:ff 0806 42: arp who-has 128.123.94.1 tell 128.123.95.225
> 
> bridge: tcpdump -n -e -i wi0 host 128.123.95.225
> 08:50:06.852332 0:2:2d:7b:17:c3 ff:ff:ff:ff:ff:ff 0806 42: arp who-has 128.123.94.1 tell 128.123.95.225
> 08:50:06.864851 0:8:e3:f:59:9 0:2:2d:7b:17:c3 0806 60: arp reply 128.123.94.1 is-at 0:8:e3:f:59:9
> 
> wired host: tcpdump -n -e -i fxp0 host 128.123.95.225
> 08:50:06.880870 0:2:2d:7b:17:c3 ff:ff:ff:ff:ff:ff 0806 60: arp who-has 128.123.94.1 tell 128.123.95.225
> 
> >From all of this, I conclude the the bridge is passing packets in both
> directions, and that the wireless hosts is generating proper arp
> requests but is not receiving the responses.
> 
> - Is this the proper interpretation of these results?

Yes

> 
> - Is the bridge configured properly?

Looks to be

> 
> - How can I make this work correctly?

I don't know. I guess your second wireless machines (the one doing the
tcpdump) can't ping either ?
What happens if you run tcpdump on the box doing the ping ?

Maybe also try tcpdump -v

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 24 ans d'experience feront toujours la difference
--