All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Rabbitson <rabbit@rabbit.us>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Load Balance and SNAT problem.
Date: Wed, 27 Jun 2007 08:03:01 +0000	[thread overview]
Message-ID: <468219B5.9060407@rabbit.us> (raw)
In-Reply-To: <7e47206b0706242007q487365d3gb7c12658b9669edd@mail.gmail.com>

Grant Taylor wrote:
> Well let me take a moment to be sure we are thinking the same thing. You 
> want the kernel to be able to realize that one route through a given 
> default gateway is no good for a given destination and use a different 
> default gateway even though the kernel can reach other destinations 
> through the first default gateway?  In other words, if the kernel can 
> not reach microsoft.com through ISP1 it should use ISP2 despite the fact 
> that it can reach google.com through ISP1?
> 

No, nothing like this. Basically my idea is that a no-packet-seen timer 
is maintained for every gateway, excluding any packets with a source 
within the ISPs netblock. This will reliably detect that no traffic is 
seen beyond the ISP, and therefore pronounce the gateway dead.

The only configuration required from the administrator would be an 
address/netmask pair for every gateway, to use as an exclusion for the 
counters, and a no-packets-seen timeout, before a gateway is marked as 
dead. Any incoming activity on the gateway will immediately change its 
status back to active.

So to answer your exact question - I want the kernel to be able to 
realize that a gateway is no good for any destinations other than the 
specified netblock.

Peter
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-06-27  8:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25  3:07 [LARTC] Load Balance and SNAT problem John Chang
2007-06-25 14:47 ` Grant Taylor
2007-06-25 21:30 ` VladSun
2007-06-26  6:46 ` Peter Rabbitson
2007-06-26 11:36 ` John Chang
2007-06-26 14:37 ` Grant Taylor
2007-06-26 15:04 ` Patrick Brandão
2007-06-26 17:44 ` Peter Rabbitson
2007-06-27  1:24 ` Grant Taylor
2007-06-27  1:51 ` Grant Taylor
2007-06-27  2:07 ` Grant Taylor
2007-06-27  2:22 ` Salim S I
2007-06-27  2:34 ` Grant Taylor
2007-06-27  2:39 ` Grant Taylor
2007-06-27  3:07 ` Salim S I
2007-06-27  3:16 ` Grant Taylor
2007-06-27  5:54 ` Peter Rabbitson
2007-06-27  6:41 ` Salim S I
2007-06-27  6:43 ` Grant Taylor
2007-06-27  6:58 ` Peter Rabbitson
2007-06-27  7:28 ` Grant Taylor
2007-06-27  7:37 ` Grant Taylor
2007-06-27  7:53 ` Grant Taylor
2007-06-27  7:57 ` Grant Taylor
2007-06-27  8:03 ` Peter Rabbitson [this message]
2007-06-27  8:03 ` Grant Taylor
2007-06-27  8:11 ` Grant Taylor
2007-06-27  8:24 ` Grant Taylor
2007-06-27  8:26 ` Grant Taylor
2007-06-27  9:09 ` Peter Rabbitson
2007-06-27 10:19 ` Grant Taylor

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=468219B5.9060407@rabbit.us \
    --to=rabbit@rabbit.us \
    --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.