mirror of https://github.com/CumulusNetworks/ifupdown2.git synced 2024-05-06 15:54:50 +00:00

Go to file

Roopa Prabhu 3ac88e1553 Dont follow dependents during down of interfaces as part of ifreload

Testing Done: tested ifreload with example in the bug

ifdown of the bridge svi was following the lowerdev and downing the
bridge. kernel implicitly deletes all svi's on bridge down.
ifup of the bridge usually handles it, but a change done in 2.5.1
was causing it not to. Thinking about this some more, its safe
to not follow dependents on down during a ifreload. This patch does
just that.
(cherry picked from commit 03f7a376aee944b4037b7b7b02a5096e9360f79e)
(cherry picked from commit aac5777ecc7d367ada0681f813fbec7f78fa80ee)

2015-06-03 13:08:10 -04:00

ifupdown2

Dont follow dependents during down of interfaces as part of ifreload

2015-06-03 13:08:10 -04:00

packages/ifupdown2/debian

ifupdown2: fixup maintainer scripts to not crash on files not existing

2015-06-03 13:05:47 -04:00

README.md

Add note in readme regarding python-ifupdown2-addons being merged into

2015-03-06 22:43:50 -08:00

README.md

ifupdown2

ifupdown2 is a alternate implementation of debian's network interface manager ifupdown.

ifupdown2 provides the required infrastructure to parse, schedule and manage interface configuration. Also provides default python addon modules for network interface configuration.

Note: Previously ifupdown2 came as two packages: python-ifupdown2 and python-ifupdown2-addons. python-ifupdown2-addons contents are now merged into python-ifupdown2 package (python-ifupdown2-addons package is hence deprecated).