[SOLVED] OVS-IntPort equivalent for VXLan

Jul 11, 2025
10
2
3
Hey,

I use VXLan to span my VM-Networks over three PVE-Nodes.
That VXLan contains multiple VNETs (trusted, untrusted, management, ...)

I now would like to assign IPs of the management VXLan-VNET to the actual PVE Hosts (so I can connect to their Web-UI via these IPs).

On a OpenVSwitch&VLAN-Setup I would use an OVS-IntPort, but that does not seem to work for VXLAN-Based SDNs.

On the Per-Host Network-Page in the PVE-UI, I don't see the "virtual interfaces" that the VXLan-SDN created, so I can't put in an IP there.

How would a proper setup look here?
Do I need to create a bridge-Interface and then add the corresponding tap/tep/"management" VXLan-Interface as member to it? Would that work?

Or is there another way to achieve this?
 
Hey,

So I tried creating a Linux Bridge in the UI.

Looking at /etc/nework/interfaces.d/sdn I can see that there is an interface called „vxlan_mgmt“ and a bridge called „mgmt“, including the „vxlan_mgmt“ interface.

But when creating the bridge in the UI, I can neither use „mgmt“ nor „vxlan_mgmt“ as „Bridge Ports“. The error being „unable to find bridge port“.

I guess I could just add an ip to the „mgmt“ bridge created by /etc/network/interfaces.d/sdn
But I dont want to edit that file by hand, as I would be afraid for the SDN to overwrite it the next time I hit „Apply“.

Can I define the „mgmt“ interface/bridge twice in /etc/network/interfaces.d?
Once by „sdn“ and once in a file created by me, where I only define an IP on it?
Would the host then merge the two interface definitions, or would one overwrite the other?
Or would the networking service outright refuse configuring the interface at all?



EDIT: Yes, one can just re-define the IP for that bridge in a different file and the networking service is smart enough to combine them.
 
Last edited: