Hello Mercado,
The VR under the default NAT configuration will have a Source NAT IP to which your isolated network will get translated to, and external networks will see that IP when any resources in the isolated network attempt to reach. This is the same case with Static NAT. You may solve this like: 1. Establishing connectivity between your Public Network (the one that's on the VR for NAT) and the storage network. If you're using VLANs, this should be termed as inter-VLAN communication. Ensure devices in your storage network have a default route (or static) in the same network to respond to the traffic. Let me know if that works for you. Thanks ---- On Wed, 05 Feb 2025 02:53:05 +0530 cmerc...@g2khosting.com wrote ---- Hi everyone, I'm setting up a CloudStack 4.19.1 environment and ran into an issue I can't seem to solve. * I have an *Isolated* network called *Vms* * I have a *Shared* network called *Storage* * I need the *Vms* network to be able to access the *Storage* network through the Virtual Router. I haven't found a way to make the Virtual Router act as a bridge between *Vms *and *Storage*. I tried adding both network interfaces to a VM, and in that case, the VM could see both networks just fine. Has anyone set up something similar or have any suggestions on how to get the Virtual Router to allow this communication?
