Public bug reported:
When building a firewall with a rule to block a specific Traffic - the
current traffic is not blocked.
For example:
Running a Ping to an instance and then building a firewall with a rule to block
ICMP to this instance doesn't have affect while the ping command is still
running.
Exiting the command and then trying pinging the Instance again shows the
desired result - i.e. the traffic is blocked.
This is also the case for SSH.
** 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/1386543
Title:
FWaaS - New blocking rules has no affect for existing traffic
Status in OpenStack Neutron (virtual network service):
New
Bug description:
When building a firewall with a rule to block a specific Traffic - the
current traffic is not blocked.
For example:
Running a Ping to an instance and then building a firewall with a rule to
block ICMP to this instance doesn't have affect while the ping command is still
running.
Exiting the command and then trying pinging the Instance again shows the
desired result - i.e. the traffic is blocked.
This is also the case for SSH.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1386543/+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
