From owner-freebsd-stable@FreeBSD.ORG Fri Feb 17 13:44:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6AA316A420 for ; Fri, 17 Feb 2006 13:44:04 +0000 (GMT) (envelope-from TAFranck@gmx.net) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 225AF43D48 for ; Fri, 17 Feb 2006 13:44:03 +0000 (GMT) (envelope-from TAFranck@gmx.net) Received: (qmail invoked by alias); 17 Feb 2006 13:44:02 -0000 Received: from dialer-147-177.kielnet.net (EHLO [192.168.1.103]) [82.97.147.177] by mail.gmx.net (mp015) with SMTP; 17 Feb 2006 14:44:02 +0100 X-Authenticated: #867087 From: "Thomas Franck" To: Chuck Swiger Date: Fri, 17 Feb 2006 14:44:04 +0100 MIME-Version: 1.0 Message-ID: <43F5E134.2791.13277DF@TAFranck.gmx.net> Priority: normal In-reply-to: <43F5CA7E.8030701@mac.com> References: <43F5C931.26653.D4AD6F@TAFranck.gmx.net> X-mailer: Pegasus Mail for Windows (4.31) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org Subject: Re: 2 NICs, SMP, weird kernel ARP messages X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2006 13:44:05 -0000 On 17 Feb 2006 at 8:07, Chuck Swiger wrote: > Thomas Franck wrote: > [ ... ] > > It doesn't seem to affect the function of the server, but it's > > mighty irritating and blows up the logs a lot... plus, I don't > > think it's supposed to show this behaviour.. :) > > > > I've going through the archives & web but the threads I found > > didn't fit my case.. :( > > The first two hits from Google were informative, but this is what > you want: the ones I found where about routing or two NICs on the same subnet.. anyway, none seem to relate to the behaviour I had.. or rather, give the sysctl mib in question.. > sysctl net.link.ether.inet.log_arp_wrong_iface=0 Yes.. that worked well.. > Your network would be better configured if separate subnets were > actually in separate collision domains, by using VLANs or an > individual hub/switch for each subnet. The error message is > useful to those people for whom it would be a genuine sign of > problems... they will be seperated again once our firewall is back & running and the standard router is taken off the net.. still, as I wrote in the reply to Dominic Marks: Isn't the request broadcast and the reply MAC addressed? if I'm right on that, the "problem" (it's more cosmetic, really) shouldn't have happened, right..? (at the moment the net looks like that: {FreeBSD} | | [sw1] [sw2] | | [switch3] | | | | | {me} | [router] the switch3 will be VLAN'ed again and properly connected once the firewall is back..) Thanks for the help.. - Thomas