Date: Tue, 4 Aug 2009 11:02:44 -0700 From: Jack Vogel <jfvogel@gmail.com> To: Julian Elischer <julian@elischer.org> 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: <2a41acea0908041102h4249faa4r8db4f9178f0ca172@mail.gmail.com> In-Reply-To: <4A786E80.5020201@elischer.org> References: <4A773D09.3030404@delphij.net> <2a41acea0908041011kaba6ab0ra6fec3b309fc42ef@mail.gmail.com> <4A786E80.5020201@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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? jack On Tue, Aug 4, 2009 at 10:23 AM, Julian Elischer <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?2a41acea0908041102h4249faa4r8db4f9178f0ca172>