no route to host

bislinks's picture
Submitted by bislinks on Tue, 02/14/2012 - 21:42 Pro Licensee

I am behind a router. I am able to access my site from outside.

recently I installed a centos with vgpl on cloudmin. the ip for the main server is ..*.12.

I am getting this error: ping failed, no route to host for the new cloudmin server.

appreciate any help.

Status: 
Closed (fixed)

Comments

bislinks's picture
Submitted by bislinks on Tue, 02/14/2012 - 22:11 Pro Licensee

Status: ping failed Detailed status error ssh: connect to host 192.168.0.151 port 22: No route to host

Submitted by JamieCameron on Wed, 02/15/2012 - 00:22

Could you explain your network setup further? It seems your system has an internal (non-internet) IP address ..

bislinks's picture
Submitted by bislinks on Wed, 02/15/2012 - 08:41 Pro Licensee

i am behind a motorola router DHCP 192.168.0.1.

The ip assigned to the virtualmin box is 192.168.0.12. I have made this ip to be DMZ on the router. I am able to access my.bislinks.com (server box) from outside the router.

the ip assigned to the first cloudmin server (with domain name c54.my.bislinks.com) is 192.168.0.151 (on the same box as 192.168.0.12 where centos with virtualmin pro is running.)

The error is in cloudmin where it says : Detailed status error ssh: connect to host 192.168.0.151 port 22: No route to host

hope that is clear enough.

i have also enabled support login access to the box, in case you need it.

Submitted by JamieCameron on Wed, 02/15/2012 - 15:54

Looking at your system now ..

Can I shut down the c54 VM?

Also, I see that c54.my.bislinks.com resolves to the IP 76.185.103.112 .. is that correct?

bislinks's picture
Submitted by bislinks on Wed, 02/15/2012 - 16:22 Pro Licensee

yes, go ahead and shutdown.

yes, the resolved ip is correct.

bislinks's picture
Submitted by bislinks on Wed, 02/15/2012 - 16:23 Pro Licensee

FYI, *.my.bislinks.com resolves to that same IP.

Submitted by JamieCameron on Wed, 02/15/2012 - 16:31

The issue is that you have the virbr0 interface active for some reason, which is another bridge that breaks Xen networking. I suggest editing /etc/libvirt/qemu/networks/default.xml, commenting out all lines, then rebooting the system.

bislinks's picture
Submitted by bislinks on Wed, 02/15/2012 - 16:44 Pro Licensee

OK. restarting in 30 seconds.

bislinks's picture
Submitted by bislinks on Wed, 02/15/2012 - 17:00 Pro Licensee

This is what I see now:

Last status Virtualmin - Config errors found (Last changed at 2012/02/15 17:20)

Submitted by JamieCameron on Wed, 02/15/2012 - 17:14

That looks pretty good actually.