public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	"DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
Subject: Re: [pve-devel] seem than ifupdown2 is installed by default on upgrade (a friend reported me an ipv6 slaac bug)
Date: Fri, 24 Nov 2023 10:07:30 +0100	[thread overview]
Message-ID: <1219a4b0-2750-4c36-b1db-1d4e61659278@proxmox.com> (raw)
In-Reply-To: <d7a3546d868e0d5d8c495b0f4974d501aaadd814.camel@groupe-cyllene.com>

Am 23/11/2023 um 18:50 schrieb DERUMIER, Alexandre:
> Hi,
> 
> I have a friend who's reported my than ifupdown2 had been installed by
> default on pve 8.1 upgrade.
> 
> I think it's because pve-network have "Recommends: ifupdown2".
> 

Well, that was the case since almost forever, but since we added a
recommends for libpve-network-perl to pve-container, qemu-serber and
pve-manager, the SDN packages gets pulled in if APT::Install::Recommends 
is true (by default for most installation) and then also ifupdown2.

But the apt full-upgrade output before the "continue?" prompt shows that,
and allows an admin to still avoid that switch.

I mean also Debian devs ponder about changing the default from ifupdown2 for
a future release [0], as ifupdown is mostly on life-support since a while.

[0]: https://lists.debian.org/debian-devel/2023/06/msg00226.html

We have not yet decided when to fully drop support for old ifudpown, but
for PBS we only ever supported ifupdown2 (we use only the CIDR notation for
passing addresses), but I think that might only be one or two major
releases away – the ifupdown network parsers would *really* benefit from
a bigger overhaul, and dropping support for legacy network might make
that a bit easier.

> Seem that it have impacted the slaac config.   (I had double check some
> months ago ipv6 with ifupdown2, all was ok,  but maybe default
> accept_ra is different if ifupdown2, not 100% sure ye)
> 

If we can improve the transition it'd be naturally nice, but I do not want
to drop that recommendation again for ifupdown2.

thanks,
 Thomas




  reply	other threads:[~2023-11-24  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23 17:50 DERUMIER, Alexandre
2023-11-24  9:07 ` Thomas Lamprecht [this message]
2023-11-24 10:12   ` DERUMIER, Alexandre
2023-11-24 12:49     ` Thomas Lamprecht
2023-11-24 13:12       ` DERUMIER, Alexandre
2023-11-24 13:41       ` DERUMIER, Alexandre
2023-11-29 12:55         ` DERUMIER, Alexandre

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=1219a4b0-2750-4c36-b1db-1d4e61659278@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=alexandre.derumier@groupe-cyllene.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