From: Simon Horman <horms@verge.net.au>
To: Michal Humpula <michal.humpula@hudrydum.cz>
Cc: "Rémi Denis-Courmont" <remi@remlab.net>, netdev@vger.kernel.org
Subject: Re: nonlocal_bind & IPv6
Date: Sat, 26 Jun 2010 23:25:40 +1000 [thread overview]
Message-ID: <20100626132540.GA30133@verge.net.au> (raw)
In-Reply-To: <201006252110.08508.michal.humpula@hudrydum.cz>
On Fri, Jun 25, 2010 at 09:10:08PM +0200, Michal Humpula wrote:
> Ok, more detail example.
>
> Let on each node be an apache (just for an example), and you configure
> VirtualHost for specific IP. So when node A fails, keepalived move IP to
> the node B and everything is still running. No need for restart of apache
> or anything else. There is a probably a better solution, but I can't find
> anything more simple than the posted patch:)
Not an answer to your original question, but that sounds like a problem
that can be resolved using IP_TRANSPARENT. Although I have only tested
that feature in conjunction with IPv4, it seems to support IPv6 too.
See Documentation/networking/tproxy.txt
next prev parent reply other threads:[~2010-06-26 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 18:43 nonlocal_bind & IPv6 Michal Humpula
2010-06-25 18:59 ` Rémi Denis-Courmont
2010-06-25 19:10 ` Michal Humpula
2010-06-26 13:25 ` Simon Horman [this message]
2010-06-26 20:42 ` Michal Humpula
2010-06-30 4:48 ` Simon Horman
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=20100626132540.GA30133@verge.net.au \
--to=horms@verge.net.au \
--cc=michal.humpula@hudrydum.cz \
--cc=netdev@vger.kernel.org \
--cc=remi@remlab.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).