Re: TTL expired in transit to qemu virtual machine.
On 18.03.2017 07:22, Igor Cicimov wrote:
>uname -a
Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.84-1 x86_64 GNU/Linux
That's an really old kernel, I don't start anything virtual these days without at least 3.13.x kernel.
I regularly do apt-get upgrade, but not to next Debian version. So, how this kernel be old for Debian 7?
Hmmm, this doesn't make much sense to me, more specifically this part:
vlan-raw-device bond0
bridge_ports bond0
Whats the purpose exactly of the vlan? Usually, and that is how I do it, you would split the VLAN's coming from the switch trunk port over the bond
and attach them to separate bridges lets say:
Don't mind that line. I putted it as a reminder to continue extend networking in using vlans. For now there is no vlan used.
That's strange indeed, except if br0 is used by something else like libvrit network that sets up the interface for proxy-arp. What's the output of:
# brctl showmacs br0
port no mac addr is local? ageing timer
1 bridge mac yes 0.00
8 fe:54:00:13:76:5b yes 0.00
5 fe:54:00:44:ac:39 yes 0.00
6 fe:54:00:a8:35:fb yes 0.00
2 fe:54:00:c2:64:2d yes 0.00
4 fe:54:00:d5:17:fb yes 0.00
3 fe:54:00:de:83:2d yes 0.00
# ip route show
10.0.0.0/8 via 10.10.10.254 dev br0
10.10.0.0/16 dev br0 proto kernel scope link src 10.10.10.10
# arp -n
gives a long list for local and virtual ip/mac
on the host, and:
# ip link show
I can't connect using ssh, only vnc.
This shows lo and eth0 with corresponding mac and is UP
# ip route show
10.10.0.0/16 dev eth0 proto kernel scope link src 10.10.10.3
169.254.0.0/16 dev eth0 scope link metric 1002
default via 10.10.10.254 dev eth0
# arp -n
gives a long list for local and virtual ip/mac
on the problematic vm and on one of the good vm's?
Thouse 3 commands shows the same (except ip and mac) on both vm's.
To find the loop I would start by doing ping between good and bad vm (both directions in turns) and check the traffic on the host interface:
# tcpdump -ennqt -i br0 \( arp or icmp \)
and corresponding network devices on both vm's too.
This gives me lot of output regarding arp and icmp on LAN.
Any sysctl settings you might have changed on the host?
net.ipv4.ip_forward=1
net.ipv4.conf.all.arp_ignore=1
net.ipv4.conf.all.arp_announce=2
--
Mimiko desu.
Reply to: