mirror of
https://github.com/PegaProx/project-pegaprox.git
synced 2026-04-25 18:15:50 +03:00
[GH-ISSUE #38] Feature: allow VM NICs to choose SDN networks (VNets) #30
Labels
No labels
Approved
Q2-3 2026 Development
bug
documentation
enhancement
help wanted
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/project-pegaprox-PegaProx#30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @spakka on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/38
Originally assigned to: @MrMasterbay on GitHub.
Currently, the UI that provides the settings for the NIC of a VM, does not show any of the VNets from SDN zones.

It only shows local bridges on the proxmox host, not the cluster-wide SDN VNets.
An example VM in Pegaprox:
Compared to the hardware -> NIC tab within the Proxmox UI:

Can we make the SDN VNets visible, so we can create VMs that are attached to them?
Note that in the above examples, the pictures are showing the same VM.
So in ProxMox, the VM is attached to a VNet. But PegaProx shows it as being on a different bridge. I haven't dared to press 'save', in case it moves it onto the wrong bridge!
Currently using PegaProx Beta 0.6.4.
ProxMox version is pve-manager/9.1.1
@mkellermann97 commented on GitHub (Feb 8, 2026):
Hi @spakka ,
please update PegaProx to the newest version.
Regards,
Marcus
@spakka commented on GitHub (Feb 9, 2026):
This works as expected, thank you for the quick implementation!