From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexandre Derumier <aderumier@odiso.com>
Subject: Re: [pve-devel] [PATCH ifupdown2] patch: fix bond mac address at boot.
Date: Thu, 19 Oct 2023 10:53:22 +0200 [thread overview]
Message-ID: <9b1d6cf3-3adc-4ada-a107-0c7923fdefda@proxmox.com> (raw)
In-Reply-To: <20230901091231.155229-1-aderumier@odiso.com>
Am 01/09/2023 um 11:12 schrieb Alexandre Derumier:
> since systemd v241, like for bridge, the bond mac is setup
> randomly at boot, instead inherit from first slave.
>
> Then, on next ifreload, ifupdown2 was already fixing it,
> but with an down/up of the bond (with potentials impact on the network).
>
Hmm, we now got a few reports in the forum that get quite a few
"Received packet on bond0 with own address as source" warnings
after upgrading to ifupdown2 to the version that just ships this
patch here:
https://forum.proxmox.com/threads/kernel-vmbr0-received-packet-on-bond0-with-own-address-as-source-address.133152/#post-597121
https://forum.proxmox.com/threads/vmbr0-received-packet-on-bond0-with-own-address-as-source-address.135044/#post-597283
Seem like the switches send the ECTP loopback packages sometimes
back over the other link due both having the same MAC address,
Wolfgang thinks that shouldn't matter though..
They mention that a downgrade helps so even if this is a switch
(configuration) issue on their side it might not be ideal to regress
here – do you have any idea what's going on?
next prev parent reply other threads:[~2023-10-19 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 9:12 Alexandre Derumier
2023-09-13 18:10 ` DERUMIER, Alexandre
2023-09-15 14:21 ` [pve-devel] applied: " Thomas Lamprecht
2023-10-19 8:53 ` Thomas Lamprecht [this message]
2023-10-19 9:39 ` [pve-devel] " DERUMIER, Alexandre
2023-11-15 6:12 ` DERUMIER, Alexandre
2023-11-15 10:37 ` 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=9b1d6cf3-3adc-4ada-a107-0c7923fdefda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox