From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH installer v2 0/9] add IPv6 SLAAC and v6-only support
Date: Mon, 11 May 2026 17:57:42 +0200 [thread overview]
Message-ID: <20260511155753.1623099-1-c.heiss@proxmox.com> (raw)
Most glaringly, neither the GUI nor TUI handled IPv6-only setups
correctly, in that the pre-filled values for the networking setup simply
defaulted to the IPv4 defaults.
Patch #1-#5 rework the installation "backend" and GUI side of things.
Patch #6 enables support for /127 and /128 IPv6 CIDRs, which we do
support elsewhere.
Finally, patch #8 enables sending router solicitations when the
installer starts, such than any IPv6 (SLAAC) configuration is retrieved.
Patches #6-#9 are independent and can be applied individually as such,
if desired.
History
=======
v1: https://lore.proxmox.com/pve-devel/20260508184546.113293-1-c.heiss@proxmox.com/
Notable changes v1 -> v2:
* dropped some old test data
* fix leftover ipconf usages in Proxmox::Install and GUI
* give routers a 2sec window to respond to router solicitations
Diffstat
========
pve-installer:
Christoph Heiss (9):
install: drop trivial fromjs() wrapper and use JSON::from_json()
install: move network subroutines to Proxmox::Sys::Net
install: use run_env->{network} instead of old run_env->{ipconf}
gui: use run_env->{network} instead of old run_env->{ipconf}
sys: net: drop the now-unused `ipconf` runtime environment
configuration
sys: net: allow up to /128 netmask for IPv6
sys: net: ignore ipv6 nameservers with zone identifiers
common: options: rework network address setup to handle ipv6-only
unconfigured: try to retrieve IPv6 SLAAC addresses on startup
Proxmox/Install.pm | 6 +-
Proxmox/Install/RunEnv.pm | 172 +------------
Proxmox/Sys/Net.pm | 238 ++++++++++++------
debian/control | 2 +
proxinstall | 86 +++++--
...n_from_dhcp_no_default_domain.run-env.json | 76 ------
.../no_fqdn_from_dhcp.run-env.json | 76 ------
.../tests/resources/run-env-info.json | 76 ------
proxmox-installer-common/src/options.rs | 89 ++++---
unconfigured.sh | 27 ++
10 files changed, 310 insertions(+), 538 deletions(-)
--
next reply other threads:[~2026-05-11 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 15:57 Christoph Heiss [this message]
2026-05-11 15:57 ` [PATCH installer v2 1/9] install: drop trivial fromjs() wrapper and use JSON::from_json() Christoph Heiss
2026-05-11 15:57 ` [PATCH installer v2 2/9] install: move network subroutines to Proxmox::Sys::Net Christoph Heiss
2026-05-11 15:57 ` [PATCH installer v2 3/9] install: use run_env->{network} instead of old run_env->{ipconf} Christoph Heiss
2026-05-11 15:57 ` [PATCH installer v2 4/9] gui: " Christoph Heiss
2026-05-11 15:57 ` [PATCH installer v2 5/9] sys: net: drop the now-unused `ipconf` runtime environment configuration Christoph Heiss
2026-05-11 15:57 ` [PATCH installer v2 6/9] sys: net: allow up to /128 netmask for IPv6 Christoph Heiss
2026-05-11 15:57 ` [PATCH RFC installer v2 7/9] sys: net: ignore ipv6 nameservers with zone identifiers Christoph Heiss
2026-05-11 15:57 ` [PATCH installer v2 8/9] common: options: rework network address setup to handle ipv6-only Christoph Heiss
2026-05-11 15:57 ` [PATCH installer v2 9/9] unconfigured: try to retrieve IPv6 SLAAC addresses on startup Christoph Heiss
2026-05-12 2:46 ` applied: [PATCH installer v2 0/9] add IPv6 SLAAC and v6-only support Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260511155753.1623099-1-c.heiss@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox