>>You setup a route for the second network? Why don’t you simply use the same
>>network for testing?
Well, this is to simulate like if I was behind an external router. (like if you
are hosted on provider like ovh)
A route should be setup somewhere to say how to reach the network behind
proxmox host.
This kind of config (replace private by public adress to simulate internet
network)
[client 10.0.1.1]---->[10.0.1.1---hardware router----10.0.0.1]---->[10.0.0.2
proxmox host]---------->192.168.0.1 guest
---------->192.168.0.2 guest
hardware router : route add 192.168.0.0/24 gw 10.0.0.2
default gw: upstream internet bgp router
when your are hosted, you have a small public range (192.168.0.0./29), and this
range is setup with a route in hosting provider hardware router
to go through proxmox ip.
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.
----- Mail original -----
De: "Dietmar Maurer" <[email protected]>
À: "Alexandre DERUMIER" <[email protected]>
Cc: [email protected]
Envoyé: Lundi 26 Août 2013 18:41:09
Objet: RE: [PATCH] add routed network mode
> But in any case, the packet can reach the proxmox host, so it's something in
> proxmox host routing.
>
> (In any case, client only have proxmox host mac-ip in his arp table and
> proxmox host have tap mac-ip in his arp table too)
You setup a route for the second network? Why don’t you simply use the same
network for testing?
_______________________________________________
pve-devel mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
