Good day.
I have added a VM and bound it to one of our Failover IPs, but cannot ping it's gateway
proxmox host: ks29406.kimsufi.com ( 91.121.103.57 )
VM:
vmid 103
name tools
OS debian 4.3.5-4
IP 94.23.144.59
GW 91.121.103.254
The problem:
------------
Code:
root@tools:~# ping 91.121.103.254
PING 91.121.103.254 (91.121.103.254) 56(84) bytes of data.
From 94.23.144.59 icmp_seq=1 Destination Host Unreachable
From 94.23.144.59 icmp_seq=2 Destination Host Unreachable
From 94.23.144.59 icmp_seq=3 Destination Host Unreachable
root@tools:~# arp -an
? (192.168.0.5) at ea:98:31:a3:7c:db [ether] on eth1
? (91.121.103.254) at on eth0
Interfaces
----------
Code:
root@tools:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr b2:f7:4a:21:14:9e
inet addr:94.23.144.59 Bcast:94.23.144.59 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:27 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1443 (1.4 KiB) TX bytes:252 (252.0 B)
Interrupt:11 Base address:0xe000
eth1 Link encap:Ethernet HWaddr a2:06:b4:18:36:0a
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5490 (5.3 KiB) TX bytes:5304 (5.1 KiB)
Interrupt:10 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:672 (672.0 B) TX bytes:672 (672.0 B)
Routing
-------
Code:
root@tools:~# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
91.121.103.254 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
0.0.0.0 91.121.103.254 0.0.0.0 UG 0 0 0 eth0
I installed tcpdump on tools and ran a few tests. Here are two of them:
- for both of them, I have manually set an arp entry on tools for the gateway with
arp -s 91.121.103.254 00:00:0c:07:ac:01 -i eth0
test 1
---------
ping tools.calm.dhamma-eu.org from abroad (86.134.83.224) and listen on tool's external interface
Code:
root@tools:~# tcpdump -i eth0 -n host 94.23.144.59 or arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
10:26:17.526409 IP 86.134.83.224 > 94.23.144.59: ICMP echo request, id 55057, seq 5888, length 40
10:26:22.913751 IP 86.134.83.224 > 94.23.144.59: ICMP echo request, id 55057, seq 6144, length 40
10:26:28.411550 IP 86.134.83.224 > 94.23.144.59: ICMP echo request, id 55057, seq 6400, length 40
10:26:33.913013 IP 86.134.83.224 > 94.23.144.59: ICMP echo request, id 55057, seq 6656, length 40
So it's receiving ICMP request, but not replying?
test 2
---------
ping 91.121.103.254 (gateway) from tools and listen on the proxmox host's external interface:
Code:
root@ks29406:~# tcpdump -i eth0 -n host 94.23.144.59
tcpdump: WARNING: eth0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
11:30:58.967312 IP 94.23.144.59 > 91.121.103.254: ICMP echo request, id 2507, seq 1, length 64
11:30:59.974623 IP 94.23.144.59 > 91.121.103.254: ICMP echo request, id 2507, seq 2, length 64
11:31:00.982579 IP 94.23.144.59 > 91.121.103.254: ICMP echo request, id 2507, seq 3, length 64
11:31:01.990593 IP 94.23.144.59 > 91.121.103.254: ICMP echo request, id 2507, seq 4, length 64
So ICMP request is being sent to the gateway, but no reply?
Additional testing:
I tried stopping a working vm, and using it's IP on the tools vm - still couldn't ping the gateway
I tried stopping the tools vm, and changing a working vm to use it's IP - couldn't ping the gateway
Then I tried stopping a working VM, and changing the IP of a second working VM to the first VM's IP - couldn't ping the gateway.
This seemed to invalidate the previous two tests.
Is this because of exising arp entries on the gateway's arp table? Will it work if I wait for them to time out?
I would appreciate any help in solving this problem.
With kind regards,
Kevan
