Date: Mon, 5 Feb 2001 02:34:46 +0100 From: Stefan `Sec` Zehl <sec@42.org> To: Rich Wales <richw@webcom.com> Cc: freebsd-stable@freebsd.org Subject: Re: BRIDGE breaks ARP? (more info) Message-ID: <20010205023446.A28259@matrix.42.org> In-Reply-To: <20010204162724.04832.richw@wyattearp.stanford.edu>; from richw@webcom.com on Sun, Feb 04, 2001 at 05:36:03PM %2B0100 References: <Pine.NEB.3.96L.1010204105615.65610B-100000@fledge.watson.org> <20010204162724.04832.richw@wyattearp.stanford.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 04, 2001 at 05:36:03PM +0100, Rich Wales wrote:
> I should add something else. My bridge =does= pass ARP info between
> the two bridged NIC's. Thus, for example, a machine on the "rl0" side
> of the bridge can successfully use a default Internet gateway which is
> on the "xl0" side of the bridge (and "arp -a" on the rl0-side machine
> shows the hardware address of the xl0-side gateway).
>
> So the problem doesn't seem to have anything to do with ARP bridging.
> Even though ARP packets are being passed through the bridge, the bridge
> itself doesn't reply to ARP requests asking it for its own MAC address.
> (Or, to be more precise, it sometimes does send out ARP replies, but
> only sporadically and unpredictably.)
Just to acknowledge that you're not alone. I have the exact problem
since upgrading from 3.x to 4.x.
the bridge didn't send arp answers for itself on some of the interfaces.
I didn't have time to mess with that or debug it any further, and just
instructed another box on the same ethernet to do arp for the bridge
with 'arp -s ... pub' which is indeed an ugly workaround, but at least
it works.
CU,
Sec
--
Black holes are where GOD is dividing by zero
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010205023446.A28259>