[pve-devel] [PATCH] add routed network mode
Dietmar Maurer
dietmar at proxmox.com
Tue Aug 27 07:41:38 CEST 2013
> In your setup, you need proxy-arp on host interface because you don't have
> the route on the client or between the client and the target network, so you
> need arpproxy on host to trick.
> But for me, this kind of setup is not real "routing", It's more like a pseudo-
> bridge with arp tricks.
This model is also used by openvz venet, so this is well known, and should work with
migration. I don’t see how live migration works if you hardcode a gateway?
The openvz code does something like this to setup the interface:
---------
my $external_iface = 'vmbr0'; # fixme: autotetect?
# add entry to local ARP cache
my $cmd = "ip neigh add proxy $net->{ip} dev ${external_iface}";
PVE::Tools::run_command($cmd);
# Send ARP request to update neighbour ARP caches
$cmd = "arpsend -c 1 -w 1 -U -i $net->{ip} -e $net->{ip} ${external_iface}";
PVE::Tools::run_command($cmd);
--------
So we only need to set proxyarp on the tap device.
More information about the pve-devel
mailing list