public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Gabriel Goller <g.goller@proxmox.com>
To: Christoph Heiss <c.heiss@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH installer 2/2] install: do not force gateway to IPv6 RA-received on non-bridged setups
Date: Wed, 10 Jun 2026 16:46:57 +0200	[thread overview]
Message-ID: <ti6vdmijukq6guxs5xqtkdcnmrkq3khallfjkzll4semaz54s3@zczmyfenyln3> (raw)
In-Reply-To: <20260610132710.199825-2-c.heiss@proxmox.com>

On 10.06.2026 15:27, Christoph Heiss wrote:
> Skip writing the default gateway for the management interface to
> /etc/network/interfaces if it was originally received through an IPv6
> RA.
> 
> Otherwise, fresh, non-bridged (aka. anything other than PVE)
> installations will repeatedly, i.e. on every received RA advertising a
> different SLAAC-capable prefix, report an error in the journal that a
> default gateway already exists.
> 
> The Rust struct definitions are not touched, as the information is not
> needed there (yet).
> 
> Suggested-by: Gabriel Goller <g.goller@proxmox.com>
> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>

Also for the record, because we talked about it:

This only affects pmg, pbs and pdm, because there we set the ip address directly
on the physical interface. In pve the physical interface is enslaved on the
default vmbr0 bridge and the bridge has an ip address. When
ifupdown2 creates a bridge with an ip address, then automatically
adds net.ipv6.conf.vmbr0.forwarding=1 (the bridge also has the default
net.ipv6.conf.vmbr0.accept_ra=1), which means it will drop every RA. So maybe we
should set accept_ra=2 so that the bridge can accept RAs?

Anyway, we can defer the pve problem for later -- pbs,pmg,pdm are more important
because there we get a kernel error every few seconds.

We also thought more generally about if we should disable RAs on the physical
(or management) nics, because we always want to have a static address on our
installations and dhcp/slaac are actually just "autofills" in the installer?

Note: Search "accept_ra" on https://docs.kernel.org/networking/ip-sysctl.html.





  parent reply	other threads:[~2026-06-10 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 13:27 [PATCH installer 1/2] sys: net: make routes hash always defined Christoph Heiss
2026-06-10 13:27 ` [PATCH installer 2/2] install: do not force gateway to IPv6 RA-received on non-bridged setups Christoph Heiss
2026-06-10 14:38   ` Gabriel Goller
2026-06-10 14:46   ` Gabriel Goller [this message]
2026-06-10 19:41 ` applied: [PATCH installer 1/2] sys: net: make routes hash always defined 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=ti6vdmijukq6guxs5xqtkdcnmrkq3khallfjkzll4semaz54s3@zczmyfenyln3 \
    --to=g.goller@proxmox.com \
    --cc=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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal