>>I posted my code to make it clear what I talk about.
So, for your setup, why not simply do a standard bridge setup + proxyarp ?
host config:
-----------
auto vmbr0
iface eth0 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports eth0
bridge_stp off
bridge_fd 0
guest config: (tap is on vmbr0)
---------------------------------
iface eth0 inet static
address 192.168.1.3
netmask 255.255.255.0
gateway 192.168.1.1
echo 1 > /proc/sys/net/ipv4/conf/tap/proxy_arp
echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
provider
router(192.168.1.1)----------eth0---proxmoxhost(192.168.1.2)-vmbr0----------tap
192.168.1.3
----- Mail original -----
De: "Dietmar Maurer" <[email protected]>
À: "Alexandre DERUMIER" <[email protected]>
Cc: [email protected]
Envoyé: Mardi 27 Août 2013 08:53:41
Objet: RE: [PATCH] add routed network mode
> Oh, ok, I understand. So proxmox is not routing packets.
> For me, this is not "routed" mode.
>
> what you do is something like bridging, but spoof guest mac address with
> host mac address.
Proxmox is routing, from tap to eth0 in above example.
And this is by sure not bridging - you will see the difference when you
implement a iptable firewall ;-)
> If a routed setup, the provider give you a subnet range, routed to the
> proxmox main ip.
> and guests use proxmox ips as gateway.
>
>
> So maybe are we talking about 2 differents this ?
I posted my code to make it clear what I talk about.
> (I need to check the forum, I had helped one use some time ago with routed
> network on hetzner, with differents sub-ranges)
>
_______________________________________________
pve-devel mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
