From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Luis R. Rodriguez" Subject: Re: [RFC v2 2/4] net: enables interface option to skip IP Date: Thu, 20 Feb 2014 12:39:29 -0800 Message-ID: References: <1392433180-16052-1-git-send-email-mcgrof@do-not-panic.com> <1392433180-16052-3-git-send-email-mcgrof@do-not-panic.com> <1392668638.21106.5.camel@dcbw.local> <1392828325.21976.6.camel@dcbw.local> <53050244.1020106@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WGaPQ-0006v6-0S for xen-devel@lists.xenproject.org; Thu, 20 Feb 2014 20:39:52 +0000 Received: by mail-lb0-f174.google.com with SMTP id l4so1725091lbv.33 for ; Thu, 20 Feb 2014 12:39:49 -0800 (PST) In-Reply-To: <53050244.1020106@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Zoltan Kiss Cc: kvm@vger.kernel.org, Patrick McHardy , Dan Williams , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , James Morris , Hideaki YOSHIFUJI , Alexey Kuznetsov , xen-devel@lists.xenproject.org, "David S. Miller" List-Id: xen-devel@lists.xenproject.org On Wed, Feb 19, 2014 at 11:13 AM, Zoltan Kiss wrote: > On 19/02/14 17:20, Luis R. Rodriguez wrote: >>>> On 19/02/14 17:20, Luis R. Rodriguez also wrote: >>>> Zoltan has noted though some use cases of IPv4 or IPv6 addresses on >>>> backends though <...> >> >> As discussed in the other threads though there *is* some use cases >> of assigning IPv4 or IPv6 addresses to the backend interfaces though: >> routing them (although its unclear to me if iptables can be used >> instead, Zoltan?). > > Not with OVS, it steals the packet before netfilter hooks. Got it, thanks! Can't the route be added using a front-end IP address instead on the host though ? I just tried that on a Xen system and it seems to work. Perhaps I'm not understand the exact topology on the routing case. So in my case I have the backend without any IPv4 or IPv6 interfaces, the guest has IPv4, IPv6 addresses and even a TUN for VPN and I can create routes on the host to the front end by not using the backend device name but instead using the front-end target IP. Luis