public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Einar Lueck <elueck@de.ibm.com>
To: Paul Jakma <paul@clubi.ie>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/ipv4 for Source VIPA support, kernel BK Head
Date: Mon, 06 Sep 2004 09:50:38 +0200	[thread overview]
Message-ID: <413C16CE.30607@de.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0409031747580.23011@fogarty.jakma.org>

Paul Jakma wrote:

> You could try:
>
> ip route change default via <gateway> src <vipa>
>
> Presuming the NFS clients are behind a gateway. If also onlink, you 
> need to modify the connected routes and change the src there too.
>
We have tried it this way, of course, and it works. But the 
corresponding routes are static. In our context, all routes have to be 
dynamic (for fault tolerance and due to configuration overhead). Zebra 
and OSPFD do not support this type of route. As a consequence, this 
approach does not work for us. Anyway, iptables is the way to do it.

Regards,

Einar.


  reply	other threads:[~2004-09-06  7:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-01 12:41 [PATCH] net/ipv4 for Source VIPA support, kernel BK Head 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2004-09-02 12:01 Einar Lueck
2004-09-02 11:05 ` 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.

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=413C16CE.30607@de.ibm.com \
    --to=elueck@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@einar-lueck.de \
    --cc=paul@clubi.ie \
    /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