On Sun, 11 Aug 2002, Sean Hamilton wrote:
> From: "Doug White" <[EMAIL PROTECTED]>
> > You should check that your network configuration is correct first, then
> > use tcpdump to locate the offender and report them to your provider. They
> > can ask the owner of said machine politely to install the patches or set
> > /proc flags to disable that behavior. You can, of course, comment out the
>
> Which /proc flags? Indeed it is a linux box, the firewall, which I have
> access to. My coworker, the administrator of this box, has simply turned a
> blind eye to this, on the grounds that it's not actually causing problems,
> just noise... but if it's a simple tweak, I'm sure he could be bribed with
> caffeine or somesuch.
I don't recall, its under /proc/sys/net most likely ... you can google for
it.
> > printfs, or hide it behind log_arp_wrong_iface which is controlled by the
> > sysctl net.link.ether.inet.log_arp_wrong_iface. The file you want to
> > modify in that case is src/sys/netinet/if_ether.c.
>
> Thanks, looks like that sysctl is what I've been looking for. Though you
> seem to indicate I would have to modify the kernel to achieve this, it seems
> to be that way already -- perhaps a recent thing? Regardless, I find it
> somewhat surprising my googling didn't point me in this direction.
log_arp_wrong_iface was in 4.5 I think, but you do need to do a minor hack
to put an if(){} block around the offending printf.
--
Doug White | FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
