From owner-freebsd-stable  Sat Feb  3 14:27:32 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.64.180.171])
	by hub.freebsd.org (Postfix) with ESMTP
	id E42CD37B401; Sat,  3 Feb 2001 14:27:10 -0800 (PST)
Received: (from richw@localhost)
	by wyattearp.stanford.edu (8.9.3/8.9.3) id OAA86919;
	Sat, 3 Feb 2001 14:26:10 -0800 (PST)
	(envelope-from richw)
Date: Sat, 3 Feb 2001 14:26:10 -0800 (PST)
From: Rich Wales <richw@webcom.com>
X-Sender: richw@wyattearp.stanford.edu
To: freebsd-net@freebsd.org
Cc: freebsd-stable@freebsd.org
Subject: BRIDGE breaks ARP?
Message-ID: <20010203220223.86591.richw@wyattearp.stanford.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm running -STABLE (cvsup'ed on 26jan2001) on a machine with the
BRIDGE option, bridging between two PCI NICs (rl0 and xl0).

I'm having ARP problems.  Machines on the "rl0" card are unable to
get a hardware address for the bridge.  (For whatever reason, I have
no problems talking via the "xl0" interface.)

I've done "tcpdump" on the bridge, and it's receiving ARP queries on
the "rl0" interface, but it doesn't appear to be sending replies.  I
did a "tcpdump" on the "xl0" interface too, just in case ARP replies
were going out over the wrong interface, but no such luck.

If I turn off bridging (sysctl -w net.link.ether.bridge=0), the ARP
problem quickly resolves itself.  So the problem would seem to be
related somehow to the bridge code.

I can sidestep the problem by using "arp -s" commands on the other
machines to tell them the bridge's hardware address -- but I really
shouldn't have to do this.

Any ideas?

Rich Wales         richw@webcom.com         http://www.webcom.com/richw/



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message