From: Einar Lueck <elueck@de.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net/ipv4 for Source VIPA support, kernel BK Head
Date: Thu, 2 Sep 2004 14:01:42 +0200 [thread overview]
Message-ID: <200409021401.42255.elueck@de.ibm.com> (raw)
On Mer, 2004-09-01 at 14:25, ?Alan Cox wrote:
> Is there anything here that cannot already be done by the ip route
> command and iptables nat ?
Our experiences with customers operating high-available enterprise
installations indicate that ip route and iptables nat do not fullfill all the
relevant requirements:
The high-availability requirements drive those customers to ensure that
all routes are dynamic which is not possible with the proposed ip route
approach.
The complexity of the relevant setups necessitates an easy and
requirements-driven configuration and solution approach. The overall
concept of setting up a virtual device with a virtual IP adress and
assigning this virtual IP adress as a Source VIPA to the devices which should
allow for a failover is well known from other operating system and expected
by relevant enterprise customers. IP routes and NAT allow to achieve the
same effect with the exception mentioned above, but the corresponding
configuration overhead is in the opinion of customers having enterprise
setups too complex and complicated. Our overall approach introduces
this concept as a facility to address these requirements very clearly.
Einar
next reply other threads:[~2004-09-02 12:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 12:01 Einar Lueck [this message]
2004-09-02 11:05 ` [PATCH] net/ipv4 for Source VIPA support, kernel BK Head Alan Cox
2004-09-02 12:20 ` Einar Lueck
2004-09-02 11:24 ` Alan Cox
2004-09-02 12:51 ` Einar Lueck
2004-09-02 20:50 ` David S. Miller
2004-09-02 13:13 ` Bill Rugolsky Jr.
-- strict thread matches above, loose matches on Subject: below --
2004-09-01 12:41 Einar Lueck
2004-09-01 12:25 ` Alan Cox
2004-09-02 16:22 ` Paul Jakma
2004-09-02 16:58 ` Einar Lueck
2004-09-02 20:59 ` Paul Jakma
2004-09-03 8:07 ` Einar Lueck
2004-09-03 16:53 ` Paul Jakma
2004-09-06 7:50 ` Einar Lueck
2004-09-06 7:57 ` Paul Jakma
2004-09-07 15:34 ` Herbert Poetzl
2004-09-05 23:02 ` Daniel Roesen
2004-09-06 3:22 ` David S. Miller
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=200409021401.42255.elueck@de.ibm.com \
--to=elueck@de.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@einar-lueck.de \
/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.