From owner-freebsd-questions@FreeBSD.ORG Wed Jun 22 08:14:57 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78BB51065704 for ; Wed, 22 Jun 2011 08:14:57 +0000 (UTC) (envelope-from bernt@bah.homeip.net) Received: from feeder.usenet4all.se (1-1-1-38a.far.sth.bostream.se [82.182.32.53]) by mx1.freebsd.org (Postfix) with ESMTP id EAB4B8FC14 for ; Wed, 22 Jun 2011 08:14:56 +0000 (UTC) Received: from kw.homeip.net (c80-217-64-49.bredband.comhem.se [80.217.64.49]) by feeder.usenet4all.se (8.13.1/8.13.1) with ESMTP id p5M8Enq2021526; Wed, 22 Jun 2011 10:14:51 +0200 (CEST) (envelope-from bernt@bah.homeip.net) Message-ID: <4E01A478.3020101@bah.homeip.net> Date: Wed, 22 Jun 2011 10:14:48 +0200 From: Bernt Hansson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; sv-SE; rv:1.9.2.17) Gecko/20110508 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Damien Fleuriot References: <201106211128.p5LBSvCe095130@x.it.okstate.edu> <4E0196E4.2060900@bah.homeip.net> <4E019DAD.2070608@my.gd> In-Reply-To: <4E019DAD.2070608@my.gd> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Two Networks on one System 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: Wed, 22 Jun 2011 08:14:57 -0000 2011-06-22 09:45, Damien Fleuriot skrev: > On 6/22/11 9:16 AM, Bernt Hansson wrote: >> 2011-06-21 13:28, Martin McCormick skrev: >>> Here is what the issue is right now. The remote campus >>> in question has been on number space that was part of our Class >>> B network. They got a block of subnets for their DNS's and >>> campus enterprises and work stations. We secured them their own >>> number space and they are migrating from their portion of our >>> network to their new network and both nets are presented >>> routable from the rest of the world. >>> >>> If you do a whois query for their domain, you get the >>> address on our network of their primary DNS. When one updates >>> the whois data, there is a lag of some hours until new queries >>> start going to the new address of their primary DNS. In the mean >>> time, we don't really care but we would like for the new >>> interface for the primary to be reachable so that the minute the >>> information changes, we're answering lookups. After that point, >>> we will permanently take down the old interface address on our >>> network and probably reboot with the normal configuration now >>> being the new IP address. >>> >>> The problem I have, probably due to a misunderstanding >>> of what I need to do, is easy to describe. >>> >>> The defaultrouter statement in rc.conf or >> >>> route add default x.x.x.x >> >> Have you tried route add netA netB or route add netB netA >> >> > > No offense but please do not give random, untested advice. No offense, but it is tested. route add 192.0.0.192 10.0.0.3 Works like a charm. > What you just wrote reads as: > - if you want to go to network A, do that through network B > - if you want to go to network B, do that through network A And the OP whanted that. > Now can you see some kind of a loop forming here ? No, not really.