On 20/02/14 20:39, Luis R. Rodriguez wrote:
On Wed, Feb 19, 2014 at 11:13 AM, Zoltan Kiss <zoltan.kiss@xxxxxxxxxx> 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.
Check this how current Xen scripts does routed networking:
http://wiki.xen.org/wiki/Xen_Networking#Associating_routes_with_virtual_devices
Note, there are no bridges involved here! As the above page says, the
backend has to have IP address, maybe it's not true anymore. I'm not too
familiar with this setup too, I've used it only once.
Zoli
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
