[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15500899#comment-15500899
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9480:
--------------------------------------------

Github user jburwell commented on the issue:

    https://github.com/apache/cloudstack/pull/1666
  
    @murali-reddy have you had a chance to investigate the Jenkins failure(s) 
and the test failures identified by @karuturi?  
    
    Does this PR address 
[CLOUDSTACK-9480](https://issues.apache.org/jira/browse/CLOUDSTACK-9480)?  If 
so, please amend the commit message to reflect this association?  Otherwise, 
which JIRA ticket should be associated with this issue?
    
    In terms of release target, this issue seems to affect 4.8 as well?  How 
much effort would it be to re-target it to 4.8 for pending 4.8.2.0 release?


> Egress Firewall: Incorrect use of Allow/Deny for ICMP
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-9480
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9480
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Network Controller
>    Affects Versions: 4.6.2, 4.7.1, 4.8.0, 4.9.0
>            Reporter: Murali Reddy
>            Assignee: Murali Reddy
>            Priority: Critical
>             Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0
>
>
> When 'default egress policy' is set to 'allow' in the network offering, any 
> egress rule that is added will 'deny' the traffic overriding the default 
> behaviour. 
> Conversely, when 'default egress policy' is set to 'deny' in the network 
> offering, any egress rule that is added will 'allow' the traffic overriding 
> the default behaviour. 
> While this works for 'tcp', 'udp' as expected, for 'icmp' protocol its always 
> set to ALLOW.
> Egress firewall rule behaviour should be consistent for all the protocols.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to