CS4.22.0 VRouter 3 Major Issues: freezes on routed environment & ACLS not filtering Incoming traffic, and Throughput not performing

[tatay188]

problem

Using CS 4.22.0 Routed or Private using any command with the " | more " freezes the Virtual router, stoping all traffic.
our VPC Vrouter has 8 cores and 8GiB RAM, and is not performing the throughput.

ETH1 is facing outside traffic WAN
ETH2 is facing Internal traffic LAN
ACLS are applied to the ETH2, not to the ETH1
How this should work:

• ACLS should be able to select which interface to apply, or
• should be by default the WAN interface always.

versions

CS 4.22.0
KVM
Private and VPC
vRouter Issues.
Dedicated CPUS and Memory

The steps to reproduce the bug

1**. ISSUE 1:**
2. create a private network or a VPC with vrouter with 4 or more cores and 4GiB or more (did not try with 2 cores)
3. Using the UI create a custom ACL
4. the ACL Applies to the Internal interface ETH2 instead to the WAN -
5. ISSUE 2:
6. login via console to the vrouter, use any command with the pipe symbol and the command more " | more "
7. vRouter freezes and all traffic stops...
8. ISSUE 3:
9. vRouter does not perform as expected, traffic throughput does not reach at least 5Gbps with 8cores and 8GiB RAM, And we have the parameters changed to support up to 10Gbps instead of the default 200Mbps, unless there is some other magic parameter.

What to do about it?

No response

[weizhouapache]

@tatay188

The network ACLs are applied to guest VM traffic. For each VPC tier, the associated ACL list can be different, so the rules are expected to be applied on the guest interfaces (eth2, eth3, etc.) inside the VPC VR.

This is different from the firewall feature, which applies to public IP traffic on the WAN side.

[weizhouapache]

@tatay188

both nft list ruleset | more and nft list ruleset | less worked in my testing environment

[weizhouapache]

@tatay188

Could you check the <interface> section in the xml definition of VPC VR and guest VMs too ?