Support Destination CIDR

[btzq]

ISSUE TYPE

• Improvement Request

COMPONENT NAME

Improvement Request (UI, Functionality)

CLOUDSTACK VERSION

4.19

CONFIGURATION

N/A

OS / ENVIRONMENT

N/A

SUMMARY

Note: This ticket is broken down as requested from the origianl post, #8841

Support Destination CIDR

• Reduces number of ACL Rules required
• Adds more security
• Makes ACL rule function more complete

STEPS TO REPRODUCE

N/A

N/A

EXPECTED RESULTS

To be able to manage ACL Rules more easily for large scale projects

ACTUAL RESULTS

Challenging to use ACL rules for large scale projects.

[DaanHoogland]

not sure if this would be UI only or even API would be enough. sounds complicated.

[DaanHoogland]

This is a bit complicated but a valid request.
For this we need to add changes through the whole system: in the

• VR scripts
• backend command(s)
• DB
• virtual appliance managers
• service
• API
• and finally in the UI
  It is not a very complicated addition but requires quite some knowledge af the system.

and extra consideration is that the destination ip (as soon as the packet has entered the VR) is no longer the public ip, so destination can become a bit ambiguous. I suggest we limit this functionality to only apply to the private addresses of the VMs.

[btzq]

Yes maybe we can limit it to Private Adresses for the time being and see how it goes. This is also to limit the blast radius of bugs due to the big change.