All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Largo Hellenz" <lamp@nyc.rr.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] 2 gateways out
Date: Sun, 23 Sep 2001 19:04:52 +0000	[thread overview]
Message-ID: <marc-lartc-100127205826757@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100119531523323@msgid-missing>

>-----Original Message-----
>From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]On
>Behalf Of bert hubert
>Sent: Sunday, September 23, 2001 10:59 AM
>To: lartc@mailman.ds9a.nl
>Subject: Re: [LARTC] 2 gateways ou


>>  the most important thing is to load balence between the two cable modems
>> and route all traffic out the right way if one of the cable modems goes
>> down.

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

yes. two different providers.

>This situation is very difficult to resolve properly, the best way is to
>experiment a bit. You will most probably need a cronscript to detect which
>modems are operating.

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?

but what if both are up? is this where policy routing steps in?
would policy routing replace any pinging cronscripts?

>Policy routing does this for you, and may in fact be the best solution.
>Route part of your customers to one modem, and others to the other, if both
>are functioning. If you detect that stuff is down, route everybody to the
>other one.

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?

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?


>> [root@io /root]# cat masquerade
>> #!/bin/sh
>>
>> modprobe ip_tables
>> modprobe ip_nat_ftp
>> modprobe ip_conntrack
>> modprobe ip_conntrack_ftp
>> modprobe iptable_nat

>Having modules autoload themselves is way easier, bt.

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

thanks,
Fernando Pando


_______________________________________________
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 19:04 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 [this message]
2001-09-23 20:00 ` bert hubert

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-100127205826757@msgid-missing \
    --to=lamp@nyc.rr.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.