Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have Server at, with a /29 subnet for running KVM-VMs. The VMs get network access via a bridge interface. I'm currently using two IPs from the subnet. The VM-host is running Ubuntu 12.04 kernel 3.2.0, as is one of the VMs, the other VM is running CentOS 5.8 kernel 2.6.18.

/etc/network/interfaces on the server:

    auto lo
    iface lo inet loopback

    auto  eth0
    iface eth0 inet manual

    auto  br0
    iface br0 inet static
            address   A.A.A.102
            broadcast A.A.A.127
            gateway   A.A.A.97
            bridge_ports eth0
            bridge_stp on
            bridge_maxwait 10
            bridge_fd 15

    # routes for B.B.B.200/29 subnet vms
            up ip route add B.B.B.200 dev br0 scope link
            up ip route add B.B.B.201 dev br0 scope link

    # default route to access subnet provided by hetzner
    up route add -net A.A.A.96 netmask gw A.A.A.97 eth0

/etc/network/interfaces on the Ubuntu VM:

    auto lo
    iface lo inet loopback

    auto eth0
    iface eth0 inet static
            address B.B.B.201

            up ip route add A.A.A.102 dev eth0 src B.B.B.201
            up ip route add default via A.A.A.102 src B.B.B.201

/etc/sysconfig/network-scripts/ifcfg-eth0 on the CentOS VM:


Since I'm no Redhat pro, I didn't know how to set the routes via the Redhat configuration tools, so I did with /etc/rc.local:

    ip route add A.A.A.102 dev eth0 src B.B.B.202
    ip route add default via A.A.A.102 src B.B.B.202

Not the most elegant way, but it works.

This setup was working flawlessly up until a few days ago, when I couldn't access the Ubuntu VM via the internet anymore. ping, ssh, http etc gave timeouts, so I accessed the VM via virt-viewer and tried to ping

    $ ping
    PING ( 56(84) bytes of data.
    64 bytes from ( icmp_req=1 ttl=57 time=7.62 ms
    From VMHOST.FQDN (A.A.A.102): icmp_seq=2 Redirect Host(New nexthop: (A.A.A.97))
    From B.B.B.201 icmp_seq=3 Destination Host Unreachable

A second attempt to ping always answered "Destination Host Unreachable"

I did not change any machine's setup, except for security updates on the Ubuntu machines, CentOS is still working, Ubuntu isn't anymore. Rolling back the update did not help.

Does anyone have a clue what's wrong? Any help appreciated.

Thanks, Marcus

share|improve this question
Hetzner's network is extremely bizarre. Contact them first. – Michael Hampton May 24 '13 at 15:36
Done already. They said, it's my fault. But as I said: the setup worked flawlessly for months. – marcus May 25 '13 at 18:26

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.