Skip to content

private gateway attach to wrong physical network #11798

Description

@weizhouapache

Discussed in #11795

Originally posted by bradh352 October 6, 2025
I've got these physical networks:

image

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):
image

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:

image

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions