All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 2 gateways out
Date: Sun, 23 Sep 2001 20:00:03 +0000	[thread overview]
Message-ID: <marc-lartc-100127523801476@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100119531523323@msgid-missing>

On Sun, Sep 23, 2001 at 03:04:52PM -0400, Largo Hellenz wrote:

> >This depends greatly on what's on the other side of the cable modems - are
> >there two separate ISPs?
> 
> yes. two different providers.

Ok. This rules out a lot of fancy tricks.

> so i would ping both of my two gateways via the cronscripts and, if the
> current
> default gateway is down, and the standby is up, then change default gateway?

With policy routing, you can have multiple default gateways.

> so policy routing dynamically routes based upon available paths on the fly?
> could anyone provide an example that just cuts traffic equally between the
> two?

Well, you could try something like this:

# ip route add default nexthop via 10.0.0.1 dev eth0 \
	nexthop via 10.0.0.202 dev eth1

Not sure if this is 'sticky'. This might just assign TCP sessions to a
single cablemodem, then again, it might not. I would vote against this. Your
users would also fall victim to the 'AOL Proxy Problem'. In the midst of
browsing a site, they continually appear from two different IP addresses,
which may upset loadbalancing tools.


> lets say someone was was browsing cars.com and it was 10 hops from one ISP
> but only 5 from the other.... can policy routing tell those packets to use
> the shorter path?  or is this something that routing daemons are for?
> or is there another way to solve this puzzle?

You could try tricks with squid, which has been known to have some kind of
support for this. Your best best is to have multiple route tables, and route
these tables differently.

This page appears to be relevant: 

              http://mlarchive.ima.com/linux-net/1999/3495.html

> do you mean droping these commands in an init script so they always come up
> at boot time? or something else?

These modules can be autoloaded by the kernel. Make sure that you have
modutils 2.4.x!

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/

      parent reply	other threads:[~2001-09-23 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-22 21:45 [LARTC] 2 gateways out Largo Hellenz
2001-09-23 14:59 ` bert hubert
2001-09-23 19:04 ` Largo Hellenz
2001-09-23 20:00 ` bert hubert [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-100127523801476@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.