All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Load Balance and SNAT problem.
Date: Wed, 27 Jun 2007 08:11:34 +0000	[thread overview]
Message-ID: <46821BB6.6000800@riverviewtech.net> (raw)
In-Reply-To: <7e47206b0706242007q487365d3gb7c12658b9669edd@mail.gmail.com>

On 6/27/2007 3:03 AM, Peter Rabbitson wrote:
> I want the kernel to be able to realize that a gateway is no good for
> any destinations other than the specified netblock.

Would it be fair to say that you are wanting an administratively 
configurable "ignore addresses that fall with in this <network>" while 
deciding if a gateway is dead?

Obviously <network> would need to be a bit more than just an ip / 
netmask combination to make this realistic.

If this is what you are wanting, it may be possible to augment the 
kernel code that is used to detect dead gateways and have it check to 
see if the networks match a list (from somewhere in proc / sysfs / 
sysctl?) and not increment traffic counters.  I am presuming that it is 
the traffic counters that have to be incremented for the kernel to think 
that a route is still alive.  So, if you purposfully did not increment 
the counters, you could probably detect that a given gateway is no good. 
  I think you would have to add an additional route that was to the 
given network(s) that did not use such a feature to provide a way for 
the routing code to route to those network(s) that it no longer would 
get to via a default gateway.

What do you think?



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

  parent reply	other threads:[~2007-06-27  8:11 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
2007-06-27  8:03 ` Grant Taylor
2007-06-27  8:11 ` Grant Taylor [this message]
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=46821BB6.6000800@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --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.