From: Adrian Chung <adrian@enfusion-group.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multipath, 2.4.16 + Julian's patches.
Date: Fri, 14 Dec 2001 15:52:28 +0000 [thread overview]
Message-ID: <marc-lartc-100834520922933@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100831072321841@msgid-missing>
On Fri, Dec 14, 2001 at 01:30:27PM -0200, Christoph Simon wrote:
> On Fri, 14 Dec 2001 10:02:50 -0500
> Adrian Chung <adrian@enfusion-group.com> wrote:
>
> > I didn't have trouble following the HOWTO, it was easy to follow. I'm
> > just not sure I understand the reasoning for having to do certain
> > steps, but that's not necessarily the goal of your HOWTO.
>
> Well, up to a certain point it is, as at least some understanding is
> necessary to apply this setup to different situations. For instance,
> in your last two messages you seem to have tried to test the load
> balancing with individual cases. As I wrote, this is not possible; you
> need a certain amount of traffic to see it. The reason is a rather
Actually, after I wrote my last couple of messages, I was thinking
about it more, and I think it's a misunderstanding that I have. Your
HOWTO is mainly geared towards load balancing, and failover when one
of the links goes down.
I'd like to do that, but I'd like to mainly use one link, and only
fall back (fail over) to the second link when the first goes down.
I tried to represent that using a greater weight on the first link,
but as I think it says in your HOWTO, this merely results in the
kernel adding more routes for the first link, and inevitably, I'm
guessing some traffic will still be routed through the second link
when the first is up.
My two links are through different ISP's, and I want to be able to use
both ISP's news, and proxy servers. In order to do this, I need to
make sure that when accessing ISP1's news server, I always connect via
the same link.
Load balancing defeats this, by sometimes routing to ISP1's news
server via ISP2, and then I get denied access because I don't have a
source IP on ISP1's network.
> Probably it's better to the list. I'm far from being an expert, and we
> all can learn something. Also, right now, I'm very busy and will not
> be able to modify that howto too soon.
A couple of things I'm unsure about:
1) is there a way to only use the second link if and when the first
goes down, instead of load balancing via both links all the time?
2) is it possible to implement source-based policy routing but fall
back to the second link when the preferred gateway is down?
Does any of this make sense?
--
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] up 134 days, 2:44, 2 users
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2001-12-14 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-14 6:17 [LARTC] Multipath, 2.4.16 + Julian's patches Adrian Chung
2001-12-14 11:09 ` Christoph Simon
2001-12-14 11:45 ` Julian Anastasov
2001-12-14 15:00 ` Adrian Chung
2001-12-14 15:02 ` Adrian Chung
2001-12-14 15:09 ` Adrian Chung
2001-12-14 15:30 ` Christoph Simon
2001-12-14 15:52 ` Adrian Chung [this message]
2001-12-14 16:15 ` Christoph Simon
2001-12-14 17:08 ` Adrian Chung
2001-12-14 17:10 ` Adrian Chung
2001-12-14 17:33 ` Julian Anastasov
2001-12-14 20:20 ` Adrian Chung
2001-12-14 21:24 ` Julian Anastasov
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-100834520922933@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.