SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-28 16:52:43 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Address management for IPv6 #585

New Issue
Closed
opened 2025-11-20 04:50:38 -05:00 by saavagebueno · 6 comments
saavagebueno commented 2025-11-20 04:50:38 -05:00
Owner
Copy Link

Originally created by @Tinsus on GitHub (Feb 22, 2025).

Originally assigned to: @michelroegl-brunner on GitHub.

🌟 Briefly describe the feature

Option for Address Management with IPv6

📝 Detailed description

in advanced settings I get ask for a lot of details for the IPv4 connection. there I can choose the type for the address management and its defaulted with dhcp. I dont get the very same option for IPv6 address management so the PXE default setting is untouched with "static".
I also want the option to change it for IPv6 - in a best case scenario that setting is defaulted with SLAAC (also for basic setups).

💡 Why is this useful?

I request this feature because I get some strange output when running e.g. the pihole instal script:

✔️ Set up Container OS
✔️ Network Connected: xxx.xxx.178.100 xxxx::xxxx:xxxx:feae:8c22 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:feae:8c22
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected

that is because I need to change it to SLAAC for a working IPv6 connection.
To get the script to check the IPv6 connection successfully I need to be faster, changing that setting in the UI after the container gets created by the script, than the script is to do this very check.

Originally created by @Tinsus on GitHub (Feb 22, 2025). Originally assigned to: @michelroegl-brunner on GitHub. ### 🌟 Briefly describe the feature Option for Address Management with IPv6 ### 📝 Detailed description in advanced settings I get ask for a lot of details for the IPv4 connection. there I can choose the type for the address management and its defaulted with dhcp. I dont get the very same option for IPv6 address management so the PXE default setting is untouched with "static". I also want the option to change it for IPv6 - in a best case scenario that setting is defaulted with SLAAC (also for basic setups). ### 💡 Why is this useful? I request this feature because I get some strange output when running e.g. the pihole instal script: ✔️ Set up Container OS ✔️ Network Connected: xxx.xxx.178.100 xxxx::xxxx:xxxx:feae:8c22 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:feae:8c22 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected that is because I need to change it to SLAAC for a working IPv6 connection. To get the script to check the IPv6 connection successfully I need to be faster, changing that setting in the UI after the container gets created by the script, than the script is to do this very check.
saavagebueno added the enhancement label 2025-11-20 04:50:38 -05:00
saavagebueno commented 2025-11-20 04:50:39 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Mar 11, 2025):

With https://github.com/community-scripts/ProxmoxVED/pull/34 I added IPV6 to our dev repo. Can you head over there and try with a script if it works? I dont use IPV6.

@michelroegl-brunner commented on GitHub (Mar 11, 2025): With https://github.com/community-scripts/ProxmoxVED/pull/34 I added IPV6 to our dev repo. Can you head over [there](https://github.com/community-scripts/ProxmoxVED) and try with a script if it works? I dont use IPV6.
saavagebueno commented 2025-11-20 04:50:39 -05:00
Author
Owner
Copy Link

@Tinsus commented on GitHub (Mar 12, 2025):

Sorry, maybe I didn't understand what to do.
For testing I just used
https://raw.githubusercontent.com/community-scripts/ProxmoxVED/refs/heads/main/ct/debian.sh
and on default mode I git the usual message - the setting on network was untouched.
and on advanced mode I didn't realise any new option.

can you pls give me an instruction how to test this?

@Tinsus commented on GitHub (Mar 12, 2025): Sorry, maybe I didn't understand what to do. For testing I just used https://raw.githubusercontent.com/community-scripts/ProxmoxVED/refs/heads/main/ct/debian.sh and on default mode I git the usual message - the setting on network was untouched. and on advanced mode I didn't realise any new option. can you pls give me an instruction how to test this?
saavagebueno commented 2025-11-20 04:50:40 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 12, 2025):

Its removed currently due massive Issues at building

@MickLesk commented on GitHub (Mar 12, 2025): Its removed currently due massive Issues at building
saavagebueno commented 2025-11-20 04:50:40 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 24, 2025):

@Tinsus, sorry for the delay, ive checked the function and reworked it.
Its only on dev-System, so can you take a look & maybe give feedback?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/ct/debian.sh)"
  1. Default Settings -> auto enabled slaac
  2. Advanced Settings -> choose between static, dhcp, auto (slaac) and none
Image Image Image

Generally speaking, should slaac / auto really be active in every default setting? Or would you prefer “none” with optional variable transfer?

@MickLesk commented on GitHub (Jun 24, 2025): @Tinsus, sorry for the delay, ive checked the function and reworked it. Its only on dev-System, so can you take a look & maybe give feedback? ```bash bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/ct/debian.sh)" ``` 1. Default Settings -> auto enabled slaac 2. Advanced Settings -> choose between static, dhcp, auto (slaac) and none <img width="446" alt="Image" src="https://github.com/user-attachments/assets/68d61b98-6403-4972-b638-94b2cdf8c35f" /> <img width="436" alt="Image" src="https://github.com/user-attachments/assets/7bfc83e1-ace4-4cb2-8f65-b5108b65367e" /> <img width="419" alt="Image" src="https://github.com/user-attachments/assets/3024cf1f-10c6-48c1-98fc-a018830c07d8" /> Generally speaking, should slaac / auto really be active in every default setting? Or would you prefer “none” with optional variable transfer?
saavagebueno commented 2025-11-20 04:50:40 -05:00
Author
Owner
Copy Link

@Tinsus commented on GitHub (Jun 28, 2025):

Thanks for your work.
I just tested that script.

First of all: with the default settings the IPv6 (using 1 as first input) selects static.

Using the advanced settings (3 on first input) and than only using the default values does exactly what I intended to reach by creating this ticket.
I got this error on my first try:

✔️ Started LXC Container ⠦ Customizing LXC Container [ERROR] in line 1279: exit code 0: while executing command pct exec "$CTID" -- bash -c "echo $tz >/etc/timezone && ln -sf /usr/share/zoneinfo/$tz /etc/localtime"

but with a very new try (again: first 3, than enter only) everything works great.

your question:
I run an IPv6 internally because I only see benefits doing that. My router doesnt need to use any funny tunneling-stuff with internal ipv4 internal traffic to the external ipv6 world. with my network SLAAC is the way also includes any LXC/VM to that very mindset. So for my egoistic view: yes, I would prefer SLAAC being the default for every default setting - because in none-ipv4-networks it simply gets ignored(?).

@Tinsus commented on GitHub (Jun 28, 2025): Thanks for your work. I just tested that script. First of all: with the default settings the IPv6 (using 1 as first input) selects static. Using the advanced settings (3 on first input) and than only using the default values does exactly what I intended to reach by creating this ticket. I got this error on my first try: ` ✔️ Started LXC Container ⠦ Customizing LXC Container [ERROR] in line 1279: exit code 0: while executing command pct exec "$CTID" -- bash -c "echo $tz >/etc/timezone && ln -sf /usr/share/zoneinfo/$tz /etc/localtime"` but with a very new try (again: first 3, than enter only) everything works great. your question: I run an IPv6 internally because I only see benefits doing that. My router doesnt need to use any funny tunneling-stuff with internal ipv4 internal traffic to the external ipv6 world. with my network SLAAC is the way also includes any LXC/VM to that very mindset. So for my egoistic view: yes, I would prefer SLAAC being the default for every default setting - because in none-ipv4-networks it simply gets ignored(?).
saavagebueno commented 2025-11-20 04:50:40 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 30, 2025):

Merged into main

@MickLesk commented on GitHub (Jun 30, 2025): Merged into main
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#585
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?