From owner-freebsd-questions@FreeBSD.ORG Wed Nov 10 21:32:27 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E0AE16A4CE for ; Wed, 10 Nov 2004 21:32:27 +0000 (GMT) Received: from imo-m22.mx.aol.com (imo-m22.mx.aol.com [64.12.137.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7202243D3F for ; Wed, 10 Nov 2004 21:32:26 +0000 (GMT) (envelope-from TM4526@aol.com) Received: from TM4526@aol.com by imo-m22.mx.aol.com (mail_out_v37_r3.8.) id r.1d9.2f81063e (3924); Wed, 10 Nov 2004 16:31:54 -0500 (EST) From: TM4526@aol.com Message-ID: <1d9.2f81063e.2ec3e2c9@aol.com> Date: Wed, 10 Nov 2004 16:31:53 EST To: speisert@yahoo.com MIME-Version: 1.0 X-Mailer: 9.0 for Windows sub 5114 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: questions@freebsd.org Subject: Re: Two NICs with one IP address each on the same subnet X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Nov 2004 21:32:27 -0000 In a message dated 11/9/04 9:58:07 PM Eastern Standard Time, speisert@yahoo.com writes: "I have a FreeBSD 5.x box with two NICs that I'd like to set up on the same subnet. The purpose is to run separate services on each NIC. I have the box set up with my rc.conf containing the following lines: defaultrouter="..." hostname="..." ifconfig_xl0="inet ... netmask 255.255.255.224" ifconfig_sk0="inet ... netmask 255.255.255.224 mtu 9000" The router and IP addresses are all on the same subnet, as I previously mentioned. Unfortunately, the first IP address seems not to work (I can ssh to the second, but not the first). Is there something special I need to do to the routing to get this to work? Anything to the kernel? " ------- You are breaking the rules. The entire point of "routing" is that each segment is a different network. So you'll have to further subnet to do what you want. Or set up Bridging