From: Adrian Chung <adrian@enfusion-group.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] route with different metric
Date: Wed, 26 Sep 2001 18:05:42 +0000 [thread overview]
Message-ID: <marc-lartc-100152753229291@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100150978014261@msgid-missing>
On Wed, Sep 26, 2001 at 04:37:49PM +0200, Juri Haberland wrote:
> bert hubert wrote:
[...]
> > 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 just did a short test with ping. Ping went out through eth0. Then I
> issued a 'ifconfig eth0 down' while ping was running. It went out
> eth1...
I thought this sounded good, but I'm still concerned about what Bert
raises.
If this machine is also running daemons, does it send replies back out
the same interface they came in on? That'll break a lot of things if
you receive packets via ISP1, and send replies back via ISP2.
I still don't know how to handle that properly.
--
Adrian Chung (adrian at enfusion-group dot com)
http://www.enfusion-group.com/~adrian
GPG Fingerprint: C620 C8EA 86BA 79CC 384C E7BE A10C 353B 919D 1A17
[rogue.enfusion-group.com] 2:04pm up 55 days, 5:14, 3 users
_______________________________________________
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 18:05 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
2001-09-26 14:37 ` Juri Haberland
2001-09-26 18:05 ` Adrian Chung [this message]
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-100152753229291@msgid-missing \
--to=adrian@enfusion-group.com \
--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.