[GH-ISSUE #38] Feature: allow VM NICs to choose SDN networks (VNets) #30

Closed
opened 2026-03-02 15:47:21 +03:00 by kerem · 2 comments
Owner

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:
Image

Compared to the hardware -> NIC tab within the Proxmox UI:
Image

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

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: <img width="517" height="556" alt="Image" src="https://github.com/user-attachments/assets/51e6f605-23d7-4baf-8d06-e66983d0d3a7" /> Compared to the hardware -> NIC tab within the Proxmox UI: <img width="342" height="279" alt="Image" src="https://github.com/user-attachments/assets/76fd408f-b5c1-454a-ac17-bcb4cb2d1774" /> 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
kerem 2026-03-02 15:47:21 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@mkellermann97 commented on GitHub (Feb 8, 2026):

Hi @spakka ,

please update PegaProx to the newest version.

Regards,
Marcus

<!-- gh-comment-id:3867640008 --> @mkellermann97 commented on GitHub (Feb 8, 2026): Hi @spakka , please update PegaProx to the newest version. Regards, Marcus
Author
Owner

@spakka commented on GitHub (Feb 9, 2026):

This works as expected, thank you for the quick implementation!

<!-- gh-comment-id:3871690931 --> @spakka commented on GitHub (Feb 9, 2026): This works as expected, thank you for the quick implementation!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/project-pegaprox-PegaProx#30
No description provided.