All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Simon <ciccio@kiosknet.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multipath, 2.4.16 + Julian's patches.
Date: Fri, 14 Dec 2001 16:15:50 +0000	[thread overview]
Message-ID: <marc-lartc-100834666027058@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100831072321841@msgid-missing>

On Fri, 14 Dec 2001 10:52:28 -0500
Adrian Chung <adrian@enfusion-group.com> wrote:

> 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.

You are right, this is a quite different situation. It worked for me
like that before installing Julian's patches. I had no multipath route,
but explicit routes to the gateways and never more than one default
route. Then I had a daemon running which ping'ed the gateways and
would delete the default route to put the other. But this is loosing
the bandwidth of a line which is being payed, so I was unhappy with
that solution. Unfortunately, I don't know which is the best routing
setup for your case. Maybe somebody else on this list can give you a
hint.

> 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.

You should be able to add an explicit host route in table main. That
is hit before the multipath route is queried. You do know the IP
of that ISP's news server, do you?

> 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?

As I said above, the contrary was the aim of my setup. I would imagine
that the solution is not using a multipath route but just two default
routes with different priority. If the first is working, it should be
used always; if it goes down, the second would be used. And if the
first comes up again, thanks to Julian's patches, it should be used
again. But note, that for this last step to work, I think you still
need to ping/arping the gateways, such that there is a chance to
detect that the failing link is up again.

> 2) is it possible to implement source-based policy routing but fall
> back to the second link when the preferred gateway is down?

I think it is, using two default routes with different priority.

> Does any of this make sense?

Unless you have to pay for traffic on one link and not on the other,
I'm not sure why you would want to leave a link unused. Beside that, I
think it does make sense.


--
Christoph Simon
ciccio@kiosknet.com.br
---
^X^C
q
quit
:q
^C
end
x
exit
ZZ
^D
?
help
.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  parent reply	other threads:[~2001-12-14 16:15 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
2001-12-14 16:15 ` Christoph Simon [this message]
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-100834666027058@msgid-missing \
    --to=ciccio@kiosknet.com.br \
    --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.