From owner-freebsd-net Sun Feb 4 8:35:29 2001 Delivered-To: freebsd-net@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.64.180.171]) by hub.freebsd.org (Postfix) with ESMTP id 6DD0637B401; Sun, 4 Feb 2001 08:35:10 -0800 (PST) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id IAA05523; Sun, 4 Feb 2001 08:35:00 -0800 (PST) (envelope-from richw) Date: Sun, 4 Feb 2001 08:35:00 -0800 (PST) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: Robert Watson Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: BRIDGE breaks ARP? (more info) In-Reply-To: Message-ID: <20010204162724.04832.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Robert Watson wrote: > There used to be a kludge that mapped the ether_header.ether_type > field of non-IP packets into the UDP port number for the purposes > of certain IPFW rules when bridging. This was pretty awful. :-) 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.) Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message