From owner-freebsd-net  Sat Mar 17 11:37:58 2001
Delivered-To: freebsd-net@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id 44E9637B719
	for <freebsd-net@FreeBSD.ORG>; Sat, 17 Mar 2001 11:37:54 -0800 (PST)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA75388;
	Sat, 17 Mar 2001 14:37:33 -0500 (EST)
	(envelope-from wollman)
Date: Sat, 17 Mar 2001 14:37:33 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200103171937.OAA75388@khavrinen.lcs.mit.edu>
To: Nick Rogness <nick@rogness.net>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: same interface Route Cache
In-Reply-To: <Pine.BSF.4.21.0103171002500.16887-100000@cody.jharris.com>
References: <3AB3882D.5EAC34@softweyr.com>
	<Pine.BSF.4.21.0103171002500.16887-100000@cody.jharris.com>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

<<On Sat, 17 Mar 2001 10:28:25 -0600 (CST), Nick Rogness <nick@rogness.net> said:

> 	Packet 1 comes in through ISP #2 network.  It comes into your
> 	internal network to machine 1.  Machine 1 replies to the
> 	packet...but where does it go?  It will exit through interface 
> 	to ISP #1 because of the default gateway.  It came in ISP #2 and
> 	left out ISP #1.  There is your problem.

That's the way Internet routing is supposed to work.  If your routing
table says a packet supposed to go one way, and it really needs to go
another way, that's *user error* -- if you misconfigure your routing,
FreeBSD will do what you ask it to; it can't read your mind!

-GAWollman


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