On Mon, 10 Sep 2012, Steve Thompson wrote:
On Mon, 10 Sep 2012, Dale Dellutri wrote:
This looks like it should work for Client A, but maybe not for Client B (see below). So maybe it's a firewall problem (iptables chain FORWARD) on the host?
Client B's default route is 192.168.4.1. This address is not on the host. Did you mean to use .2? If not, is .1 aware of the routing to the 192.168.0.0/22 network?
Actually I have two similar setups, one with .1 and one with .2, so I mixed up the examples here. But in reality it is setup up correctly. And it doesn't work for either client :-(
Let me expand on this. There is no issue with a client on net1 communicating with a client on net2; the host passes packets from one subnet to the other as it should. The only issue is when the client is a virtual machine on the host.
Steve