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: Tue, 26 Jun 2007 14:37:26 +0000	[thread overview]
Message-ID: <468124A6.8000101@riverviewtech.net> (raw)
In-Reply-To: <7e47206b0706242007q487365d3gb7c12658b9669edd@mail.gmail.com>

On 06/26/07 01:46, Peter Rabbitson wrote:
> This is a bad bad advice in this day and age.

I think that is a bit of a bold statement.  You are free to have your 
opinion on what is better for you, as am I.

> If there are not enough users route caching will kill him. Here is a 
> recent discussion of this:
> http://marc.info/?l=lartc&m\x117912699505681&w=2

Um, I just read this discussion and I have a few issues with it.

First and foremost:  It did not cover the reason "... route caching will 
kill ..." to my satisfaction like you indicated.

Second:  It relies on user space processes to alter and maintain things. 
  Thus if for some reason these processes do not run or do not do so in 
a timely manner, they may not function correctly.

Third:  You are altering the way a running kernel is operating from user 
space, not letting the kernel maintain its self.

Fourth:  Occam's Razor dictates the use of the simpler and equally 
effective (equality is debatable) method to achieve the same result.

Though the method you site has potential, I think there is just as much 
room for improvement as there is in the method that I suggested.  Each 
method has its pros and cons.

> P.S. I am not insisting that netfilter is superior in this regard, I 
> am simply expressing common requirements and looking into ways of 
> achieving them.  If someone can point me to how to do this with 
> kernel routes - I am all ears, since I recognize that the netfilter 
> solution is not very elegant, although it works.

By your own statement, you are indicating that both methods leave 
something to be desired.



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

  parent reply	other threads:[~2007-06-26 14:37 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 [this message]
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
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=468124A6.8000101@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.