From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Starting from scratch w/ multiple uplinks
Date: Mon, 09 May 2005 16:19:21 +0000 [thread overview]
Message-ID: <1115655561.18871.79.camel@pc> (raw)
In-Reply-To: <756AAB68-8733-4BF4-A78F-146966BD9E0F@mediarete.it>
[-- Attachment #1.1: Type: text/plain, Size: 1189 bytes --]
On Mon, 2005-05-09 at 16:05 +0200, Rafael A Barrero wrote:
> Hi guys;
>
> I'm sure you are all bored of hearing the same story over and over...
> but here it comes again. :) Yep, tomorrow I'm getting another ADSL
> line installed and I wanted my linux router to handle both providers
> (new and old). I have my linux router (fedora core 2) setup to do NAT
> for my current line, but I know I'll need to change my configuration
> to accommodate the second line.
I inquired about this a while ago and the final word seemed to be that
in order for you to use two uplinks, both NATting the internal
outbound-originated traffic (i.e. clients behind the gateway going to
Internet based services) and both accepting inbound-originated traffic
(i.e. running services behind the NAT for Internet users to use), one
needs to patch the kernel.
I could not seem to get the traffic leaving the gateway to go via the
uplink that was relevant for it's NATted source. All traffic wanted to
leave by only one interface even though it was NATted for the other. Of
course the upstream dropped the packets because the source address
violated their egress filters.
b.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-05-09 16:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 14:05 [LARTC] Starting from scratch w/ multiple uplinks Rafael A Barrero
2005-05-09 14:30 ` Sylvain BERTRAND
2005-05-09 15:14 ` Rafael A Barrero
2005-05-09 15:53 ` Markus Feilner
2005-05-09 15:58 ` Sylvain BERTRAND
2005-05-09 16:19 ` Brian J. Murrell [this message]
2005-05-09 18:11 ` Markus Schulz
2005-05-09 20:06 ` Brian J. Murrell
2005-05-09 23:37 ` Alexander Samad
2005-05-10 9:33 ` Rafael A Barrero
2005-05-10 10:12 ` Marc Manthey
2005-05-10 11:02 ` Markus Feilner
2005-05-10 11:11 ` Sylvain BERTRAND
2005-05-10 11:13 ` Robert Vangel
2005-05-10 12:07 ` Robert Vangel
2005-05-10 12:19 ` Marc Manthey
2005-05-10 12:39 ` Paulo Andre
2005-05-10 12:56 ` Markus Schulz
2005-05-10 13:00 ` Markus Schulz
2005-05-10 13:04 ` Paulo Andre
2005-05-10 13:40 ` Markus Schulz
2005-05-10 14:08 ` Rafael A Barrero
2005-05-10 15:10 ` Markus Feilner
2005-05-10 23:53 ` Alexander Samad
2005-05-11 0:02 ` Alexander Samad
2005-05-11 17:45 ` Markus Schulz
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=1115655561.18871.79.camel@pc \
--to=brian@interlinx.bc.ca \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.