Skip to content

When ACL is applied to a subnet, affects ACL rules based on security groups, such as pg group? #245

@BigCousin-z

Description

@BigCousin-z

ovn acl :
logical_switch :
_uuid : 12b25a3d-b32c-4f37-a89d-7c1b7cf81772
action : allow-related
direction : to-lport
external_ids : {acl_group=ACL-1}
label : 0
log : false
match : "ip4.src == 0.0.0.0/0 && tcp && 8080 <= tcp.dst <= 8080"
meter : []
name : ACL-1-in-3
options : {}
priority : 1497
severity : []

port group:
_uuid : 5a98ec19-a151-4f20-a12d-26fbd4bf5014
action : drop
direction : from-lport
external_ids : {}
label : 0
log : false
match : "ip && inport == @ovn_pg_1"
meter : []
name : []
options : {}
priority : 2000
severity : []

If the lsp interface of the VM exists in both logical switch and port group, the ACLs can only take effect at one level logcal switch or pg.
Is it correct that this kind of security policy affects each other when the actual effective scope is inconsistent? Or how can I configure it so that the two types of ACLs do not affect each other

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions