From: YUAN RUI via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: YUAN RUI <number201724@me.com>
Subject: [pve-devel] IPv6 document addresses are not allowed to be configured.
Date: Tue, 20 Jan 2026 18:24:06 +0800 [thread overview]
Message-ID: <mailman.447.1768905164.353.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 10604 bytes --]
From: YUAN RUI <number201724@me.com>
To: pve-devel@lists.proxmox.com
Subject: IPv6 document addresses are not allowed to be configured.
Date: Tue, 20 Jan 2026 18:24:06 +0800
Message-ID: <e6d92a6a-5835-4494-a7ae-6dfaa9ef0136@me.com>
In some cases, users may want to use the "DOCUMENTION" address as the
internal address of NAT66.
Shouldn't a check be added here to allow the configuration of document
address?
If ULA is used, systems such as Windows and Android will not prioritize
IPv6, so some users use addresses intended for documentation purposes to
bypass this restriction.
https://git.proxmox.com/?p=pve-manager.git;a=blob;f=PVE/API2/Network.pm;h=fc053fec7a8bae6dc30d2bb2870a2a94d3420231;hb=HEAD#l588
> my $check_ipv6_settings = sub {
> my ($address, $netmask) = @_;
>
> raise_param_exc({ netmask => "$netmask is not a valid subnet
> length for ipv6" })
> if $netmask < 0 || $netmask > 128;
>
> raise_param_exc({ address => "$address is not a valid host IPv6
> address." })
> if !Net::IP::ip_is_ipv6($address);
>
> my $binip = ipv6_tobin($address);
> my $binmask = Net::IP::ip_get_mask($netmask, 6);
>
> my $type = ($binip eq $binmask) ? 'ANYCAST' :
> Net::IP::ip_iptypev6($binip);
>
> if (defined($type) && $type !~
> /^(?:(?:GLOBAL|(?:UNIQUE|LINK)-LOCAL)-UNICAST)$/) {
> raise_param_exc(
> { address => "$address with type '$type', cannot be used
> as host IPv6 address." });
> }
> };
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2026-01-20 10:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.447.1768905164.353.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=number201724@me.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