[GH-ISSUE #9854] Defaults system: Add support for multiple VLAN or support for multiple default "presets" #2148

Closed
opened 2026-02-26 12:51:27 +03:00 by kerem · 1 comment
Owner

Originally created by @Gregor-zbjk on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9854

🌟 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). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9854 ### 🌟 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.
kerem 2026-02-26 12:51:27 +03:00
Author
Owner

@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.

<!-- gh-comment-id:3710510543 --> @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 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#2148
No description provided.