-
-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network subject selectors @internal and @external does not work in ACLs #1423
Comments
I reproduced the issue here. The OVN state looks correct so it's a bit puzzling as to why the traffic gets rejected. Especially as an |
Right, so yeah, all the ACL logic appears correct as far as the filter being pushed into OVN. The problem appears to be that port selectors generally don't work in an ingress rule but work fine in an egress rule... This feels like an OVN bug so I'll need to do some work to redo my package building logic so I can reliably spit out the latest stable packages for OVS and OVN in Ubuntu and Debian. Then I'll need to reproduce this on the latest OVN and reach out to upstream so see what's going on. I'm saying this feels like an OVN bug because running this exact flow through
|
Moving to 6.9 as it will take more time to get to the bottom of this with the OVN folks. If this is intentional, then we'll need to put some checks or at least documentation in place to explain this behavior. |
Required information
Issue description
I had assumed that @internal would match sources and destinations within the Incus network, while @external would match sources and destinations outside the Incus network. However, my experiments are yielding unexpected results both on Incus v6.0.2 and v6.7.
I’m testing this on a three-member Incus cluster with an OVN-type network:
There are three container instances foo, bar and baz:
Instances can reach internet and each other when no ACLs are involved:
When I add an ACL that should permit all egress traffic and only allow ingress traffic from internal addresses, I unexpectedly find that traffic between instances is blocked:
Interestingly, if I replace ‘@internal’ with the explicit subnet ‘10.47.57.0/24’, internal traffic is restored:
Out of curiosity, I’ve also experimented with using selectors in egress rules. In some cases, the behavior matches my expectations:
Some times not:
Steps to reproduce
The text was updated successfully, but these errors were encountered: