Sorry, replied directly: ---------- Forwarded message ---------- From: The King in Yellow <yellowk...@gmail.com> Date: Tue, Mar 5, 2013 at 12:56 PM Subject: Re: [Openstack] Rebooted, now can't ping my guest To: Sylvain Bauza <sylvain.ba...@digimind.com>
In fact, when I ping 10.5.5.2, tcpdump on the network node actually shows responses... root@os-network:/var/log/quantum# tcpdump -i tap45ffdc5f-da host 10.5.5.5 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on tap45ffdc5f-da, link-type EN10MB (Ethernet), capture size 65535 bytes : 12:50:12.936292 ARP, Request who-has os-network.local tell 10.5.5.5, length 28 12:50:12.936329 ARP, Reply os-network.local is-at fa:16:3e:36:2e:54 (oui Unknown), length 28 12:50:14.936338 ARP, Request who-has os-network.local tell 10.5.5.5, length 28 12:50:14.936378 ARP, Reply os-network.local is-at fa:16:3e:36:2e:54 (oui Unknown), length 28 12:50:15.936299 ARP, Request who-has os-network.local tell 10.5.5.5, length 28 12:50:15.936343 ARP, Reply os-network.local is-at fa:16:3e:36:2e:54 (oui Unknown), length 28 12:50:16.936008 ARP, Request who-has os-network.local tell 10.5.5.5, length 28 12:50:16.936045 ARP, Reply os-network.local is-at fa:16:3e:36:2e:54 (oui Unknown), length 28 above, pinging 10.5.5.1 ; below, pinging 10.5.5.2 12:50:17.044161 IP 10.5.5.5 > os-network.local: ICMP echo request, id 18433, seq 0, length 64 12:50:17.044222 IP os-network.local > 10.5.5.5: ICMP echo reply, id 18433, seq 0, length 64 12:50:18.044399 IP 10.5.5.5 > os-network.local: ICMP echo request, id 18433, seq 1, length 64 12:50:18.044455 IP os-network.local > 10.5.5.5: ICMP echo reply, id 18433, seq 1, length 64 12:50:19.044847 IP 10.5.5.5 > os-network.local: ICMP echo request, id 18433, seq 2, length 64 12:50:19.044899 IP os-network.local > 10.5.5.5: ICMP echo reply, id 18433, seq 2, length 64 12:50:20.045370 IP 10.5.5.5 > os-network.local: ICMP echo request, id 18433, seq 3, length 64 12:50:20.045427 IP os-network.local > 10.5.5.5: ICMP echo reply, id 18433, seq 3 Unfortunately, the CirrOS image 10.5.5.5 is using doesn't seem to have the arp utility, nor does 'ip -n' work. I guess it isn't getting the ARP replies for 10.5.5.1, and somehow got an ARP entry for 10.5.5.2 and isn't seeing the echo replies. Seems to imply some sort of issue from the network node back to him? Found ARP entries via "cat /proc/1/net/arp," which seems to confirm that-- entry for 10.5.5.1 is 00:00:00:00:00:00.
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp