Hi,
I believe you are hitting the following issue:
https://github.com/apache/cloudstack/issues/9673. The reason this is happening
is that when multiple physical networks for guest traffic type are created,
they are tagged. So, while listing the offerings they are filtered based on the
tags. In order to get around this, you will have to create network offerings
for shared networks with the tag that you have set on the said physical network.
Regards,
Pearl
________________________________
From: Mercado <cmerc...@g2khosting.com>
Sent: January 16, 2025 1:58 PM
To: users@cloudstack.apache.org <users@cloudstack.apache.org>
Subject: Guest traffic in two interface
Hi everyone.
I have a CloudStack 4.19 cluster using KVM as a hypervisor in a lab
environment. This setup includes a 1 Host, an 1 Storage server, and a
Management server.
The Host has two network interfaces:
1. One interface, "cloudbr0," is used for "public," "guest,"
"management," and "storage" traffic.
2. The other interface connects the Host to the primary storage server.
This network is isolated and does not connect to other networks.
Currently, I need some VMs with "guest" traffic on "cloudbr0" to access
physical servers in the storage network. To achieve this, I configured a
bridge "cloudbr1" on the Host in the interface that connects to the
storage network.
In the CloudStack GUI:
1. I created a "Physical Network 2" with Tag=STO and "Guest" traffic,
using "Traffic Label=cloudbr1."
2. I also created a *network offering* for "Shared" networks associated
with this "Physical Network 2."
The issue arises when I try to create a shared network associated with
"Physical Network 2": the network offering list appears empty.
