Date: Mon, 5 Feb 2001 16:33:53 -0800 (PST) From: Luigi Rizzo <rizzo@aciri.org> To: richw@webcom.com (Rich Wales) Cc: rizzo@aciri.org, julian@elischer.org, patrick@netzuno.com, freebsd-net@FreeBSD.ORG, julian@FreeBSD.ORG Subject: Re: Almost fixed (was Re: BRIDGE breaks ARP? (Julian's patch)) Message-ID: <200102060033.f160Xrt33550@iguana.aciri.org> In-Reply-To: <20010205234036.74638.richw@wyattearp.stanford.edu> from Rich Wales at "Feb 5, 2001 4:12:28 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> Good news and bad news. > > First the good news: > > The bridge is answering ARP requests for its own hardware address > on the internal (rl0) interface now. expected :) > Now the bad news: > > ARP replies from the bridge to the DSL modem (via the external > i/f) are still getting sent to the desktop (via the internal i/f), this is a bit less expected -- because the reply is unicast to the MAC of the host requesting the packet, and ether_output() is called with the correct interface pointer. What do you have in net.link.ether.bridge_cfg , and do you also see the ARP reply on the 'external' side (i suppose so) ? cheers luigi > and the desktop is using them to change its idea of the bridge's > hardware address. This causes a log message like the following: > > /kernel: arp: 171.66.188.114 moved from 00:e0:29:68:64:3e > to 00:60:97:05:32:cd on rl0 > > The desktop can contact the bridge using either of the bridge's > hardware addresses, of course -- but I still think the bridge > ought to send out its ARP replies =only= on the interface from > which the query came that the bridge is replying to. > > FWIW, the desktop is still running 4.2-RELEASE. > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102060033.f160Xrt33550>