From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] route with different metric
Date: Wed, 26 Sep 2001 14:10:42 +0000 [thread overview]
Message-ID: <marc-lartc-100151343730843@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100150978014261@msgid-missing>
On Wed, Sep 26, 2001 at 03:53:23PM +0200, Juri Haberland wrote:
> > > If that works as intended, please let us know!
> >
> > I just tried and it does some funny things - still investigating...
>
> Ok, seems to work, but it looks like you have to have the default routes
> in the order of the interfaces, e.g.:
> eth0: 10.0.1.2 (/24)
> eth1: 10.0.2.2 (/24)
> ip route add default nexthop via 10.0.1.1 dev eth0 nexthop via 10.0.2.1
> dev eth1
I think that that's very unlikely. The important thing is: is this 'sticky'?
Is a single TCP session mated to a single route automatically? Or does MASQ
do this for you?
I've started writing a chapter on this subject.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-09-26 14:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 13:10 [LARTC] route with different metric Christian Lox
2001-09-26 13:13 ` bert hubert
2001-09-26 13:39 ` Christoph Simon
2001-09-26 13:45 ` Juri Haberland
2001-09-26 13:53 ` Juri Haberland
2001-09-26 14:10 ` bert hubert [this message]
2001-09-26 14:37 ` Juri Haberland
2001-09-26 18:05 ` Adrian Chung
2001-09-26 20:53 ` bert hubert
2001-09-26 21:16 ` Adrian Chung
2001-09-27 7:44 ` Juri Haberland
2001-09-27 22:40 ` Adrian Chung
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-100151343730843@msgid-missing \
--to=ahu@ds9a.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.