Strange, I’ve setup dozens of virtualization clusters, and never used anything other than bridged networking. I haven’t really met anyone using routed or NAT mode, but I guess there’s a first time for everything.
You might be able to get the NAT mode to work for you, to pass traffic between the networks, you probably only need to enable IP forwarding on the KVM host, and make sure the FORWARD chain in iptables accepts the packets. Russ > On Mar 23, 2016, at 12:10 AM, Joshua J. Kugler <[email protected]> wrote: > > On Tuesday, March 22, 2016 23:47:05 Russell Purinton wrote: >> The routing table looks normal. That 3rd statement that Pawan mentioned is >> just a normal default gateway. Nothing wrong there. >> >> I suspect the issue is at the virtual network layer… <forward >> mode='route’/> seems suspect. >> >> http://serverfault.com/questions/270931/routing-networking-on-kvm >> <http://serverfault.com/questions/270931/routing-networking-on-kvm> >> >> I think you’d want to setup Bridge mode interfaces. > > Yeah, I think it is something in the network layer. However, it worked fine > when the KVM config was using NAT. A bridged interface requires linking up > with > a physical interface on the host machine, and I can't do that on the machine > I'm on at the moment. > > Really not sure what's going on here. I wish there was a way for two 'nat' > type virbr networks to talk to each other, I wouldn't need the 'route' type. > > j > > -- > Joshua J. Kugler - Fairbanks, Alaska > Azariah Enterprises - Programming and Website Design > [email protected] - Jabber: [email protected] > PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A
_______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
