Repository navigation
Define the proper functionality for source nat in shared networks #10846
Description
The required feature described as a wish
As an implementer I would like to be clear on what the functionality of shared networks is completely and without ambiguity.
as shown in testing for #10612, shared networks are now allowed to support the functionality “Source NAT” , but as the VMs in a shared network have their own public IP, this does not make much sense. It would make sense if some plugin would provide “Firewall”, or “Packet Shaper”/“QoS" for the network however.
Investigation is needed (probably followed by design/implementation) to see what should be possible and how to deal with it in API and UI.
Activity
github-actions commentedon Dec 20, 2025
This issue is stale because it has been open for 120 days with no activity. It may be removed by administrators of this project at any time. Remove the stale label or comment to request for removal of it to prevent this.
DaanHoogland commentedon Dec 20, 2025
@weizhouapache , any thoughts on this?
weizhouapache commentedon Dec 22, 2025
I have no idea which network plugin supports Source NAT on shared network.
we know VR can not be used as Source NAT if network type is Shared. if it is disallowed, it is ok to me.
DaanHoogland commentedon Dec 23, 2025
This is in the end a UI issue and an API issue that need separate implementations, is it?