From: Alexander Samad <alex@samad.com.au>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Starting from scratch w/ multiple uplinks
Date: Mon, 09 May 2005 23:37:37 +0000 [thread overview]
Message-ID: <20050509233737.GC15049@samad.com.au> (raw)
In-Reply-To: <756AAB68-8733-4BF4-A78F-146966BD9E0F@mediarete.it>
[-- Attachment #1.1.1: Type: text/plain, Size: 1475 bytes --]
On Mon, May 09, 2005 at 04:06:12PM -0400, Brian J. Murrell wrote:
> On Mon, 2005-05-09 at 20:11 +0200, Markus Schulz wrote:
> > Am Montag, 9. Mai 2005 16:05 schrieb Rafael A Barrero:
> > > Hi guys;
> > >
> > [...]
> > > Here's what I want to know:
> > > 1. Does an updated guide exist for multiple providers?
> >
> > Look at this howto: http://www.ssi.bg/~ja/nano.txt
>
> Indeed, and herein contains the patched needed to a kernel for it to
> route packets with a given NATted source address out the right
> interface. Not sure which patch(es) exactly in there do it if not all
> of them are really needed for just that functionality.
I haven't pacthed mine and it seems to work, using a debian 2.6.11-3
source package.
What i have done is setup a set of files in
/var/run/multigw{,.dev,.gw,.ip,.speed}, this are feed from scripts in
/etc/ppp/ip-{up.d,down.d}/adsl - this populates the files with valid
numbers when the line goes up or deletes the control file when going
down. This scripts also run my multigw.sh which setups routes and ip
rules as well - also setups up the SNAT rules are well, I have attached
the script
>
> I sure wish this patch would get rolled into the main kernel. I hate
> having to maintain umpteen kernels for different tasks.
>
> b.
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
[-- Attachment #1.1.2: multidgw.sh --]
[-- Type: application/x-sh, Size: 4255 bytes --]
[-- Attachment #1.2: Digital signature --]
[-- 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 23:37 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
2005-05-09 18:11 ` Markus Schulz
2005-05-09 20:06 ` Brian J. Murrell
2005-05-09 23:37 ` Alexander Samad [this message]
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=20050509233737.GC15049@samad.com.au \
--to=alex@samad.com.au \
--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.