apache / apache/cloudstack

CS4.22.0 vROUTER ACLs Feature is non RFC compliant applied to Internal Interface

Open
#13,266 10 comments 0 reactions 1 assignee Claimed by @weizhouapache View on GitHub
component:networking component:virtual-router type:enhancement
Dominant language
Java
Stars
3.1k
Forks
1.4k
Avg merge
6d 19h
Merged PRs (30d)
32

Description

### problem

CS 4.22.0
Host Ubuntu 22.4 KVM
vRouter on VPC ACLs

This VPC ACL feature is beyond good, it's awesome. However @weizhouapache with all the love I have for the team. That's not right, ACL should be applied to the edge - and we know that should not be to interpretation, and many think are just Cisco best practices - we should have a feature to select WAN-side, LAN-side or named Edge-side, Internal-Side which seems are more contemporary names.

- RFC 2827
- RFC 3704

Suggestion: if decided to make it RF-ish. To make easy the transition for existing systems, the updated feature will apply to LAN-side (internal-side) by default.

### versions

CS 4.22.0
Host Ubuntu 22.4 KVM
running vRouter with 8CPUs and 8GRAM, oversubscription is 1:1 for all systems.

### The steps to reproduce the bug

1. Create a VPC
2. Add the custom ACL with ingress only
3. the ACL does not filter the traffic, as is applied to the vRouter LAN AKA Internal interface.

### What to do about it?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.