starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-16 05:34:07 +03:00
Code Issues 23 Packages Projects Releases 44 Wiki Activity

Defaults system: Add support for multiple VLAN or support for multiple default "presets" #2147

New Issue
Closed
opened 2026-02-05 03:57:08 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 03:57:08 +03:00
Owner
Copy Link

Originally created by @Gregor-zbjk on GitHub (Dec 10, 2025).

🌟 Briefly describe the feature

Add the ability to define multiple VLANs in a defaults file, or alternatively, allow multiple default presets that can be selected during installation.

📝 Detailed description

It would be helpful to have the option to specify several VLANs directly in the defaults file and choose one of them from a menu during the installer script.

Example:
var_vlan: 99, 10, 20

These VLANs should appear as selectable options during the installation process.

Alternative approach:
Instead of (or in addition to) multiple VLAN entries, offering multiple global default presets would be very useful. For example, one preset for internal applications, another for gaming servers, and so on. Users could then simply select the desired preset either in the installer or via a menu, without needing to go through advanced configuration each time.

💡 Why is this useful?

This feature would streamline the installation workflow and eliminate the need to manually configure VLAN tags repeatedly. For users like me where VLAN 99 is the primary network but VLAN 10 is required for internal applications, the current defaults system cannot be used effectively. Adding support for multiple VLANs or selectable presets would significantly improve flexibility and overall ease of use.

Originally created by @Gregor-zbjk on GitHub (Dec 10, 2025). ### 🌟 Briefly describe the feature Add the ability to define multiple VLANs in a defaults file, or alternatively, allow multiple default presets that can be selected during installation. ### 📝 Detailed description It would be helpful to have the option to specify several VLANs directly in the defaults file and choose one of them from a menu during the installer script. Example: `var_vlan: 99, 10, 20` These VLANs should appear as selectable options during the installation process. Alternative approach: Instead of (or in addition to) multiple VLAN entries, offering multiple global default presets would be very useful. For example, one preset for internal applications, another for gaming servers, and so on. Users could then simply select the desired preset either in the installer or via a menu, without needing to go through advanced configuration each time. ### 💡 Why is this useful? This feature would streamline the installation workflow and eliminate the need to manually configure VLAN tags repeatedly. For users like me where VLAN 99 is the primary network but VLAN 10 is required for internal applications, the current defaults system cannot be used effectively. Adding support for multiple VLANs or selectable presets would significantly improve flexibility and overall ease of use.
OVERLORD added the enhancement label 2026-02-05 03:57:08 +03:00
OVERLORD commented 2026-02-05 03:57:13 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 5, 2026):

This would add significant complexity for a very specific edge case. The current system already provides flexibility:

Existing solutions:

1.) Use Advanced Settings during installation to change VLAN (one extra step)
2.) Pass environment variable: var_vlan=10 bash -c "$(curl ...)"
3.) Create app-specific defaults files if needed

Multiple presets per app would be difficult to maintain and too subjective. The defaults system is designed for sensible general defaults, not user-specific network configurations.

@MickLesk commented on GitHub (Jan 5, 2026): This would add significant complexity for a very specific edge case. The current system already provides flexibility: **Existing solutions:** 1.) Use Advanced Settings during installation to change VLAN (one extra step) 2.) Pass environment variable: var_vlan=10 bash -c "$(curl ...)" 3.) Create app-specific defaults files if needed Multiple presets per app would be difficult to maintain and too subjective. The defaults system is designed for sensible general defaults, not user-specific network configurations.
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 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#2147
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?