Date: Mon, 6 Sep 2004 08:57:42 +0100 (IST)
From: Paul Jakma <paul@clubi.ie>
To: lkml@einar-lueck.de
cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/ipv4 for Source VIPA support, kernel BK Head
In-Reply-To: <413C16CE.30607@de.ibm.com>
Message-ID: <Pine.LNX.4.61.0409060854100.23011@fogarty.jakma.org>
References: <200409011441.10154.elueck@de.ibm.com> <200409021858.38338.elueck@de.ibm.com>
 <Pine.LNX.4.61.0409022147220.23011@fogarty.jakma.org> <200409031007.29467.elueck@de.ibm.com>
 <Pine.LNX.4.61.0409031747580.23011@fogarty.jakma.org> <413C16CE.30607@de.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1203
Lines: 35

On Mon, 6 Sep 2004, Einar Lueck wrote:

> 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).

then change the 'connected' routes. that's all you need to affect 
source address selection. All your other dynamic routes will still 
work.

> Zebra and OSPFD do not support this type of route.

ospfd never would. You could add the required support to zebra if you 
wished. ;)

> As a consequence, this approach does not work for us. Anyway, 
> iptables is the way to do it.

One way, but quite a kludge to effectively NAT local machines. You'd 
be much better up configuring the routes which affect source address 
selection to taste.

anyway..

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
All of the animals except man know that the principal business of life is
to enjoy it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/