TTL expired in transit to qemu virtual machine.
Hello.
I've setup qemu/kvm and installed several virtual machines. Access and ping to some virtuals are ok, but one have a stable problem not receiving
correctly packets. First, this is the environment:
>uname -a
Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.84-1 x86_64 GNU/Linux
>libvirtd --version
libvirtd (libvirt) 0.9.12.3
>cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
auto eth1
iface eth1 inet manual
auto bond0
iface bond0 inet manual
bond-slaves eth0 eth1
bond-mode balance-alb
bond-miimon 100
bond-downdelay 200
bond-updelay 200
auto br0
iface br0 inet static
address 10.10.10.10
netmask 255.255.0.0
vlan-raw-device bond0
bridge_ports bond0
bridge_stp off
bridge_fd 0
bridge_ageing 0
bridge_maxwait 0
Virtual machines connects to LAN using bridge:
>virt-install .... --network=bridge:br0,model=virtio ....
All virtuals has networking configuret like that. Also in iptables is an entry to allow access to virtuals:
>iptables -L FORWARD -nv
Chain FORWARD (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
X X ACCEPT all -- br0 br0 0.0.0.0/0 0.0.0.0/0
Most virtuals does not have networking problems, but some times they can't be reached. For now only one virtual machines have this problem:
From windows machine ping virtual machine:
>ping 10.10.10.3
Reply from 10.10.10.10: TTL expired in transit.
Reply from 10.10.10.10: TTL expired in transit.
Reply from 10.10.10.10: TTL expired in transit.
Reply from 10.10.10.10: TTL expired in transit.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 10.10.10.10: TTL expired in transit.
Reply from 10.10.10.10: TTL expired in transit.
Reply from 10.10.10.10: TTL expired in transit.
Reply from 10.10.10.10: TTL expired in transit.
>tracert -d 10.10.10.3
Tracing route to 10.10.10.3 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.10.10.10
2 <1 ms <1 ms <1 ms 10.10.10.10
3 <1 ms <1 ms * 10.10.10.10
4 1 ms <1 ms <1 ms 10.10.10.10
5 <1 ms <1 ms * 10.10.10.10
So packet goes round on interfaces of server hosting virtuals.
Virtuals are linux different flavour and one windows. This problem may occur on any of this virtuals.
I've observed that for this particular virtual, which have problem, the arp table of host assigned self mac to the virtual's IP, not the mac
configured for virtual machine.
What could be the problem?
--
Mimiko desu.
Reply to: