All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias DiPasquale <codeslinger@gmail.com>
To: Harald Welte <laforge@netfilter.org>,
	nf-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: CLUSTERIP and ProxyARP?
Date: Mon, 27 Jun 2005 06:50:28 -0400	[thread overview]
Message-ID: <876ef97a050627035063f5d929@mail.gmail.com> (raw)
In-Reply-To: <20050627090959.GE19928@sunbeam.de.gnumonks.org>

On 6/27/05, Harald Welte <laforge@netfilter.org> wrote:
> On Thu, Jun 23, 2005 at 06:36:08PM -0400, Tobias DiPasquale wrote:
> > Hi all,
> >
> > Does anyone know if ipt_CLUSTERIP and ProxyARP will work correctly
> > together on a current Linux kernel? Anything special to watch out for?
> > TIA :)
> 
> 1. all current linux kernel up to (and including 2.6.12) has a CLUSTERIP bug
>    anyway

What bug? Was it mentioned on this list earlier? I don't remember seeing it...

> 2. I didn't think about interoperability with  proxyarp when
>    implementing CLUSTERIP.  In fact, CLUSTERIP is meant to run on
>    end-hosts (Such as webservers), not on gateways.
> 
> CLUSTERIP mangles ARP requests (and replies) from/to the CLUSTER IP
> address.  So if you are proxy-ARP'ing for different IP addresses, it
> _should_ work.

I'm going to test it out today. I will let the list know the results. Thanks.

-- 
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d

  reply	other threads:[~2005-06-27 10:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23 22:36 CLUSTERIP and ProxyARP? Tobias DiPasquale
2005-06-27  9:09 ` Harald Welte
2005-06-27 10:50   ` Tobias DiPasquale [this message]
2005-06-27 11:11     ` Tobias DiPasquale
2005-06-27 11:40       ` Harald Welte
  -- strict thread matches above, loose matches on Subject: below --
2005-06-23 22:45 Tobias DiPasquale

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=876ef97a050627035063f5d929@mail.gmail.com \
    --to=codeslinger@gmail.com \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.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.