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:20:46 +0200 [thread overview]
Message-ID: <200409021420.46785.elueck@de.ibm.com> (raw)
In-Reply-To: <1094123102.4996.10.camel@localhost.localdomain>
On Donnerstag, 2. September 2004 13:05 Alan Cox wrote:
> On Iau, 2004-09-02 at 13:01, Einar Lueck wrote:
> > The high-availability requirements drive those customers to ensure that
> > all routes are dynamic which is not possible with the proposed ip route
> > approach.
>
> Why. You are simply doing NAT for that port from all locally sourced
> packets to your "virtual" address ?
I thought You proposed to utilize ip route in the following way:
"ip route xxx.xxx.xxx.xxx/xx via xxx dev xxx src MY_VIRTUAL_IP_ADDRESS"
This approach does not work with the setups we have in mind. So I misunderstood
You. As we pointed out in the other part of the mail iptables NAT is not an option
for the relevant customers.
Einar
next prev parent reply other threads:[~2004-09-02 12:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 12:01 Einar Lueck
2004-09-02 11:05 ` Alan Cox
2004-09-02 12:20 ` Einar Lueck [this message]
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=200409021420.46785.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome