From owner-freebsd-questions@FreeBSD.ORG Tue Jun 5 18:38:08 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0ACEC16A41F for ; Tue, 5 Jun 2007 18:38:08 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from smtp803.mail.ird.yahoo.com (smtp803.mail.ird.yahoo.com [217.146.188.63]) by mx1.freebsd.org (Postfix) with SMTP id 79EB113C45E for ; Tue, 5 Jun 2007 18:38:07 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: (qmail 12845 invoked from network); 5 Jun 2007 18:38:06 -0000 Received: from unknown (HELO ?192.168.1.2?) (thomasjudge@btinternet.com@217.44.143.76 with plain) by smtp803.mail.ird.yahoo.com with SMTP; 5 Jun 2007 18:38:05 -0000 X-YMail-OSG: N.fUT9oVM1mn.YXjtSxys44dbzUD2Ww.xV33BYdsZPrxG9GT Message-ID: <4665AE60.7080908@tomjudge.com> Date: Tue, 05 Jun 2007 19:41:36 +0100 From: Tom Judge User-Agent: Thunderbird 1.5.0.10 (X11/20070306) MIME-Version: 1.0 To: John Nielsen References: <46654109.8070507@careytech.com.au> <20070605135733.bju5l1fioc40c00c@newwebmail.jnielsen.net> In-Reply-To: <20070605135733.bju5l1fioc40c00c@newwebmail.jnielsen.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org, ivan@careytech.com.au Subject: Re: How to correctly use 2 on board nics X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2007 18:38:08 -0000 John Nielsen wrote: > Quoting Ivan Carey : >> I have a server board with 2 onboard nic's >> I have set them up in rc.conf as follows >> >> defaultrouter="192.168.1.1" >> network_interfaces="em0 em1 lo0" >> ifconfig_em0="inet 192.168.1.3 netmask 255.255.255.0" >> ifconfig_em1="inet 192.168.1.4 netmask 255.255.255.0" >> >> The question, is this the correct configuration? > > Manually specifying network_interfaces is deprecated (take that line > out). Putting both NIC's on the same subnet and segment but with > different IP's like this may not be too useful.. > >> If I have both nic's connected to the switch I can ping 192.168.1.1 >> and 192.168.1.3 and 192.168.1.4 >> >> If I have only em0 connected I can ping 192.168.1.1 and 192.168.1.3 >> >> If I have only em1 connected I can ping 192.168.1.3. > > That is because the route to 192.168.1.1 is associated with em0 at this > point. > >> What could the 2 onboard nic's be best used for. I was thinking that >> in the event on was to fail then the other would still be ok. > > For that to be most useful you'll want to set something up so they can > share the same IP. The lagg(4) (link aggregation) virtual interface has > already been mentioned, but I believe it is still only available in > -CURRENT. Other possibilities might include attaching ifconfig scripts > to link up/down events or [lack of] ping responses on one or both > interfaces. > > JN I thought I saw if_lagg MFC'd to RELENG_6 a few weeks back on cvs-src@... After checking cvsweb it is available in RELENG_6. Tom