From owner-freebsd-stable@FreeBSD.ORG Fri Feb 17 12:57:42 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 17E4216A420 for ; Fri, 17 Feb 2006 12:57:42 +0000 (GMT) (envelope-from TAFranck@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4B24743D45 for ; Fri, 17 Feb 2006 12:57:40 +0000 (GMT) (envelope-from TAFranck@gmx.net) Received: (qmail invoked by alias); 17 Feb 2006 12:57:40 -0000 Received: from dialer-147-177.kielnet.net (EHLO [192.168.1.103]) [82.97.147.177] by mail.gmx.net (mp031) with SMTP; 17 Feb 2006 13:57:40 +0100 X-Authenticated: #867087 From: "Thomas Franck" To: "Dominic Marks" Date: Fri, 17 Feb 2006 13:57:41 +0100 MIME-Version: 1.0 Message-ID: <43F5D655.8339.1080134@TAFranck.gmx.net> Priority: normal In-reply-to: <3432.195.12.22.194.1140179160.squirrel@www.helenmarks.co.uk> 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 12:57:42 -0000 On 17 Feb 2006 at 12:26, Dominic Marks wrote: > Tried these sysctls? > > net.link.ether.inet.log_arp_wrong_iface > net.link.ether.inet.log_arp_movements > net.link.ether.inet.log_arp_permanent_modify I set this in sysctl.conf now and did a reboot.. net.link.ether.inet.log_arp_wrong_iface = 0 and it works like expected.. no more messages of that kind... Thank you... :) Say.. this this flag is probably aware of run-time changes, too, hmm? so a "sysctl net.link.ether.inet.log_arp_wrong_iface=0" would have turned it off without reboot as well, right? How can an arp reply be received by the wrong interface, though? Isn't the request broadcast and the reply MAC addressed? I'm amazed - problem solved in less than 30 mins.. - Thomas