From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH ifupdown2 0/3] update to last master + fixes
Date: Mon, 21 Sep 2020 18:51:12 +0200 [thread overview]
Message-ID: <20200921165115.2930386-1-aderumier@odiso.com> (raw)
Hi,
can you update the ifupdown2 mirror to last master ?
I have reworked the postinst/preinst to only generate /etc/network/interfaces.new
at first install of ifupdown2 only.
I have added a small patch to allow vlan inside vxlan tunnel,
and removed an old ovs patch now upstream.
Alexandre Derumier (3):
remove patch
0009-address-don-t-process_mtu-if-ovs-mtu-is-defined.patch
patch: allow vlan tag inside vxlan tunnel
update patch10: only rewrite config on first ifupdown2
...-t-process_mtu-if-ovs-mtu-is-defined.patch | 32 -------------
...9-allow-vlan-tag-inside-vxlan-tunnel.patch | 31 ++++++++++++
...-update-network-config-compatibility.patch | 47 +++++++++++++++----
debian/patches/series | 2 +-
4 files changed, 71 insertions(+), 41 deletions(-)
delete mode 100644 debian/patches/pve/0009-address-don-t-process_mtu-if-ovs-mtu-is-defined.patch
create mode 100644 debian/patches/pve/0009-allow-vlan-tag-inside-vxlan-tunnel.patch
--
2.20.1
next reply other threads:[~2020-09-21 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 16:51 Alexandre Derumier [this message]
2020-09-21 16:51 ` [pve-devel] [PATCH ifupdown2 1/3] remove patch 0009-address-don-t-process_mtu-if-ovs-mtu-is-defined.patch Alexandre Derumier
2020-09-21 16:51 ` [pve-devel] [PATCH ifupdown2 2/3] patch: allow vlan tag inside vxlan tunnel Alexandre Derumier
2020-09-21 16:51 ` [pve-devel] [PATCH ifupdown2 3/3] update patch10: only rewrite config on first ifupdown2 Alexandre Derumier
2020-09-25 7:30 ` [pve-devel] applied: [PATCH ifupdown2 0/3] update to last master + fixes 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=20200921165115.2930386-1-aderumier@odiso.com \
--to=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.