Hi, Based on your diagram, I think Virtual Router should work for you.
You need to set the correct kvm traffic labels in Zone ->Physical network -> click "Update traffic labels" on top-right. - Public (cloudbr0) - Guest (cloudbr1 or cloudbr0) The traffic flow looks like VM -> VR (guest gateway) -> VR (public IP) -> Storage so you need to make sure VR public IPs and Storage IPs (on shared network) are reachable. -Wei On Wed, Feb 5, 2025 at 7:40 PM Mercado <cmerc...@g2khosting.com> wrote: > The connection I'm trying to establish is between two networks that are > not on the same interface. Each host has two network interfaces—one for > general traffic and the other exclusively for internal traffic with the > *Storage servers*. > > I don’t want to expose my network connection to the main network. > Instead, I want to use a *Virtual Router (VR)* that is connected to both > networks. I understand that for Internet access, a connection to the > main network would also be required. > > My physical networks are: > > * *Physical Network 1 (CLOUDBR0):* Main network > * *Physical Network 2 (CLOUDBR1):* Storage servers network with the > *STO* tag > > I'm using the following network offerings: > > * *DefaultSharedNetworkOffering* with the *STO* tag > * *DefaultNetworkOfferingforKubernetesService* (no tag) > > Graph of the expected network: > https://drive.google.com/file/d/1q-p33zsBS8dGrWFl4SH5Vk3trAc3rTdh/view > > Thanks for your reply. > > --- > > El 4/2/25 a las 21:57, Jayanth Reddy escribió: > > 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 +0530cmerc...@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? > > > >
