From: Ralph van Etten <ralph@brothom.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Source based routing with two internet connections
Date: Wed, 04 Jul 2001 18:32:35 +0000 [thread overview]
Message-ID: <marc-lartc-99436436131811@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99418675705361@msgid-missing>
On Wed, 4 Jul 2001, Arthur van Leeuwen wrote:
> > #ip rule add from 192.168.11.70 table fast pref 102
> > #ip route add 0/0 dev eth2 table fast
> > #ip route flush cache
>
> You're not doing source address selection (the src argument to ip route add),
> causing the masquerading code to possibly select the wrong address to
> masquerade to. Check the archives for the postings on multipath upstream
> routing for information on a setup with multiple upstreams. Such a setup
> will gladly masquerade on each of the uplinks, and *work*. From that you can,
> without a doubt, simplify to your situation.
I've read the articles in the archive again and first I though of the
following :
#ip route add 0/0 src 123.123.123.123 dev eth2 table adsl
But this didn't worked, so I read some more and tried this :
#ip route add 123.123.123.1 dev eth2 table fast
#ip route add 0/0 via 123.123.123.123 dev eth2 table fast
with and without src argument and this gave exactly the same problem. Are
the above commands correct ?
Should the default route in the main table be a multipath route for
this to work ?
Thanks,
Ralph.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-07-04 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 18:59 [LARTC] Source based routing with two internet connections Ralph van Etten
2001-07-04 7:26 ` Arthur van Leeuwen
2001-07-04 18:32 ` Ralph van Etten [this message]
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=marc-lartc-99436436131811@msgid-missing \
--to=ralph@brothom.nl \
--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.