[Openstack-operators] floatin ip issue
george.shuklin at gmail.com
Sat Oct 25 08:18:05 UTC 2014
Check out if qrouter got floating inside network namespace (ip net exec
qrouter... ip -4 a), or just bash in to it (stdbuf -e0 -o0 ip net exec
qrouter... /bin/bash) and play with it like with normal server.
On 10/24/2014 07:38 PM, Paras pradhan wrote:
> Assigned a floating ip to an instance. But I can't ping the instance.
> This instance can reach internet with no problem. But I can't ssh or
> icmp to this instance. Its not a security group issue.
> On my network node that runs l3, I can see qrouter. The extenel subnet
> looks like this:
> allocation-pool start=192.168.122.193,end=192.168.122.222
> --disable-dhcp --gateway 192.168.122.1 192.168.122.0/24
> I can ping 192.168.122.193 using: ip netns exec
> qrouter-34f3b828-b7b8-4f44-b430-14d9c5bd0d0c ping 192.168.122.193
> but not 192.168.122.194 (which is the floating ip)
> Doing tcp dump on the interace that connects to the external world, I
> can see ICMP request but not reply from the interface :
> 11:36:40.360255 IP 192.168.122.1 > 192.168.122.194
> <http://192.168.122.194>: ICMP echo request, id 2589, seq 312, length 64
> 11:36:41.360222 IP 192.168.122.1 > 192.168.122.194
> <http://192.168.122.194>: ICMP echo request, id 2589, seq 313, length 64
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-operators