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 11 Packages Projects Releases 10 Wiki Activity

OpenWRT exit code #1480

New Issue
Closed
opened 2026-02-05 01:00:05 +03:00 by OVERLORD · 8 comments
OVERLORD commented 2026-02-05 01:00:05 +03:00
Owner
Copy Link

Originally created by @pete1019 on GitHub (Aug 18, 2025).

✅ Have you read and understood the above guidelines?

yes

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

OpenWRT

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/openwrt.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.

Proxmox 8.4.5
https://community-scripts.github.io/ProxmoxVE/scripts?id=openwrt

Prints this Error:

  • Starting OpenWrt VM...no physical interface on bridge 'vmbr1'
    kvm: -netdev type=tap,id=net0,ifname=tap133i0,script=/usr/libexec/qemu-server/pve-bridge,downscript=/usr/libexec/qemu-server/pve-bridgedown,vhost=on: network script /usr/libexec/qemu-server/pve-bridge failed with status 6400
    start failed: QEMU exited with code 1

[ERROR] in line 597: exit code 255: while executing command qm start $VMID

🔄 Steps to reproduce the issue.

IP 192.168.14.1
Netmask: 255.255.255.0

❌ Paste the full error output (if available).

  • Starting OpenWrt VM...no physical interface on bridge 'vmbr1'
    kvm: -netdev type=tap,id=net0,ifname=tap133i0,script=/usr/libexec/qemu-server/pve-bridge,downscript=/usr/libexec/qemu-server/pve-bridgedown,vhost=on: network script /usr/libexec/qemu-server/pve-bridge failed with status 6400
    start failed: QEMU exited with code 1

[ERROR] in line 597: exit code 255: while executing command qm start $VMID

🖼️ Additional context (optional).

No response

Originally created by @pete1019 on GitHub (Aug 18, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? OpenWRT ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/openwrt.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. Proxmox 8.4.5 https://community-scripts.github.io/ProxmoxVE/scripts?id=openwrt Prints this Error: - Starting OpenWrt VM...no physical interface on bridge 'vmbr1' kvm: -netdev type=tap,id=net0,ifname=tap133i0,script=/usr/libexec/qemu-server/pve-bridge,downscript=/usr/libexec/qemu-server/pve-bridgedown,vhost=on: network script /usr/libexec/qemu-server/pve-bridge failed with status 6400 start failed: QEMU exited with code 1 [ERROR] in line 597: exit code 255: while executing command qm start $VMID ### 🔄 Steps to reproduce the issue. IP 192.168.14.1 Netmask: 255.255.255.0 ### ❌ Paste the full error output (if available). - Starting OpenWrt VM...no physical interface on bridge 'vmbr1' kvm: -netdev type=tap,id=net0,ifname=tap133i0,script=/usr/libexec/qemu-server/pve-bridge,downscript=/usr/libexec/qemu-server/pve-bridgedown,vhost=on: network script /usr/libexec/qemu-server/pve-bridge failed with status 6400 start failed: QEMU exited with code 1 [ERROR] in line 597: exit code 255: while executing command qm start $VMID ### 🖼️ Additional context (optional). _No response_
OVERLORD added the not a script issue label 2026-02-05 01:00:05 +03:00
OVERLORD commented 2026-02-05 01:00:14 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 18, 2025):

your vmbr1 is down or defect

https://forum.proxmox.com/threads/migration-error-pve-bridge-failed-with-status-6400.88703/

@MickLesk commented on GitHub (Aug 18, 2025): your vmbr1 is down or defect https://forum.proxmox.com/threads/migration-error-pve-bridge-failed-with-status-6400.88703/
OVERLORD commented 2026-02-05 01:00:17 +03:00
Author
Owner
Copy Link

@pete1019 commented on GitHub (Aug 18, 2025):

your vmbr1 is down or defect

https://forum.proxmox.com/threads/migration-error-pve-bridge-failed-with-status-6400.88703/

