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 ifupdown2] add ovs support for fakebridge.
Date: Fri, 14 Oct 2022 15:26:06 +0200	[thread overview]
Message-ID: <314ce1fb-3a40-2d23-0576-a49b74b57487@proxmox.com> (raw)
In-Reply-To: <20221014072235.2902517-1-aderumier@odiso.com>

Am 14/10/2022 um 09:22 schrieb Alexandre Derumier:
> This was request by a proxmox user on ifupdown2 github issues.
> 
> https://github.com/CumulusNetworks/ifupdown2/issues/245
> 
> It was possible to do it with ifupdown1, but not ifupdown2.
> 
> The patch is already applied upstream
> https://github.com/CumulusNetworks/ifupdown2/pull/246
> 
> example to define a fake ovs bridge with vlan10:
> 
> auto vmbr0
> iface vmbr0 inet manual
>         ovs_type OVSBridge
> 
> auto vmbr0v10
> iface vmbr0v10 inet manual
>         ovs_type OVSBridge
>         ovs_bridge vmbr0
>         ovs_options vmbr0 10
> 
> Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> ---
>  debian/patches/series                         |  3 +-
>  .../0001-ovs-add-support-for-fakebridge.patch | 57 +++++++++++++++++++
>  2 files changed, 59 insertions(+), 1 deletion(-)
>  create mode 100644 debian/patches/upstream/0001-ovs-add-support-for-fakebridge.patch
> 
>

applied, thanks!

Would be great if upstream would finally do a bump..
https://github.com/CumulusNetworks/ifupdown2/issues/211#issuecomment-1196842942




      reply	other threads:[~2022-10-14 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  7:22 [pve-devel] " Alexandre Derumier
2022-10-14 13:26 ` 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=314ce1fb-3a40-2d23-0576-a49b74b57487@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