From owner-freebsd-net  Tue Jul 11 16: 8:30 2000
Delivered-To: freebsd-net@freebsd.org
Received: from rapidnet.com (rapidnet.com [205.164.216.1])
	by hub.freebsd.org (Postfix) with ESMTP id 892EC37B979
	for <freebsd-net@freebsd.org>; Tue, 11 Jul 2000 16:08:21 -0700 (PDT)
	(envelope-from nick@rapidnet.com)
Received: from localhost (nick@localhost)
	by rapidnet.com (8.9.3/8.9.3) with ESMTP id RAA82914;
	Tue, 11 Jul 2000 17:08:15 -0600 (MDT)
Date: Tue, 11 Jul 2000 17:08:15 -0600 (MDT)
From: Nick Rogness <nick@rapidnet.com>
To: Trumpy <freebsd-q@cambridge.lh.net>
Cc: freebsd-net@freebsd.org
Subject: Re: Routed and multiple routes...
In-Reply-To: <Pine.SGI.4.21.0007111547250.10832-100000@cambridge.lh.net>
Message-ID: <Pine.BSF.4.21.0007111659340.77366-100000@rapidnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, 11 Jul 2000, Trumpy wrote:

> 2) Two default routes, one out to a router on the new
> subnet, and one out to a router on the old subnet, the
> first more preferenced such that if it goes down, default
> traffic will start going out to a router on the old subnet.

	I have had this problem before with 2 default routes to the same
	network for different gateways.  Read more below.

> I've tried running routed, but when I enter the default
> routes in /etc/gateways and then start routed, I get:
> 
>   Jul 11 16:06:47 god routed[26243] unreachable gateway 
>   192.168.0.254 in /etc/gateways
> 
	Haven't tried this with routed.  

> 
> 	    192.168.0.254               10.0.0.254
> 	     ___________                ___________
> 	     |  NEW    |                |   OLD   |
>              | BORDER  |----------------| BORDER  |
>              | ROUTER  |                | ROUTER  |
>              |_________|                |_________|
>                  |                           |
> 		 |			     |
> (preferred       |			     |
>      route)      |     ________________      |
> 		 |     | FreeBSD 3.4  |      |
> 		 |     |              |	     |	
> 192.168.0.25 ->	 ------|eth0      eth1|-------  <- 10.0.0.25
>                        |              |
> 		       |--------------|
> 
> Any ideas? Do I need to try gated?

	Gated may still not help much (haven't tried it).  This is what I
	have done in the past (easier):

	# Prefered gateway
	route add -net 0.0.0.0 -netmask 128.0.0.0 192.168.0.254
	route add -net 128.0.0.0 -netmask 128.0.0.0 192.168.0.254

	#Backup gateway
	route add -net 0.0.0.0 -netmask 0.0.0.0 10.0.0.254


	This will work because  the first 2 routes are more specific than
	the backup route...so it is the preferred route.  They
	still point to basically the same network, one is a supernetted
	version of the 2 smaller networks.

Nick Rogness
- Speak softly and carry a Gigabit switch.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message