starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 17:26:03 +03:00

[GH-ISSUE #12288] opnSense script fails when setting LAN Bridge to a SDN #2561

New issue

Closed

opened 2026-02-26 12:52:50 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 12:52:50 +03:00

Owner

Originally created by @traverseda on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/12288

✅ Have you read and understood the above guidelines?

Yes

🔎 Did you run the script with verbose mode enabled?

Yes, no extra output when running in verbose. Verbose mode not available in advanced mode settings, tried to set
with env vars.

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

opnsense-vm.sh

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

dev_mode="trace" var_verbose="yes" bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/opnsense-vm.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📈 Which Proxmox version are you on?

pve-manager/9.1.1/42db4a6cf33dac83 (running kernel: 6.17.2-1-pve)

📝 Provide a clear and concise description of the issue.

When using SDN, ✗ Bridge 'lan01' does not exist in /etc/network/interfaces. This prevents using opnSense with an SDN as the lan bridge.

🔄 Steps to reproduce the issue.

Set up SDN networking as per the proxmox documentation here: https://pve.proxmox.com/pve-docs/chapter-pvesdn.html

Run the script bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/opnsense-vm.sh)"

Navigate to advanced.

During setup, set your lan bridge to your SDN network name.

❌ Paste the full error output (if available).

Using Default Settings
Using Virtual Machine ID: 100
Using Hostname: opnsense
Allocated Cores: 4
Allocated RAM: 8192
Using LAN Bridge: vmbr0
Using LAN VLAN: Default
Using LAN MAC Address: 02:61:26:BB:53:62
Network Mode: Dual Interface (Firewall)
Using WAN MAC Address: 02:FA:90:52:4A:18
 ✗ Bridge 'vmbr1' does not exist in /etc/network/interfaces

🖼️ Additional context (optional).

No response

Originally created by @traverseda on GitHub (Feb 24, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/12288 ### ✅ Have you read and understood the above guidelines? Yes ### 🔎 Did you run the script with verbose mode enabled? Yes, no extra output when running in verbose. Verbose mode not available in advanced mode settings, tried to set with env vars. ### 📜 What is the name of the script you are using? opnsense-vm.sh ### 📂 What was the exact command used to execute the script? dev_mode="trace" var_verbose="yes" bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/opnsense-vm.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📈 Which Proxmox version are you on? pve-manager/9.1.1/42db4a6cf33dac83 (running kernel: 6.17.2-1-pve) ### 📝 Provide a clear and concise description of the issue. When using SDN, `✗ Bridge 'lan01' does not exist in /etc/network/interfaces`. This prevents using opnSense with an SDN as the lan bridge. ### 🔄 Steps to reproduce the issue. Set up SDN networking as per the proxmox documentation here: https://pve.proxmox.com/pve-docs/chapter-pvesdn.html Run the script `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/opnsense-vm.sh)"` Navigate to advanced. During setup, set your lan bridge to your SDN network name. ### ❌ Paste the full error output (if available). ``` Using Default Settings Using Virtual Machine ID: 100 Using Hostname: opnsense Allocated Cores: 4 Allocated RAM: 8192 Using LAN Bridge: vmbr0 Using LAN VLAN: Default Using LAN MAC Address: 02:61:26:BB:53:62 Network Mode: Dual Interface (Firewall) Using WAN MAC Address: 02:FA:90:52:4A:18 ✗ Bridge 'vmbr1' does not exist in /etc/network/interfaces ``` ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:52:50 +03:00

closed this issue
added the
bug
label

kerem referenced this issue

2026-02-26 13:34:46 +03:00

[PR #2561] [MERGED] New Script: Jupyter Notebook #3824

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/ProxmoxVE#2561

No description provided.

Rows
Columns