GitHub user bradh352 closed a discussion: private gateway attach to physical 
network issue

I've got these physical networks:

<img width="741" height="293" alt="image" 
src="https://github.com/user-attachments/assets/362e968d-7332-4a09-80d9-502f9cad0edd";
 />

And I want to add a private gateway to access the mgmt network to allow access 
to few ports (ceph via the mgmt/hypervisor network in this case):
<img width="1071" height="621" alt="image" 
src="https://github.com/user-attachments/assets/ab343355-79cd-41d8-bdf9-92a6ec695bc0";
 />

Before I attempt to add a private gateway, I check my network bridges:
```
ceph            8000.de95ff0e22c3       no              vxlan200
hypervisor              8000.0625c5991a54       no              vxlan100
public          8000.d286dc39fb05       no              vnet1
                                                        vxlan2
```

I can see `vnet1` for my VPC public ips attached to `public` which is right.  
But otherwise no vnets are attached to those bridges which is right as well.

So I create a private gateway in my VPC like this:

<img width="506" height="773" alt="image" 
src="https://github.com/user-attachments/assets/b9cb1851-db24-43e0-88f7-7f9f0b9aa611";
 />

It creates fine, but when I look at bridge config, it attached to the wrong 
network!

```
ceph            8000.de95ff0e22c3       no              vxlan200
hypervisor              8000.0625c5991a54       no              vxlan100
public          8000.d286dc39fb05       no              vnet1
                                                        vnet11
                                                        vxlan2
```

I would have expected vnet11 to attach to `hypervisor` but instead it attached 
to `public`.  Am I doing something wrong here?  Or misunderstanding something?  
Or is this a bug?

I'm running 4.21.0

GitHub link: https://github.com/apache/cloudstack/discussions/11795

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to