From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Mark Schouten <mark@tuxis.nl>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [PVE-User] Proxmox VE 7.0 (beta) released!
Date: Tue, 29 Jun 2021 14:27:52 +0200 (CEST) [thread overview]
Message-ID: <14296680.254.1624969672688@webmail.proxmox.com> (raw)
> On 06/29/2021 2:04 PM Mark Schouten <mark@tuxis.nl> wrote:
>
>
> Hi,
>
> Op 29-06-2021 om 12:31 schreef Thomas Lamprecht:
> >> I do not completely understand why that fixes it though. Commenting out MACAddressPolicy=persistent helps, but why?
> >>
> >
> > Because duplicate MAC addresses are not ideal, to say the least?
>
> That I understand. :)
>
> But, the cluster interface works when bridge_vlan_aware is off,
> regardless of the MacAddressPolicy setting.
Yep, this may actually need more investigation, as I also had this issue on a single PVE VM on my ArchLinux host.
- definitely no duplicate mac addresses there
- no MAC related firewall settings
- network traffic *routed* off of a bridge on the host (so the final physical nic being an intel one should also not influence this)
- works when disabling `bridge-vlan-aware`
- still works when enabling vlan filtering via /sys after the fact
- also works with MACAddressPolicy commented out *regardless* of `bridge-vlan-aware`...
Also tried using systemd-networkd for the bridge in place of ifupdown2.
Same behavior when toggling `VLANFiltering` in the [Bridge] section...
Also note that similar to manually enabling vlan filtering via /sys, simply enabling `VLANFiltering` and restarting `systemd-networkd` does not actually break it, only if I delete the bridge first and then let systemd-network recreate it from scratch it'll be broken...
Curious stuff...
next reply other threads:[~2021-06-29 12:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 12:27 Wolfgang Bumiller [this message]
[not found] <kcEE.HSoMZfIyQreLVdFDq7JFjQ.AFttFk5y1wE@ckcucs11.intern.ckc-it.at>
2021-07-06 10:22 ` Stoiko Ivanov
-- strict thread matches above, loose matches on Subject: below --
2021-06-24 13:16 Martin Maurer
2021-06-29 8:05 ` Mark Schouten
2021-06-29 8:23 ` Stoiko Ivanov
2021-06-29 8:34 ` Mark Schouten
2021-06-29 9:46 ` Thomas Lamprecht
2021-06-29 10:06 ` Mark Schouten
2021-06-29 10:31 ` Thomas Lamprecht
2021-06-29 12:04 ` Mark Schouten
2021-06-29 13:31 ` Stoiko Ivanov
2021-06-29 13:51 ` alexandre derumier
2021-06-29 14:14 ` Thomas Lamprecht
2021-07-02 20:57 ` Thomas Lamprecht
2021-07-02 21:06 ` Mark Schouten
[not found] ` <mailman.239.1625514988.464.pve-user@lists.proxmox.com>
2021-07-06 9:55 ` Stoiko Ivanov
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=14296680.254.1624969672688@webmail.proxmox.com \
--to=w.bumiller@proxmox.com \
--cc=mark@tuxis.nl \
--cc=pve-user@lists.proxmox.com \
--cc=t.lamprecht@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.