From owner-freebsd-stable Mon Jan 29 22:21:18 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 5F98137B400 for ; Mon, 29 Jan 2001 22:21:01 -0800 (PST) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id WAA80815; Mon, 29 Jan 2001 22:20:33 -0800 (PST) (envelope-from richw) Date: Mon, 29 Jan 2001 22:20:33 -0800 (PST) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: Bridge and ARP problem? Message-ID: <20010130060046.80489.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 at home which I've configured as a bridge (options BRIDGE). After some problems with a PnP ISA network card ("ed" driver), I'm running more or less successfully, bridging between two PCI NICs ("xl0" to the Internet, and "rl0" to an internal network). Now, though, I'm having ARP problems. A machine on the "rl0" NIC is unable to get a hardware address for the bridge ("arp -a" shows the bridge's ARP entry as "incomplete"). If I turn off bridging (sysctl -w net.link.ether.bridge=0), the ARP problem quickly resolves itself and the two affected machines can talk to each other. So the problem would seem to be related to the bridge code. For whatever reason, the bridge is having no problems talking over its other interface (xl0). I can sidestep the problem by doing an "arp -s" command on the other machine to tell it the bridge's hardware address -- but I 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