From owner-freebsd-stable Sun Apr 30 18:30:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from got.wedgie.org (got.wedgie.org [216.181.169.146]) by hub.freebsd.org (Postfix) with ESMTP id A800C37C090 for ; Sun, 30 Apr 2000 18:30:39 -0700 (PDT) (envelope-from jgarman@got.wedgie.org) Received: (from jgarman@localhost) by got.wedgie.org (8.9.3/8.9.3) id VAA93462 for stable@freebsd.org; Sun, 30 Apr 2000 21:30:35 -0400 (EDT) (envelope-from jgarman) Date: Sun, 30 Apr 2000 21:30:35 -0400 From: Jason Garman To: stable@freebsd.org Subject: bridging code problems with aliasing Message-ID: <20000430213035.A93390@got.wedgie.org> Reply-To: jgarman@wedgie.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i X-Phase-Of-Moon: The Moon is Waning Crescent (13% of Full) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The bridging code returns a random hw address from the interfaces which are bridged to arp requests. My bridge host has an IP x (bound to ed0), and every time an arp request is sent on the wire for x, either ed0's hw address is returned or fxp0's address is returned. This is mostly a minor annoyance most of the time, because the machine will answer arp requests on both ed0 and fxp0 regardless of the hw address it is currently "using." However, when an alias is added to the machine, if the machine currently "thinks" its hardware address is fxp0's hw address, it will not answer any arp requests from ed0. If the machine currently "thinks" its hardware address is ed0's hw address then it will answer all arp requests from both wires. So, basically, aliasing and bridging do not mix. Any clues? -- Jason Garman http://web.wedgie.org/ Student, University of Maryland jgarman@wedgie.org From fortune(1): Whois: JAG145 "... Had this been an actual emergency, we would have fled in terror, and you would not have been informed." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message