Rich,
On 2011-09-24 03:49, Philip Rhoades wrote: > Rich, > > > On 2011-09-24 03:42, Richard W.M. Jones wrote: >> Another thought I had: is the *guest* running libvirtd? >> >> There used to be a bug that we started libvirtd in the guest, which >> created its own 192.168.122/24 network, which royally messed up >> routing to that guest. > > > libvirtd not running on guest - but http://libvirt.org/firewall.html > looks promising so I will work my way through that. I finally found that stopping the firewall on the client changed the error message on the host from: "No route to host" to: "Connection refused" then I realised I hadn't restarted sshd on the client but the original problem was the firewall on the client so I have set that up properly now and it is likely that the rules at: http://libvirt.org/firewall.html are not necessary for a default F16 setup. BTW, you were right about restarting iptables upsetting libvirtd/dnsmasq . . Regards, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: [email protected] _______________________________________________ virt mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/virt
