On Sat, 17 Mar 2001, Nick Rogness wrote:
More clarification.
>
> > I completely fail to see that you have actually stated a problem yet.
> >
> > What exactly is the problem you think you're trying to solve here?
> >
>
> Consider the following. I have to restate this every damn couple
> of weeks to get it through. Here is the problem:
>
>
> ISP#1 ISP#2
> | |
> | |
> --- xl0 FreeBSD xl1 -----
> xl2
> |
> |
> Internal network
> |
> |
> Machine 1
>
>
> 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.
There is no way to tell your packet to go back out to ISP #2. That is the
point I'm trying to get across. Unless your running a routing
daemon. But is that really practical with cable modems, dsl, etc?...I
don't think so.
>
> What if you are running nat in this case....your hosed.
>
natd on each interface is what I'm stating here...just to clarify.
> You can check out route-cache at Cisco's online site. It may help
> to clarify as to why you would want to do this.
>
> If you check the -net mailing list this problem re-occurs over and
> over and over and over and over. To which there is a work around
> that's a bit messy.
Nick Rogness <[EMAIL PROTECTED]>
- Keep on routing in a Free World...
"FreeBSD: The Power to Serve!"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
