From owner-freebsd-stable@FreeBSD.ORG Fri Feb 17 14:43:06 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 2989F16A420 for ; Fri, 17 Feb 2006 14:43:06 +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 5E45643D45 for ; Fri, 17 Feb 2006 14:43:05 +0000 (GMT) (envelope-from TAFranck@gmx.net) Received: (qmail invoked by alias); 17 Feb 2006 14:43:03 -0000 Received: from dialer-147-177.kielnet.net (EHLO [192.168.1.103]) [82.97.147.177] by mail.gmx.net (mp019) with SMTP; 17 Feb 2006 15:43:03 +0100 X-Authenticated: #867087 From: "Thomas Franck" To: Chuck Swiger Date: Fri, 17 Feb 2006 15:43:06 +0100 MIME-Version: 1.0 Message-ID: <43F5EF0A.31646.16880A2@TAFranck.gmx.net> Priority: normal In-reply-to: <43F5D6F0.8030609@mac.com> References: <43F5E134.2791.13277DF@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 14:43:06 -0000 On 17 Feb 2006 at 9:00, Chuck Swiger wrote: > [...] > ARPOP_REQUESTs are made to the all-ones broadcast MAC address, > and ARPOP_REPLYs go back addressed to the sender's MAC. Yes, that's what I was saying... good - so I haven't suddenly forgotten networking... :) > FreeBSD notes when ARP traffic is seen which indicates that a > MAC is moving being on one NIC to another. Ahhh.. I think I know what the messages meant then.. The server saw the broadcasts of the other PCs here - but they where coming in on a different NIC than FreeBSD's ARP cache is saying it should be.. It's not bad behaviour at all.. the Kernel is just concerned about the weird broadcasts that are on the net.. If I got that right - sorry for the noise and thanks for the knowledge... :) > Unless you take special measures (ng_fec?), one does not > normally connect two NICs on one machine to the same collision > domain. Hmm.. don't really see a problem with that.. two NICs with diffent IP on the same subnet.. binding say, a webserver and a database to different NICs... takes load off the single NIC, giving 100MBit to each service... > By default, some other hardware (like Suns), will even use the > same MAC address for every NIC on the machine.... Uhh.. that's nasty.. :) - Thomas