Date: Tue, 04 Aug 2009 11:47:09 -0700 From: Julian Elischer <julian@elischer.org> To: Jack Vogel <jfvogel@gmail.com> Cc: Jack F Vogel <jfv@freebsd.org>, freebsd-net@freebsd.org, d@delphij.net Subject: Re: em(4): sending ARP regardless of NOARP flag Message-ID: <4A78822D.1080507@elischer.org> In-Reply-To: <2a41acea0908041102h4249faa4r8db4f9178f0ca172@mail.gmail.com> References: <4A773D09.3030404@delphij.net> <2a41acea0908041011kaba6ab0ra6fec3b309fc42ef@mail.gmail.com> <4A786E80.5020201@elischer.org> <2a41acea0908041102h4249faa4r8db4f9178f0ca172@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jack Vogel wrote: > Ya, except that's when the hardware 'eats' the arp that the OS sends, > not one > where it sends one the OS doesn't want :) > > This is the first I've even heard of this option, but I can't see how its a > driver thing, either the stack sends an arp packet or it doesnt, right? noarp is supposed to stop it responding to arps too. it won't stop IPMI from doing it though. just an idea > > jack > > > On Tue, Aug 4, 2009 at 10:23 AM, Julian Elischer <julian@elischer.org > <mailto:julian@elischer.org>> wrote: > > Jack Vogel wrote: > > I don't see how arping or not can be a driver problem, the > driver just sends > packets queued by the stack, there exists NO mechanism to > communicate > that kind of thing down into the driver, -arp is something that > must be > negotiated in the stack somewhere, as for it working with > broadcom... > <shrugs> > > > except for the system management stuff. > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A78822D.1080507>