it.
>
>Carl
>
>On Mon, Oct 27, 2014 at 9:50 AM, Itzik Brown wrote:
>>
>> - Original Message -
>>> From: "Carl Baldwin"
>>> To: "OpenStack Development Mailing List (not for usage questions)"
>>>
>>> Sent: Mond
"Carl Baldwin"
>> To: "OpenStack Development Mailing List (not for usage questions)"
>>
>> Sent: Monday, October 27, 2014 5:27:57 PM
>> Subject: Re: [openstack-dev] [Neutron] FWaaS/Security groups Not blocking
>> ongoing traffic
>>
- Original Message -
> From: "Carl Baldwin"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Monday, October 27, 2014 5:27:57 PM
> Subject: Re: [openstack-dev] [Neutron] FWaaS/Security groups Not blocking
> ongoing
On Mon, Oct 27, 2014 at 6:34 AM, Simon Pasquier wrote:
> Hello Itzik,
> This has been discussed lately on this ML. Please see
> https://bugs.launchpad.net/neutron/+bug/1335375.
This is a good example that any create, update, or delete of a SG rule
can expose this issue. This bug only mentions de
Hello Itzik,
This has been discussed lately on this ML. Please see
https://bugs.launchpad.net/neutron/+bug/1335375.
BR,
Simon
On Mon, Oct 27, 2014 at 1:17 PM, Itzik Brown wrote:
>
> Hi,
>
> When building a firewall with a rule to block a specific Traffic - the
> current traffic is not blocked.
>
Hi,
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 t
