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 <jul...@elischer.org
<mailto:jul...@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.
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
