all lists on 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>,
	Alexandre Derumier <aderumier@odiso.com>
Subject: [pve-devel] applied: [PATCH pve-manager] disable systemd link macpolicy
Date: Wed, 15 Nov 2023 11:36:16 +0100	[thread overview]
Message-ID: <3137bfba-5ff8-4875-b996-129fb27a3f22@proxmox.com> (raw)
In-Reply-To: <20230917134444.3998037-1-aderumier@odiso.com>

Am 17/09/2023 um 15:44 schrieb Alexandre Derumier:
> since debian11, systemd is changing behaviour of macadress
> of bridge, but also bond, where the mac is generated randomly
> instead inherit from the first slave.
> 
> We already fix that with ifupdown2, but they are still another problem:
> 
> If a bridge don't have any slaves, systemd is keeping bridge offline.
> 
> https://www.justinsteven.com/posts/2023/03/26/virtualbox-bridge-ports-none-no-carrier-debian-11/
> 
> That mean that a dhcp daemon like kea can't bind on a standalone bridge (used for s-nat for example), until a
> tap interface is started.
> 
> This patch disable systemd mac policy (this don't break already fixed ifupdown2 mac),
> 
> funny but centos && fedora also disable it
> 
> https://fedoraproject.org/wiki/Changes/MAC_Address_Policy_none
> 
> https://gitlab.com/redhat/centos-stream/rpms/systemd/-/blob/c8953519504bf2e694bfbc2b02a456c1056f252e/0028-udev-net-setup-link-change-the-default-MACAddressPol.patch#L43
> 
> before this patch
> ------------------
> ~ ip a sh dev vmbr1
> vmbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 10
> 
> after this patch
> ----------------
> ~ ip a sh dev vmbr1
> vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
> ---
>  configs/Makefile            | 2 +-
>  configs/link-macpolicy.conf | 6 ++++++
>  2 files changed, 7 insertions(+), 1 deletion(-)
>  create mode 100644 configs/link-macpolicy.conf
> 
>

applied, thanks!
But i now install the config as `/usr/lib/systemd/network/98-proxmox-ve-default.link`,
because the ones from /etc/ belong to the user, not the distro, and the having a .d
file can have some slightly odd/unexpected effects if the user overrides parts of
the (systemd) defaults.




      reply	other threads:[~2023-11-15 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 13:44 [pve-devel] " Alexandre Derumier
2023-11-15 10:36 ` Thomas Lamprecht [this message]

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=3137bfba-5ff8-4875-b996-129fb27a3f22@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=aderumier@odiso.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal