From owner-freebsd-stable@FreeBSD.ORG Fri Feb 17 13:07:22 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 B28A516A42A for ; Fri, 17 Feb 2006 13:07:22 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2762F43D93 for ; Fri, 17 Feb 2006 13:07:11 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/8.12.11/smtpout06/MantshX 4.0) with ESMTP id k1HD7B58008022; Fri, 17 Feb 2006 05:07:11 -0800 (PST) Received: from [192.168.1.3] (pool-68-161-67-103.ny325.east.verizon.net [68.161.67.103]) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 4.0) with ESMTP id k1HD78Ma019301 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Feb 2006 05:07:10 -0800 (PST) Message-ID: <43F5CA7E.8030701@mac.com> Date: Fri, 17 Feb 2006 08:07:10 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Thomas Franck References: <43F5C931.26653.D4AD6F@TAFranck.gmx.net> In-Reply-To: <43F5C931.26653.D4AD6F@TAFranck.gmx.net> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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:07:23 -0000 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: sysctl net.link.ether.inet.log_arp_wrong_iface=0 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... -- -Chuck