starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 15 Packages Projects Releases 10 Wiki Activity

Can't select SDN in network section #929

New Issue
Closed
opened 2026-02-04 22:15:10 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-04 22:15:10 +03:00
Owner
Copy Link

Originally created by @alanoitaliano on GitHub (May 9, 2025).

Originally assigned to: @michelroegl-brunner on GitHub.

✅ Have you read and understood the above guidelines?

Yes

📜 What is the name of the script you are using?

Debian LXC, Ubuntu LXC

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/debian.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Hi,

I'm running Proxmox in cloud. using SDN to create a virtual network behind vmbr0.
It seems the install script changed, and now it shows a list of network bridges, where before we could enter the name manually.
This makes it impossible to select SDN bridge, as it's not even in Network bridges on Proxmox.

Image

Image

Image

🔄 Steps to reproduce the issue.

Create an SDN network
Start install script (I guess any, but I tried Debian and Ubuntu)
Choose Advanced Settings
When on network bridge select, only Proxmox bridge appears

❌ Paste the full error output (if available).

No error

🖼️ Additional context (optional).

Maybe allow manual input of network device when in advanced settings, just like it was before?

Originally created by @alanoitaliano on GitHub (May 9, 2025). Originally assigned to: @michelroegl-brunner on GitHub. ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? Debian LXC, Ubuntu LXC ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/debian.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Hi, I'm running Proxmox in cloud. using SDN to create a virtual network behind vmbr0. It seems the install script changed, and now it shows a list of network bridges, where before we could enter the name manually. This makes it impossible to select SDN bridge, as it's not even in Network bridges on Proxmox. ![Image](https://github.com/user-attachments/assets/6131d5eb-bfd6-481e-97e2-19e0c480a22c) ![Image](https://github.com/user-attachments/assets/28a9d0c6-8d95-47e6-a165-3b2b7dde4e11) ![Image](https://github.com/user-attachments/assets/34f12a85-804c-4076-b2e0-8d624683e16f) ### 🔄 Steps to reproduce the issue. Create an SDN network Start install script (I guess any, but I tried Debian and Ubuntu) Choose Advanced Settings When on network bridge select, only Proxmox bridge appears ### ❌ Paste the full error output (if available). No error ### 🖼️ Additional context (optional). Maybe allow manual input of network device when in advanced settings, just like it was before?
OVERLORD added the bugenhancement labels 2026-02-04 22:15:10 +03:00
OVERLORD commented 2026-02-04 22:15:16 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (May 9, 2025):

Ah ok.
I did not think of that SDN feature and that it is in needed here as i dont use SDN.

You mind elaborating a bit what you entered there and how you use it with our scripts? Then i can have a look and implement the grepping for the menu correctly.
Probably tommorow, latest Monday!

@michelroegl-brunner commented on GitHub (May 9, 2025): Ah ok. I did not think of that SDN feature and that it is in needed here as i dont use SDN. You mind elaborating a bit what you entered there and how you use it with our scripts? Then i can have a look and implement the grepping for the menu correctly. Probably tommorow, latest Monday!
OVERLORD commented 2026-02-04 22:15:21 +03:00
Author
Owner
Copy Link

@alanoitaliano commented on GitHub (May 9, 2025):

Ah ok. I did not think of that SDN feature and that it is in needed here as i dont use SDN.

You mind elaborating a bit what you entered there and how you use it with our scripts? Then i can have a look and implement the grepping for the menu correctly. Probably tommorow, latest Monday!

Hi Michel,

With Proxmox hosted in cloud, most of the times one MAC can transfer per IP, otherwise the server gets blocked (For example Hetzner Dedis).
To bypass that, you can run OPNSense (on second bought IP) with let's say vmbr1 acting as LAN for containers and VMs, Just similar to a home router setup.
Proxmox has something similar, a software defined network, which creates a virtual zone where Proxmox is basically the gateway for all stuff, so containers/vms have LAN IPs and route thru Proxmox (https://pve.proxmox.com/pve-docs/chapter-pvesdn.html).
So with my setup, for all containers and VMs I select vnet0 instead of vmbr0 to get internet access into LXC/VMs that I want.

@alanoitaliano commented on GitHub (May 9, 2025): > Ah ok. I did not think of that SDN feature and that it is in needed here as i dont use SDN. > > You mind elaborating a bit what you entered there and how you use it with our scripts? Then i can have a look and implement the grepping for the menu correctly. Probably tommorow, latest Monday! Hi Michel, With Proxmox hosted in cloud, most of the times one MAC can transfer per IP, otherwise the server gets blocked (For example Hetzner Dedis). To bypass that, you can run OPNSense (on second bought IP) with let's say vmbr1 acting as LAN for containers and VMs, Just similar to a home router setup. Proxmox has something similar, a software defined network, which creates a virtual zone where Proxmox is basically the gateway for all stuff, so containers/vms have LAN IPs and route thru Proxmox (https://pve.proxmox.com/pve-docs/chapter-pvesdn.html). So with my setup, for all containers and VMs I select vnet0 instead of vmbr0 to get internet access into LXC/VMs that I want.
OVERLORD commented 2026-02-04 22:15:28 +03:00
Author
Owner
Copy Link

@alanoitaliano commented on GitHub (May 9, 2025):

Posting also cat of interfaces file and sdn file:

root@px:/etc/network/interfaces.d# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface enp7s0 inet manual

auto enp7s0.4000
iface enp7s0.4000 inet static
        address 192.168.100.1/24
        mtu 1400

auto vmbr0
iface vmbr0 inet static
        address XX
        gateway XX
        bridge-ports enp7s0
        bridge-stp off
        bridge-fd 0

iface vmbr0 inet6 static
        address YY
        gateway YY

source /etc/network/interfaces.d/*
root@px:/etc/network/interfaces.d# cat /etc/network/interfaces.d/sdn
#version:2

auto vnet0
iface vnet0
        address 10.0.0.1/24
        post-up iptables -t nat -A POSTROUTING -s '10.0.0.0/24' -o vmbr0 -j SNAT --to-source XX
        post-down iptables -t nat -D POSTROUTING -s '10.0.0.0/24' -o vmbr0 -j SNAT --to-source XX
        post-up iptables -t raw -I PREROUTING -i fwbr+ -j CT --zone 1
        post-down iptables -t raw -D PREROUTING -i fwbr+ -j CT --zone 1
        bridge_ports none
        bridge_stp off
        bridge_fd 0
        ip-forward on
@alanoitaliano commented on GitHub (May 9, 2025): Posting also cat of interfaces file and sdn file: ``` root@px:/etc/network/interfaces.d# cat /etc/network/interfaces # network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the network configuration manually, # please utilize the 'source' or 'source-directory' directives to do # so. # PVE will preserve these directives, but will NOT read its network # configuration from sourced files, so do not attempt to move any of # the PVE managed interfaces into external files! auto lo iface lo inet loopback iface enp7s0 inet manual auto enp7s0.4000 iface enp7s0.4000 inet static address 192.168.100.1/24 mtu 1400 auto vmbr0 iface vmbr0 inet static address XX gateway XX bridge-ports enp7s0 bridge-stp off bridge-fd 0 iface vmbr0 inet6 static address YY gateway YY source /etc/network/interfaces.d/* root@px:/etc/network/interfaces.d# cat /etc/network/interfaces.d/sdn #version:2 auto vnet0 iface vnet0 address 10.0.0.1/24 post-up iptables -t nat -A POSTROUTING -s '10.0.0.0/24' -o vmbr0 -j SNAT --to-source XX post-down iptables -t nat -D POSTROUTING -s '10.0.0.0/24' -o vmbr0 -j SNAT --to-source XX post-up iptables -t raw -I PREROUTING -i fwbr+ -j CT --zone 1 post-down iptables -t raw -D PREROUTING -i fwbr+ -j CT --zone 1 bridge_ports none bridge_stp off bridge_fd 0 ip-forward on ```
OVERLORD commented 2026-02-04 22:15:32 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (May 9, 2025):

Ah ok. I did not think of that SDN feature and that it is in needed here as i dont use SDN.

You mind elaborating a bit what you entered there and how you use it with our scripts? Then i can have a look and implement the grepping for the menu correctly. Probably tommorow, latest Monday!

Hi Michel,

With Proxmox hosted in cloud, most of the times one MAC can transfer per IP, otherwise the server gets blocked (For example Hetzner Dedis).
To bypass that, you can run OPNSense (on second bought IP) with let's say vmbr1 acting as LAN for containers and VMs, Just similar to a home router setup.
Proxmox has something similar, a software defined network, which creates a virtual zone where Proxmox is basically the gateway for all stuff, so containers/vms have LAN IPs and route thru Proxmox (https://pve.proxmox.com/pve-docs/chapter-pvesdn.html).
So with my setup, for all containers and VMs I select vnet0 instead of vmbr0 to get internet access into LXC/VMs that I want.

Thank you for your response!
There seems to be a PR up wich should fix your issue. But i will dig into the SDN and if/how we can incorporated it in our scripts.

@michelroegl-brunner commented on GitHub (May 9, 2025): > > Ah ok. I did not think of that SDN feature and that it is in needed here as i dont use SDN. > > > > You mind elaborating a bit what you entered there and how you use it with our scripts? Then i can have a look and implement the grepping for the menu correctly. Probably tommorow, latest Monday! > > Hi Michel, > > With Proxmox hosted in cloud, most of the times one MAC can transfer per IP, otherwise the server gets blocked (For example Hetzner Dedis). > To bypass that, you can run OPNSense (on second bought IP) with let's say vmbr1 acting as LAN for containers and VMs, Just similar to a home router setup. > Proxmox has something similar, a software defined network, which creates a virtual zone where Proxmox is basically the gateway for all stuff, so containers/vms have LAN IPs and route thru Proxmox (https://pve.proxmox.com/pve-docs/chapter-pvesdn.html). > So with my setup, for all containers and VMs I select vnet0 instead of vmbr0 to get internet access into LXC/VMs that I want. Thank you for your response! There seems to be a PR up wich should fix your issue. But i will dig into the SDN and if/how we can incorporated it in our scripts.
OVERLORD commented 2026-02-04 22:15:35 +03:00
Author
Owner
Copy Link

@Kastello1 commented on GitHub (May 11, 2025):

Ah ok. I did not think of that SDN feature and that it is in needed here as i dont use SDN.
You mind elaborating a bit what you entered there and how you use it with our scripts? Then i can have a look and implement the grepping for the menu correctly. Probably tommorow, latest Monday!

Hi Michel,
With Proxmox hosted in cloud, most of the times one MAC can transfer per IP, otherwise the server gets blocked (For example Hetzner Dedis).
To bypass that, you can run OPNSense (on second bought IP) with let's say vmbr1 acting as LAN for containers and VMs, Just similar to a home router setup.
Proxmox has something similar, a software defined network, which creates a virtual zone where Proxmox is basically the gateway for all stuff, so containers/vms have LAN IPs and route thru Proxmox (https://pve.proxmox.com/pve-docs/chapter-pvesdn.html).
So with my setup, for all containers and VMs I select vnet0 instead of vmbr0 to get internet access into LXC/VMs that I want.

Thank you for your response! There seems to be a PR up wich should fix your issue. But i will dig into the SDN and if/how we can incorporated it in our scripts.

Hey, I'm new here and hope its okay to comment here.
Even with the new code change it seems to detect only bridges within the /etc/network/interfaces while SDN's create them in /etc/network/interfaces.d/sdn so the script still wont find them.

That's why it's needed to include the line "source /etc/network/interfaces.d/*" within the /etc/network/interfaces file.

The updated PR just looks for all bridges regardless of their name, but only in "/etc/network/interfaces" it doesn't include Vlans / SDN's as they are in a seperated file.

@Kastello1 commented on GitHub (May 11, 2025): > > > Ah ok. I did not think of that SDN feature and that it is in needed here as i dont use SDN. > > > You mind elaborating a bit what you entered there and how you use it with our scripts? Then i can have a look and implement the grepping for the menu correctly. Probably tommorow, latest Monday! > > > > > > Hi Michel, > > With Proxmox hosted in cloud, most of the times one MAC can transfer per IP, otherwise the server gets blocked (For example Hetzner Dedis). > > To bypass that, you can run OPNSense (on second bought IP) with let's say vmbr1 acting as LAN for containers and VMs, Just similar to a home router setup. > > Proxmox has something similar, a software defined network, which creates a virtual zone where Proxmox is basically the gateway for all stuff, so containers/vms have LAN IPs and route thru Proxmox (https://pve.proxmox.com/pve-docs/chapter-pvesdn.html). > > So with my setup, for all containers and VMs I select vnet0 instead of vmbr0 to get internet access into LXC/VMs that I want. > > Thank you for your response! There seems to be a PR up wich should fix your issue. But i will dig into the SDN and if/how we can incorporated it in our scripts. Hey, I'm new here and hope its okay to comment here. Even with the new code change it seems to detect only bridges within the /etc/network/interfaces while SDN's create them in /etc/network/interfaces.d/sdn so the script still wont find them. That's why it's needed to include the line "source /etc/network/interfaces.d/*" within the /etc/network/interfaces file. The updated PR just looks for all bridges regardless of their name, but only in "/etc/network/interfaces" it doesn't include Vlans / SDN's as they are in a seperated file.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#929
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?