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] ifupdown2 "bridge_set_static_mac_from_port" policy
Date: Wed, 14 Jul 2021 07:38:06 +0200 [thread overview]
Message-ID: <3ac18ec6-e4e2-e52e-a5a0-0949b4b6eccb@proxmox.com> (raw)
In-Reply-To: <75efa993d34cb722b91d0a1b378664c3d026f2a9.camel@odiso.com>
On 13.07.21 07:16, alexandre derumier wrote:
> Hi,
> it seem that it's possible to enable some policy on bridge in ifupdown2
>
>
> cumulus linux distro for example, have this policy
>
> $ cat /var/lib/ifupdown2/policy.d/bridge.json
> {
> "bridge": {
> "module_globals": {
> "warn_on_untagged_bridge_absence": "yes",
> "vxlan_bridge_default_igmp_snooping": "off",
> "allow_arp_nd_suppress_only_on_vxlan": "yes",
> "bridge_set_static_mac_from_port": "yes"
> },
> "defaults": {
> "bridge-stp": "on",
> "bridge-vlan-stats" : "on",
> "bridge-mcstats" : "on",
> "bridge-portprios": "8",
> "bridge-hashel": "4096",
> "bridge-hashmax": "4096",
> "bridge-ageing": "1800"
> }
> }
> }
>
>
> bridge_set_static_mac_from_port could be usefull to reuse physical
> interface mac on bridge.
>
sounds good in theory, but to which port? As with more than one it's important
to be deterministic - that's why we had that kernel patch in the first place.
next prev parent reply other threads:[~2021-07-14 5:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 5:16 alexandre derumier
2021-07-14 5:38 ` Thomas Lamprecht [this message]
2021-07-14 6:19 ` Thomas Lamprecht
2021-07-14 10:16 ` alexandre derumier
2021-07-14 10:53 ` alexandre derumier
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=3ac18ec6-e4e2-e52e-a5a0-0949b4b6eccb@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