Gleb,
> A> I'm not an expert on networking, but is this condition of ignoring such an
> ARP packet really a noteworthy event? I.e. is this something that should not
> occur in "normal" operation according to the ARP specifications? If this is
> mostly for kernel developers, maybe it should only
Alexander,
On Thu, Nov 10, 2011 at 12:42:15PM -0500, Alexander Wittig wrote:
A> > Can you try attached patch. It reduces severity level of all ARP
A> > messages, that can be triggered by packet on network, with expection to
A> > "using my IP address".
A> >
A> > With default syslog.conf, now ARP
Alexander Wittig wrote:
>
> Nov 10 12:25:45 bt kernel: in_arp: 03:bf:23:09:44:e4 is multicast
> Nov 10 12:25:45 bt kernel: in_arp: 03:bf:23:09:44:87 is multicast
> [...]
>
> I'm not an expert on networking, but is this condition of ignoring
> such an ARP packet really a noteworthy event? I.e. is
Gleb,
Am 10.11.2011 um 01:51 schrieb Gleb Smirnoff:
> On Tue, Nov 08, 2011 at 05:14:45PM -0500, Alexander Wittig wrote:
> A> I upgraded one of my machines from FreeBSD 8 to 9.0-RC1 (FreeBSD
> bt.pa.msu.edu 9.0-RC1 FreeBSD 9.0-RC1 #3: Fri Oct 28 16:45:28 EDT 2011
> r...@bt.pa.msu.edu:/usr/ob
Alexander,
On Tue, Nov 08, 2011 at 05:14:45PM -0500, Alexander Wittig wrote:
A> I upgraded one of my machines from FreeBSD 8 to 9.0-RC1 (FreeBSD
bt.pa.msu.edu 9.0-RC1 FreeBSD 9.0-RC1 #3: Fri Oct 28 16:45:28 EDT 2011
r...@bt.pa.msu.edu:/usr/obj/usr/src/sys/ALEX i386), and ever since that
Hello
I upgraded one of my machines from FreeBSD 8 to 9.0-RC1 (FreeBSD bt.pa.msu.edu
9.0-RC1 FreeBSD 9.0-RC1 #3: Fri Oct 28 16:45:28 EDT 2011
r...@bt.pa.msu.edu:/usr/obj/usr/src/sys/ALEX i386), and ever since that
upgrade the kernel keeps flooding my log files with messages like these:
Nov
