Public bug reported:
Instances appear to be pingable for a short time after a floating ip is
associated even though there is no ingress icmp security group rule.
tcpdump of the instance's tap device shows that the instance isn't
actually responding to the ping. It appears that the router gateway
interface is responding to the ping for a short time. You can reproduce
this by booting an instance using a security group with only egress
rules. Allocate a floating ip address. ping the ip address ( nothing
will happen yet ). Associate the ip with the instance. The ping will
begin responding.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1260530
Title:
Instances appear pingable without an ingress icmp security rule
Status in OpenStack Neutron (virtual network service):
New
Bug description:
Instances appear to be pingable for a short time after a floating ip
is associated even though there is no ingress icmp security group
rule. tcpdump of the instance's tap device shows that the instance
isn't actually responding to the ping. It appears that the router
gateway interface is responding to the ping for a short time. You can
reproduce this by booting an instance using a security group with only
egress rules. Allocate a floating ip address. ping the ip address (
nothing will happen yet ). Associate the ip with the instance. The
ping will begin responding.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1260530/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
