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

Support for IP ranges in new defaults system #2141

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

Originally created by @Goslawq on GitHub (Dec 8, 2025).

🌟 Briefly describe the feature

Add support for default IP ranges, similar to the one used before the overhaul

📝 Detailed description

Before the overhaul of the defaults system, it was possible to set IP range as a default for new containers, in the opt/community-scripts/.settings file, for example NET="192.168.0.100/24-192.168.0.255/24".
The script would then ping the range in order until it found a free address and use it for the container.

In the new tiered defaults system such mechanism is gone, allowing only for picking between dhcp and static, which would then have to be manually configured.

💡 Why is this useful?

Automating IP assignment like that allows to have predictable IP, related to the Container ID, with less manual configuration

Originally created by @Goslawq on GitHub (Dec 8, 2025). ### 🌟 Briefly describe the feature Add support for default IP ranges, similar to the one used before the overhaul ### 📝 Detailed description Before the overhaul of the defaults system, it was possible to set IP range as a default for new containers, in the opt/community-scripts/.settings file, for example `NET="192.168.0.100/24-192.168.0.255/24"`. The script would then ping the range in order until it found a free address and use it for the container. In the new tiered defaults system such mechanism is gone, allowing only for picking between dhcp and static, which would then have to be manually configured. ### 💡 Why is this useful? Automating IP assignment like that allows to have predictable IP, related to the Container ID, with less manual configuration
OVERLORD added the enhancement label 2026-02-05 03:56:26 +03:00
OVERLORD commented 2026-02-05 03:56:35 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 16, 2025):

Have fun, ive tested it with advanced settings & default.vars, example:

# Network
var_brg=vmbr0
var_net=192.168.3.10/24-192.168.3.80/24
var_ipv6_method=none
var_gateway=192.168.1.1
Image Image
@MickLesk commented on GitHub (Dec 16, 2025): Have fun, ive tested it with advanced settings & default.vars, example: ``` # Network var_brg=vmbr0 var_net=192.168.3.10/24-192.168.3.80/24 var_ipv6_method=none var_gateway=192.168.1.1 ``` <img width="536" height="179" alt="Image" src="https://github.com/user-attachments/assets/98e985ff-5381-413e-b9a9-20102999964d" /> <img width="550" height="144" alt="Image" src="https://github.com/user-attachments/assets/db1b6915-ca7f-4d89-ba90-668d2b1e028c" />
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#2141
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?