no route to host on certain ports, kvm bridged guest

el_tedward · 05-13-2012, 12:40 AM

I have a bridged KVM guest where only certain ports seem to route to it properly. For instance, I can ssh in over port 22 and ping it just fine (from the host as well as on a separate box on my network). However, if I change SSH to run on port 9822, I get a no route to host error, though port 22 gives the expected connection refused error.

KVM guest is at 192.168.0.50, running centos 6.2

KVM host (is also gateway for my network) is at 192.168.0.1, running scientific linux 6.2

other physical box is at 192.168.0.10, running ubuntu 12.04

Here are the relevant network scripts for the KVM host:

cat /etc/sysconfig/network-scripts/ifcfg-br0

Code:

[sudo] password for tedward: 
DEVICE=br0
BOOTPROTO="static"
ONBOOT=yes
TYPE=Bridge
BROADCAST="192.168.0.255"
IPADDR="192.168.0.1"
NETMASK="255.255.255.0"

cat /etc/sysconfig/network-scripts/ifcfg-eth0

Code:

DEVICE="eth0"
HWADDR="00:50:43:00:87:53"
NM_CONTROLLED="no"
ONBOOT="yes"
#BOOTPROTO="static"
BRIDGE=br0
BROADCAST="192.168.0.255"
IPADDR="192.168.0.1"
NETMASK="255.255.255.0"
PROMISC="yes"

frankbell · 05-13-2012, 07:18 PM

Is SE/Linux enabled and what are its settings?

el_tedward · 05-13-2012, 11:42 PM

I've had the default targeted policies in enforce mode. Switching to permissive on both host and guest gets me the same results, though.

el_tedward · 05-19-2012, 09:06 PM

Any ideas?

okcomputer44 · 05-21-2012, 01:11 AM

Hi,

Iptables/firewall rules?

I think just only the 22(ssh) enabled in your box and when you change it to 9822 then you lose the packet at the INPUT chain.
Try to stop iptables/firewall first to see what happens.