From owner-freebsd-questions@FreeBSD.ORG Mon Jul 19 18:29:24 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 BEAB716A4CF for ; Mon, 19 Jul 2004 18:29:24 +0000 (GMT) Received: from iceberg.web-walrus.com (iceberg.web-walrus.com [169.207.176.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C40A43D46 for ; Mon, 19 Jul 2004 18:29:24 +0000 (GMT) (envelope-from custpriv@web-walrus.com) Received: from iceberg.web-walrus.com (localhost [127.0.0.1]) i6JHtlDH038891; Mon, 19 Jul 2004 12:55:47 -0500 (CDT) (envelope-from custpriv@web-walrus.com) Received: from localhost (custpriv@localhost)i6JHtk8Q038887; Mon, 19 Jul 2004 12:55:46 -0500 (CDT) X-Authentication-Warning: iceberg.web-walrus.com: custpriv owned process doing -bs Date: Mon, 19 Jul 2004 12:55:45 -0500 (CDT) From: "Web Walrus (Robert Wall)" To: Matthew Seaman In-Reply-To: <20040719112823.GC21175@happy-idiot-talk.infracaninophile.co.uk> Message-ID: <20040719124619.V19557@iceberg.web-walrus.com> References: <20040719040431.V19557@iceberg.web-walrus.com> <20040719043004.T19557@iceberg.web-walrus.com> <20040719112823.GC21175@happy-idiot-talk.infracaninophile.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD Questions Mail List cc: Nelis Lamprecht Subject: Re: Routing issue 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: Mon, 19 Jul 2004 18:29:24 -0000 > > > > ifconfig_dc0 inet 1.2.3.4 netmask 255.255.255.248 > > > > ifconfig_dc0_alias0 inet 2.3.4.5 netmask 255.255.255.248 > > > > defaultrouter="1.2.3.1" > > > > It's not on the same network; that's the problem. Two complete separate > > networks, same interface card. The issue is that one of the networks > > works, and the other doesn't, depending on what network the default router > > happens to be on. > > In general, you're going to need a mechanism for dynamically routing > packets in order to make this sort of setup work. For most setups, > you'ld need the co-operation of your ISP to make things work as well. The situation is this - there are 4 servers that are on one network. I'm trying to switch them over to another network, but I need to do it without downtime. Therefore, I need to have both IPs completely active and functional simultaneously. Would the situation be any easier if I put one of the networks on a separate NIC? Is there any way to determine what IP/interface a connection came in on, and continue to use that IP/interface for the outbound packets? Maybe with static routes or something of that nature? The thing is, I used this exact setup (albeit on two different network cards) on a FreeBSD 2.x box quite a ways back, for the same purpose (switching networks), and it was working fine.