[
https://issues.apache.org/jira/browse/CLOUDSTACK-10075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367225#comment-17367225
]
Daan commented on CLOUDSTACK-10075:
-----------------------------------
This issue is kind of orphaned. It was probably never encountered in the wild
because it works as expected when the rule is for instance only for ICMP and
not for 'all' protocols.
> Egress rules not allowing neighboring IPs when using /32 configuration
> ----------------------------------------------------------------------
>
> Key: CLOUDSTACK-10075
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10075
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Boris Stoyanov
> Priority: Major
>
> Steps:
> 1. deploy 2 vms in network
> For example:
> vm1: 10.1.1.10
> vm2: 10.1.1.20
> Create egress rule allow all for 10.1.1.10/32
> Expected: only VM1 will have access to public
> Actual: VM1 and VM2 have access.
> For more references please look at marvin test:
> component/test_egress_fw_rules.py::test_01_2_egress_fr1()
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
