FWaaS - New blocking rules has no affect for existing traffic

Bug #1386543 reported by Itzik Brown
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
New
Undecided
Unassigned

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.

Tags: fwaas
Revision history for this message
Sumit Naiksatam (snaiksat) wrote :

This is related to the use of the underlying iptables library. A similar bug has been filed for SG:
https://bugs.launchpad.net/neutron/+bug/1335375

A common solution will work in both cases.

Changed in neutron:
status: New → Triaged
assignee: nobody → badveli_vishnuus (badveli-vishnuus)
Changed in neutron:
importance: Undecided → High
Revision history for this message
badveli_vishnuus (badveli-vishnuus) wrote :

Since a similar fix was done for security groups separately need to add code for firewall.
Thanks
Vishnu

tags: added: fwaas
Revision history for this message
fangzhen (zhen-fang) wrote :

Hi,
Vishnu, are you still working on this? If no, I'd like to help.

Changed in neutron:
assignee: badveli_vishnuus (badveli-vishnuus) → nobody
status: Triaged → New
status: New → Incomplete
importance: High → Undecided
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Itzik Brown (itzikb1) wrote :

Why is it marked as incomplete?

Itzik Brown (itzikb1)
Changed in neutron:
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.