Thanks for the fast reply. Does it have something todo with the scripting choosing LAN Vlan 999 as default VLAN? I deleted that.

Linux Bridge on Proxmox is just fine.
Tying now with VLAN-Aware to on.

@pete1019 commented on GitHub (Aug 18, 2025): > your vmbr1 is down or defect > > https://forum.proxmox.com/threads/migration-error-pve-bridge-failed-with-status-6400.88703/ Thanks for the fast reply. Does it have something todo with the scripting choosing LAN Vlan 999 as default VLAN? I deleted that. Linux Bridge on Proxmox is just fine. Tying now with VLAN-Aware to on.
OVERLORD commented 2026-02-05 01:00:19 +03:00
Author
Owner
Copy Link

@pete1019 commented on GitHub (Aug 18, 2025):

Maybe found the problem in the script.
This Command is being typed to fast!
so only "elete ..." ist left as command.

Image
@pete1019 commented on GitHub (Aug 18, 2025): Maybe found the problem in the script. This Command is being typed to fast! so only "elete ..." ist left as command. <img width="1105" height="404" alt="Image" src="https://github.com/user-attachments/assets/ef5133cc-558d-4e5f-91b7-3fa4d947d8b8" />
OVERLORD commented 2026-02-05 01:00:26 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 18, 2025):

Does it work in default mode?

@MickLesk commented on GitHub (Aug 18, 2025): Does it work in default mode?
OVERLORD commented 2026-02-05 01:00:30 +03:00
Author
Owner
Copy Link

@pete1019 commented on GitHub (Aug 18, 2025):

"VLAN-Aware" in Proxmox made the VM start now.
I think its important to give that as a note.
Need to check everything now.

@pete1019 commented on GitHub (Aug 18, 2025): "VLAN-Aware" in Proxmox made the VM start now. I think its important to give that as a note. Need to check everything now.
OVERLORD commented 2026-02-05 01:00:35 +03:00
Author
Owner
Copy Link

@pete1019 commented on GitHub (Aug 18, 2025):

Looks fine now with "VLAN-Aware" checked on Linux-Bridge for LAN in Proxmox.

And why does the LAN default to VLAN 999 in the script?

@pete1019 commented on GitHub (Aug 18, 2025): Looks fine now with "VLAN-Aware" checked on Linux-Bridge for LAN in Proxmox. And why does the LAN default to VLAN 999 in the script?
OVERLORD commented 2026-02-05 01:00:40 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 18, 2025):

It’s not really a bug, but more of a design choice in the script. By default it assigns VLAN 999 to the LAN interface to avoid mixing it with the WAN network. In Proxmox, if you use a VLAN tag, the bridge must be set to “VLAN Aware” – otherwise the VM won’t start.

So technically the script works as intended, but the default VLAN can cause confusion. A safer approach would be to leave VLAN empty by default and only set it when the user actually wants to use VLANs.

@MickLesk commented on GitHub (Aug 18, 2025): It’s not really a bug, but more of a design choice in the script. By default it assigns VLAN 999 to the LAN interface to avoid mixing it with the WAN network. In Proxmox, if you use a VLAN tag, the bridge must be set to “VLAN Aware” – otherwise the VM won’t start. So technically the script works as intended, but the default VLAN can cause confusion. A safer approach would be to leave VLAN empty by default and only set it when the user actually wants to use VLANs.
OVERLORD commented 2026-02-05 01:00:41 +03:00
Author
Owner
Copy Link

@pete1019 commented on GitHub (Aug 18, 2025):

Info: i deleted the VLAN 999 on the LAN-Interface. It still would not start the VM.

So some notes on the website would be nice to check the "vlan-aware" before installing.

@pete1019 commented on GitHub (Aug 18, 2025): Info: i deleted the VLAN 999 on the LAN-Interface. It still would not start the VM. So some notes on the website would be nice to check the "vlan-aware" before installing.
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 not a script issue
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#1480
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?