Yea... sorry about the diagram. Only has def gateway of 192.168.122.1, which knows how to get to 10.0.0.0 .
Tried the direct routeanyway, but did not help. "route add 10.0.0.0 gw 192.168.122.1" I can do a dig from the physical server OS to the 192.168.122.10 vm, , which is going through the bridge. This works perfect. On Wed, 2008-09-17 at 11:17 -0400, Graeme Fowler wrote: > On Wed, 2008-09-17 at 11:05 -0400, Josh Mullis wrote: > > This is a very basic setup. > > ...ok... > > > Thought maybe this award -winning diagram would help clear up any > > confusion. > > Post-modern, more like. The formatting went pop in transit :) > > Simple question: does the realserver (the VM, 192.168.122.10) have a > route direct back to the 10.0.0.0/whatever network? > > More specific routes will override the default, so having a direct > route > means the traffic will not necessarily traverse the director and will > therefore not be un-NATted on the way back. > > Is there some sort of virtual ethernet bridge affecting it with both > network segments on the same "virtual cable"? > > Graeme > > > _______________________________________________ > LinuxVirtualServer.org mailing list - [email protected] > Send requests to [EMAIL PROTECTED] > or go to http://lists.graemef.net/mailman/listinfo/lvs-users > > _______________________________________________ LinuxVirtualServer.org mailing list - [email protected] Send requests to [EMAIL PROTECTED] or go to http://lists.graemef.net/mailman/listinfo/lvs-users
