[
https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866715#comment-13866715
]
Wei Zhou commented on CLOUDSTACK-5144:
--------------------------------------
BF-cloudbr0 should be like this.
Chain BF-cloudbr0 (2 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere state
RELATED,ESTABLISHED
BF-cloudbr0-IN all -- anywhere anywhere PHYSDEV match
--physdev-is-in --physdev-is-bridged
BF-cloudbr0-OUT all -- anywhere anywhere PHYSDEV
match --physdev-is-out --physdev-is-bridged
ACCEPT all -- anywhere anywhere PHYSDEV match
--physdev-out em1 --physdev-is-bridged
Are you sure the bridge cloudbr0 exists?
if the bridge does not exist, there is no rule in this chain.This is similar to
your result of iptables command.
> [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when
> there is no ingress rule defined for the security group
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5144
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5144
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Affects Versions: 4.3.0
> Reporter: Gaurav Aradhye
> Assignee: Wei Zhou
> Priority: Blocker
> Labels: automation
> Fix For: 4.3.0
>
> Attachments: MS-Log.txt, agent.log, agent.log, ipset-L output.txt,
> iptables-rules.txt, management-server.log
>
>
> In Basic Zone Setup:
> 1. Create an account
> 2. Deploy a VM in that account
> 3. Verify that any ingress rule is not defined for the security group
> belonging to the account
> 4. Try SSH to VM using the nic ipaddress from external client
> SSH is successful to the VM where as it should fail when the ingress rule is
> not defined.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
