1 ifupdown2 (3.1.0-1+pmx3) bullseye; urgency=medium
3 * fix a point-to-point regression introduced in 3.1
5 -- Proxmox Support Team <support@proxmox.com> Mon, 26 Jul 2021 12:29:08 +0200
7 ifupdown2 (3.1.0-1+pmx2) bullseye; urgency=medium
9 * avoid re-generating and reloading network configuration in the installer
11 -- Proxmox Support Team <support@proxmox.com> Thu, 15 Jul 2021 10:35:31 +0200
13 ifupdown2 (3.1.0-1+pmx1) bullseye; urgency=medium
15 * update to 3.1.0 upstream release
17 * ship default policy to enable setting the MAC of a bridge to its first
20 -- Proxmox Support Team <support@proxmox.com> Wed, 14 Jul 2021 16:58:03 +0200
22 ifupdown2 (3.0.0-1+pve6) bullseye; urgency=medium
24 * always trigger a reload on first installation, to cope with ifupdown1
25 doing a networking stop on its way out.
27 -- Proxmox Support Team <support@proxmox.com> Tue, 06 Jul 2021 14:00:17 +0200
29 ifupdown2 (3.0.0-1+pve5) bullseye; urgency=medium
31 * fix shipping networking.service for updated debhelper compat level
33 -- Proxmox Support Team <support@proxmox.com> Tue, 25 May 2021 10:36:40 +0200
35 ifupdown2 (3.0.0-1+pve4) bullseye; urgency=medium
37 * re-build for Proxmox VE 7 / Debian Bullseye
39 -- Proxmox Support Team <support@proxmox.com> Mon, 24 May 2021 12:38:32 +0200
41 ifupdown2 (3.0.0-1+pve3) buster; urgency=medium
43 * allow vlan tag inside vxlan tunnel
45 * only rewrite config on first ifupdown2 installation
47 * update ifupdown2 submodule to current master
49 -- Proxmox Support Team <support@proxmox.com> Fri, 25 Sep 2020 09:17:21 +0200
51 ifupdown2 (3.0.0-1+pve2) pve; urgency=medium
53 * OVS already manages the MTU if 'ovs-mtu' is defined, mind that.
55 -- Proxmox Support Team <support@proxmox.com> Fri, 05 Jun 2020 08:31:14 +0200
57 ifupdown2 (3.0.0-1+pve1) pve; urgency=medium
59 * update to new 3.0.0 upstream release
61 -- Proxmox Support Team <support@proxmox.com> Wed, 03 Jun 2020 09:22:02 +0200
63 ifupdown2 (2.0.1-1+pve10) pve; urgency=medium
65 * avoid bringing network config in sync if pve-common isn't available
67 * openvswitch: do not remove tap|veth interfaces when adding an internal ovs
70 -- Proxmox Support Team <support@proxmox.com> Tue, 19 May 2020 22:11:49 +0200
72 ifupdown2 (2.0.1-1+pve8) pve; urgency=medium
74 * drop now outdated allow=ovs systemd service ExecStart/Stop adaption
76 -- Proxmox Support Team <support@proxmox.com> Mon, 16 Mar 2020 06:33:45 +0100
78 ifupdown2 (2.0.1-1+pve7) pve; urgency=medium
80 * fupdown2-pre.service: fix udevadm path for non usr-merged systems
82 -- Proxmox Support Team <support@proxmox.com> Tue, 10 Mar 2020 08:09:53 +0100
84 ifupdown2 (2.0.1-1+pve6) pve; urgency=medium
86 * add openvswitch addon
88 * add patch to ifup/ifdown allow=ovs on start/stop
90 * add ifupdown2-pre.service service to be sure that networking devices are
91 correctly setup before networking service is started
93 * do not change interface forwarding value if not defined
95 * read/write the network configuration on upgrade and removal of the
96 ifupdown2 package, writing eventual changes to the pending 'interfaces.new'
97 changes file. This ensures compatibility adapations for a respective
98 ifupdwon2 or ifupdown1 version are enforced.
100 -- Proxmox Support Team <support@proxmox.com> Mon, 09 Mar 2020 13:25:58 +0100
102 ifupdown2 (2.0.1-1+pve4) pve; urgency=medium
104 * execute addon scripts before module to ensure OVS interfaces are available
105 at the time they're now being configured...
107 -- Proxmox Support Team <support@proxmox.com> Mon, 03 Feb 2020 10:53:43 +0100
109 ifupdown2 (2.0.1-1+pve3) pve; urgency=medium
111 * fix ordering and dependencies of networking.service
113 -- Proxmox Support Team <support@proxmox.com> Thu, 30 Jan 2020 12:51:45 +0100
115 ifupdown2 (2.0.1-1+pve2) pve; urgency=medium
119 -- Proxmox Support Team <support@proxmox.com> Mon, 13 Jan 2020 09:14:22 +0100
121 ifupdown2 (1.2.8-1+pve4) pve; urgency=medium
123 * add arp-accept option required for bgp-evpn
125 * config: keep addon_syntax_check off to allow openvswitch syntax
127 -- Proxmox Support Team <support@proxmox.com> Tue, 26 Nov 2019 14:29:11 +0100
129 ifupdown2 (1.2.8-1+pve3) pve; urgency=medium
131 * re-add config tuning patch to allow multiple VLAN aware bridges and
132 allow `ovs_*` options to co-exist
134 -- Proxmox Support Team <support@proxmox.com> Fri, 30 Aug 2019 06:58:55 +0200
136 ifupdown2 (1.2.8-1+pve2) pve; urgency=medium
138 * restore the behavior to not remove (tap|veth|fwpr) interfaces from bridges
141 -- Proxmox Support Team <support@proxmox.com> Wed, 28 Aug 2019 16:43:11 +0200
143 ifupdown2 (1.2.8-1+pve1) pve; urgency=medium
145 * update to upstream 1.2.8-1 release
147 -- Proxmox Support Team <support@proxmox.com> Wed, 28 Aug 2019 11:06:45 +0200
149 ifupdown2 (1.2.5-2+pve1) pve; urgency=medium
151 * don't remove bridge if tap|veth|fw are connected
152 * ifup/ifdown vxlan interface on reload
153 * update to current upstream master
154 * add uplink-id option
156 -- Proxmox Support Team <support@proxmox.com> Tue, 18 Jun 2019 10:22:34 +0200
158 ifupdown2 (1.2.5-1+pvetest1) unstable; urgency=medium
162 -- Proxmox Support Team <support@proxmox.com> Tue, 16 Apr 2019 10:00:00 +0200
164 ifupdown2 (1.2.2-1+pvetest1) unstable; urgency=medium
168 -- Proxmox Support Team <support@proxmox.com> Mon, 31 Dec 2018 09:00:00 +0200
170 ifupdown2 (1.2.0-1+pvetest1) unstable; urgency=medium
172 * Update to 1.2.0 tag with some fixups from master-next
174 -- Proxmox Support Team <support@proxmox.com> Tue, 03 Jul 2018 10:47:42 +0200
176 ifupdown2 (1.2.0-1~pvetest3) unstable; urgency=medium
178 * allow specifying addresses on vlan aware bridges
180 -- Proxmox Support Team <support@proxmox.com> Mon, 18 Jun 2018 10:05:00 +0200
182 ifupdown2 (1.2.0-1~pvetest2) unstable; urgency=medium
184 * readd patch for vxlan/anycast support
186 -- Proxmox Support Team <support@proxmox.com> Mon, 18 Jun 2018 09:56:51 +0200
188 ifupdown2 (1.2.0-1~pvetest1) unstable; urgency=medium
190 * Initial 1.2.0 package
192 -- Proxmox Support Team <support@proxmox.com> Fri, 15 Jun 2018 09:14:59 +0200