From: Mike Fedyk <mfedyk@matchmail.com>
To: Linux Advanced Routing and Trafic Control <lartc@mailman.ds9a.nl>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [Fwd: [LARTC] 1 adsl + 1 sdsl + masq + simultaneous incomming routes]
Date: Fri, 02 Mar 2001 19:38:08 -0800 [thread overview]
Message-ID: <3AA06720.77D94BFE@matchmail.com> (raw)
phil@optimumdata.com wrote:
>
> On Fri, 2 Mar 2001, Mike Fedyk wrote:
>
> > I have two dsl links, each with one ip, and a single gateway is assigned the ip
> > for each.
> >
> > ______ ______
> > | ADSL | | SDSL |
> > |______| |______|
> > \ /
> > \/
> > ___||____
> > | gateway |
> > |_________|
> > ||
> > ||
> > ||
> > _||__
> > | web |
> > |_____|
> >
> > OK.
> >
> > The problem: I am able to have the web server use one or the other dsl, but not
> > both at the same time.
> >
> > If I have web set to sdsl, replies to queries that came from adsl go out on the
> > sdsl link. Also since masq is involved, it also responds with the sdsl ip.
> >
> > How can I have replies go back on the correct internet link? OH, btw, the web
> > server is NT, so I won't be able to modify any packets there...
>
> What I've done is to put two IPs on the server (your web server, in this
> case). You would then have the gateway send one IP out via ADSL, and the
> out via SDSL.
>
> There is no way I know of to make that work.
>
> --
> -----------------------------------------------------------------------
> Phil Brutsche phil@optimumdata.com
There has to be a better way. I'm forwarding this to LKML. Maybe they have a
better idea...
I know the kernel keeps a route cache, is there something like a reverse MASQ
feature somewhere. Storing which incoming route + port number and keeping a
dynamic list...
TIA,
Mike
next reply other threads:[~2001-03-03 3:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 3:38 Mike Fedyk [this message]
2001-03-03 4:15 ` [Fwd: [LARTC] 1 adsl + 1 sdsl + masq + simultaneous incomming routes] Jeremy Jackson
2001-03-03 5:46 ` phil
2001-03-03 6:02 ` David
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3AA06720.77D94BFE@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=lartc@mailman.ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox