From: alexandre derumier <aderumier@odiso.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Mark Schouten <mark@tuxis.nl>
Cc: Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [PVE-User] Proxmox VE 7.0 (beta) released!
Date: Tue, 29 Jun 2021 15:51:06 +0200 [thread overview]
Message-ID: <0790b6524457e986e6f14176af5e2ee9d88a5d97.camel@odiso.com> (raw)
In-Reply-To: <20210629153111.2a0fbc28@rosa.proxmox.com>
Hi,
I have found a bug report about promisc && vlan-aware on mellanox site,
of a proxmox user.
(proxmox 6.4 with kernel (5.12?)
https://community.mellanox.com/s/question/0D51T00008ansfP/vlan-aware-linux-bridging-is-not-functional-on-connectx4lx-card-unless-manually-put-in-promiscuous-mode
So maybe is it a kernel change ?
I don't known is that ifupdown2 has been bumped to last master ? (I
don't have seen special commit of this kind of change)
Le mardi 29 juin 2021 à 15:31 +0200, Stoiko Ivanov a écrit :
> On Tue, 29 Jun 2021 14:04:05 +0200
> 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?
> > > >
> > >
> >
> > That I understand. :)
> >
> > But, the cluster interface works when bridge_vlan_aware is off,
> > regardless of the MacAddressPolicy setting.
> >
>
> We managed to find a reproducer - my current guess is that it might
> have
> something to do with intel NIC drivers or some changes in ifupdown2 (or
> udev, or in their interaction ;) - Sadly if tcpdump fixes the issues,
> it
> makes debugging quite hard :)
>
> In any case - as can also be seen in the 2 reports you sent:
> with vlan-aware bridges the promisc flag of the ethernet interface (the
> bridge-port) is set to 0, when vlan-aware is not present it is set to
> 1.
> This explains the symptoms you're seeing, and why running tcpdump fixes
> it
>
> FWIW: I think simply starting a guest would have fixed the issue as
> well
> (when a second bridge_port gets added the kernel sets the promisc flag
> on
> the port correctly)
>
> As Wolfgang wrote - we'll look into it and will hopefully come up with
> a
> sensible solution.
>
> Thanks for the beta-test and the report!
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2021-06-29 13:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 13:16 Martin Maurer
2021-06-24 14:08 ` [PVE-User] Error updating Ceph from Nautilus to Octopus Ralf Storm
2021-06-29 8:05 ` [PVE-User] Proxmox VE 7.0 (beta) released! 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 [this message]
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
2021-06-29 12:27 Wolfgang Bumiller
[not found] <kcEE.HSoMZfIyQreLVdFDq7JFjQ.AFttFk5y1wE@ckcucs11.intern.ckc-it.at>
2021-07-06 10:22 ` 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=0790b6524457e986e6f14176af5e2ee9d88a5d97.camel@odiso.com \
--to=aderumier@odiso.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox