mirror/CumulusNetworks-ifupdown2
1
0
Fork 0
mirror of https://github.com/CumulusNetworks/ifupdown2.git synced 2024-05-06 15:54:50 +00:00
Code Activity
Files
a26be96ffb8e0eaed62b34561a3a28d48c04b8c9
CumulusNetworks-ifupdown2/config/addons.conf

38 lines
560 B
Plaintext
Raw Normal View History

new ifupdown2 link module to create dummy devices Ticket: CM-3525 Reviewed By: CCR-3326 Testing Done: Tested creating dummy devices using ifupdown2 This is modification to gospos loopback module. It solves the same purpose ie using linux dummy device like a loopback device but there were objections on calling it loopback so i have renamed it to link and i have changed it into a generic module that can do any 'ip link'. Can be extended for link args in the future. below example creates a loopy device $ifquery loopy auto loopy iface loopy link-type dummy $ifup loopy $ifquery -c loopy auto loopy iface loopy [pass] link-type dummy [pass] (cherry picked from commit 1151420408a53c106d29183a1e0da5562c8b03a3)
2015-08-12 23:30:55 -07:00
pre-up,link
Allow customer set bond defaults for CL with ifupdown2 Ticket: CM-6723 Reviewed By: roopa Testing Done: unit tested and testifupdown2 test suite This patch installs bond interface defaults in /etc/network/ifupdown2/policy.d/bond_defaults.json and allows users to modify this file. Users can then leave out these bond attributes in their configs to save typing and space. It also changes the ifenslave and ifenslaveutil module to bond and bondutil, respectively to be consistent with other modules (and also because customers think of "bond" interfaces not "ifenslave" interfaces.) For example, the default file installed looks like the following: { "README": "This file is user generated and modifiable.", "bond": { "defaults": { "bond-mode": "802.3ad", "bond-miimon": "100", "bond-use-carrier": "1", "bond-lacp-rate": "0", "bond-min-links": "1", "bond-xmic-hash-policy": "layer3+4" } } } Please enter the commit message for your changes. Lines starting
2015-07-22 18:38:07 -04:00
pre-up,bond
Add addon module for B.A.T.M.A.N. advanced interface configuration. (#12) * Add addon module for B.A.T.M.A.N. advanced interface configuration. This commit adds support for configuring B.A.T.M.A.N. advanced interfaces with ifupdown2. B.A.T.M.A.N. advanced is a protocol to build Layer2 based mesh networks with. It's supported in the Linux kernel and thus available in many Linux environments. A configuration could look like this auto bat0 iface bat0 batman-ifaces eth1 eth2.23 batman-ifaces-ignore-regex .*_nodes batman-hop-penalty 23 # address 192.0.2.42/24 where »bat0« would be the local connection to the mesh network. The interfaces »eth1« and »eth2.23« would be used by the B.A.T.M.A.N. adv. protocol to communicate to other member of the mesh network. Any interfaces matching the »ifaces-ignore-regex« will be gently ignored by ifquery and ifreload as there might be some tunnels or interfaces added to the mesh network by other means which should not be removed by any subsequent ifreload run. The »hop-penalty» parameter set the penalty of this node within the mesh network. Signed-off-by: Maximilian Wilhelm <max@rfc2324.org> * addons: batman_adv: replacing rtnetlink by netlink api call and iproute2 instantiation fix These changes are due to modifications we introduced in debian-prep2. We no longer use the rtnetlink_api but a new one "netlink" build on top of python-nlmanager. * Reflect upstream change where flags are stored. Signed-off-by: Maximilian Wilhelm <max@rfc2324.org>
2016-10-05 12:18:05 +02:00
pre-up,batman_adv
Move ifupdown2addons into ifupdown2 pacakge Ticket: CM-3864 Reviewed By: Testing Done: Tested build and install open item: - cleanup stale ifupdown2-addons package files
2014-10-09 16:02:46 -07:00
pre-up,vlan
pre-up,vxlan
ifupdown changes for active-active vxlan Ticket: CM-3715 Reviewed By: CCR-3065 Testing Done: unit testing Changes to proto down vxlan devices to avoid packet loops or duplicates before clagd checks consistency and installs egress acl rules. When vxlan device is brought up, check for presence of peer link and proto-down the device if peer link exists. - get_dependent_ifacenames is used to eliminate order dependency in specifying peer link and vxlan configuration in /etc/network/interfaces. - A separate script clagVxlanProtoDown is used to protodown vxlan devices if peer link is configured separately (ifup peerlink) and vxlan devices are already functional in the system.
2015-06-18 01:18:43 -07:00
pre-up,clagd
Move ifupdown2addons into ifupdown2 pacakge Ticket: CM-3864 Reviewed By: Testing Done: Tested build and install open item: - cleanup stale ifupdown2-addons package files
2014-10-09 16:02:46 -07:00
pre-up,usercmds
Fix a few ordering issues + fix following upperiface for bridge device Ticket: CM-3346 Reviewed By: Testing Done: sanity test
2014-10-10 14:05:19 -07:00
pre-up,bridge
First phase checkin for new format for vlan aware bridge Ticket: CM-3346 Reviewed By: Testing Done: Sanity test + test new bridge format There are a bunch of open issues with `vlan` interface handling. Below is the format. auto swp1 iface swp1 bridge-access 300 mstpctl-pathcost 0 mstpctl-adminedge yes mstpctl-autoedge yes mstpctl-p2p yes mstpctl-bpduguard yes mstpctl-treeprio 64 mstpctl-network yes mstpctl-bpdufilter yes auto swp2 iface swp2 bridge-vids 301 bridge-pvid 302 bridge-pathcost 10 bridge-priority 10 bridge-multicast-router 0 bridge-multicast-fast-leave 1 auto br0 iface br0 bridge-vlan-aware yes bridge-stp on bridge-ports swp1 swp2 bridge-vids 2001 auto br0.2001 iface br0.2001 address 10.0.14.2 hwaddress 00:03:00:00:00:12 address-virtual 00:00:5e:00:01:01 11.0.4.1/24 auto br0.2001 vlan br0.2001 bridge-igmp-querier-src 172.16.101.1
2014-10-24 10:11:07 -07:00
pre-up,bridgevlan
Fix a few ordering issues + fix following upperiface for bridge device Ticket: CM-3346 Reviewed By: Testing Done: sanity test
2014-10-10 14:05:19 -07:00
pre-up,mstpctl
addons: support for new addon module for vrf This patch adds initial support for vrf in ifupdown2. Example interfaces file section: auto swp1.100 iface swp1.100 vrf blue auto blue iface blue vrf-table 10 iproute2 vrf map is generated under: /etc/iproute2/rt_tables.d/ifupdown2.vrf_map this patch also adds prelimnary support for 'vrf-table auto'. But this needs more work. Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
2016-01-28 14:00:09 -08:00
pre-up,vrf
Move ifupdown2addons into ifupdown2 pacakge Ticket: CM-3864 Reviewed By: Testing Done: Tested build and install open item: - cleanup stale ifupdown2-addons package files
2014-10-09 16:02:46 -07:00
up,dhcp
up,address
up,addressvirtual
up,usercmds
post-up,ethtool
post-up,usercmds
Add clagd in the default shipped addons.conf and remove the editing of addons file Ticket: CM-4423 Reviewed By: Testing Done: tested ifupdown2 in the presence and absence of clagd This is a hack to get around an ifupdown2 limitation. The real fix should come as part of CM-3782
2014-12-09 13:49:23 -08:00
post-up,clagd
vxfld: ifupdown2 addon for vxrd Ticket: CM-6358 Reviewed By: roopa Testing Done: Yes ifupdown2 creates overrides vxrd's config when either (or both) the vxrd-src-ip and vxrd-svcnode-ip appear under the loopback interface's configuration. Example address 12.0.0.4/32 vxrd-src-ip 12.0.0.4 vxrd-svcnode-ip 99.99.99.9
2015-07-06 13:40:52 -07:00
post-up,vxrd
Move ifupdown2addons into ifupdown2 pacakge Ticket: CM-3864 Reviewed By: Testing Done: Tested build and install open item: - cleanup stale ifupdown2-addons package files
2014-10-09 16:02:46 -07:00
pre-down,usercmds
Add default link parameter support for ethtool module Ticket: CM-5254 Reviewed By: roopa Testing Done: tested master and 2.5_br images with testifupdown2 suite and hand tested This patch creates a json defaults file upon bootup (which can be overridden by customer configs in /etc) which the ethtool module in ifupdown2 will consult when "link-x" configs are removed in order to restore them to the initial settings used by the switch. (cherry picked from commit 8388664f5a5a85f2a813cafbf40ac92d7b86f4bf) Conflicts: packages/cl-utilities/usrlib/update-ports (cherry picked from commit 21c9c10ab2fccaf60be9accb337e82541d497cc4)
2015-05-10 15:42:47 -04:00
pre-down,ethtool
vxfld: ifupdown2 addon for vxrd Ticket: CM-6358 Reviewed By: roopa Testing Done: Yes ifupdown2 creates overrides vxrd's config when either (or both) the vxrd-src-ip and vxrd-svcnode-ip appear under the loopback interface's configuration. Example address 12.0.0.4/32 vxrd-src-ip 12.0.0.4 vxrd-svcnode-ip 99.99.99.9
2015-07-06 13:40:52 -07:00
pre-down,vxrd
addons: dhcp: stop IPv6 dhclient on ifdown and add delay before starting dhclient Ticket: CM-11043 Reviewed By: roopa Testing Done: used the config mentioned in bug This patch adds a delay before starting IPv6 dhclient to make sure the configured interface/link in up. Also, ifdown on a IPv6 interface, this patch makes sure that the link in up before dhcp release. Dhcp release is done using a default lease file. Signed-off-by: Nikhil <nikhil@cumulusnetworks.com>
2016-07-15 14:21:23 -07:00
pre-down,dhcp
Move ifupdown2addons into ifupdown2 pacakge Ticket: CM-3864 Reviewed By: Testing Done: Tested build and install open item: - cleanup stale ifupdown2-addons package files
2014-10-09 16:02:46 -07:00
down,addressvirtual
down,address
down,usercmds
addons: support for new addon module for vrf This patch adds initial support for vrf in ifupdown2. Example interfaces file section: auto swp1.100 iface swp1.100 vrf blue auto blue iface blue vrf-table 10 iproute2 vrf map is generated under: /etc/iproute2/rt_tables.d/ifupdown2.vrf_map this patch also adds prelimnary support for 'vrf-table auto'. But this needs more work. Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
2016-01-28 14:00:09 -08:00
post-down,vrf
Move clag_enable setting to ifupdown2 ifenslave. Ticket: CM-4802 Reviewed By: Testing Done: yes 1. clag_enable needs to be set before slaves are added to the bond. Otherwise bonding driver will bring the slaves up independent of clagd. 2. also added post_down clagd addon to cleanup the clag-id on ifdown.
2015-02-02 09:54:53 -08:00
post-down,clagd
Fix a few ordering issues + fix following upperiface for bridge device Ticket: CM-3346 Reviewed By: Testing Done: sanity test
2014-10-10 14:05:19 -07:00
post-down,mstpctl
First phase checkin for new format for vlan aware bridge Ticket: CM-3346 Reviewed By: Testing Done: Sanity test + test new bridge format There are a bunch of open issues with `vlan` interface handling. Below is the format. auto swp1 iface swp1 bridge-access 300 mstpctl-pathcost 0 mstpctl-adminedge yes mstpctl-autoedge yes mstpctl-p2p yes mstpctl-bpduguard yes mstpctl-treeprio 64 mstpctl-network yes mstpctl-bpdufilter yes auto swp2 iface swp2 bridge-vids 301 bridge-pvid 302 bridge-pathcost 10 bridge-priority 10 bridge-multicast-router 0 bridge-multicast-fast-leave 1 auto br0 iface br0 bridge-vlan-aware yes bridge-stp on bridge-ports swp1 swp2 bridge-vids 2001 auto br0.2001 iface br0.2001 address 10.0.14.2 hwaddress 00:03:00:00:00:12 address-virtual 00:00:5e:00:01:01 11.0.4.1/24 auto br0.2001 vlan br0.2001 bridge-igmp-querier-src 172.16.101.1
2014-10-24 10:11:07 -07:00
post-down,bridgevlan
Move ifupdown2addons into ifupdown2 pacakge Ticket: CM-3864 Reviewed By: Testing Done: Tested build and install open item: - cleanup stale ifupdown2-addons package files
2014-10-09 16:02:46 -07:00
post-down,bridge
post-down,vxlan
post-down,vlan
Allow customer set bond defaults for CL with ifupdown2 Ticket: CM-6723 Reviewed By: roopa Testing Done: unit tested and testifupdown2 test suite This patch installs bond interface defaults in /etc/network/ifupdown2/policy.d/bond_defaults.json and allows users to modify this file. Users can then leave out these bond attributes in their configs to save typing and space. It also changes the ifenslave and ifenslaveutil module to bond and bondutil, respectively to be consistent with other modules (and also because customers think of "bond" interfaces not "ifenslave" interfaces.) For example, the default file installed looks like the following: { "README": "This file is user generated and modifiable.", "bond": { "defaults": { "bond-mode": "802.3ad", "bond-miimon": "100", "bond-use-carrier": "1", "bond-lacp-rate": "0", "bond-min-links": "1", "bond-xmic-hash-policy": "layer3+4" } } } Please enter the commit message for your changes. Lines starting
2015-07-22 18:38:07 -04:00
post-down,bond
Add addon module for B.A.T.M.A.N. advanced interface configuration. (#12) * Add addon module for B.A.T.M.A.N. advanced interface configuration. This commit adds support for configuring B.A.T.M.A.N. advanced interfaces with ifupdown2. B.A.T.M.A.N. advanced is a protocol to build Layer2 based mesh networks with. It's supported in the Linux kernel and thus available in many Linux environments. A configuration could look like this auto bat0 iface bat0 batman-ifaces eth1 eth2.23 batman-ifaces-ignore-regex .*_nodes batman-hop-penalty 23 # address 192.0.2.42/24 where »bat0« would be the local connection to the mesh network. The interfaces »eth1« and »eth2.23« would be used by the B.A.T.M.A.N. adv. protocol to communicate to other member of the mesh network. Any interfaces matching the »ifaces-ignore-regex« will be gently ignored by ifquery and ifreload as there might be some tunnels or interfaces added to the mesh network by other means which should not be removed by any subsequent ifreload run. The »hop-penalty» parameter set the penalty of this node within the mesh network. Signed-off-by: Maximilian Wilhelm <max@rfc2324.org> * addons: batman_adv: replacing rtnetlink by netlink api call and iproute2 instantiation fix These changes are due to modifications we introduced in debian-prep2. We no longer use the rtnetlink_api but a new one "netlink" build on top of python-nlmanager. * Reflect upstream change where flags are stored. Signed-off-by: Maximilian Wilhelm <max@rfc2324.org>
2016-10-05 12:18:05 +02:00
post-down,batman_adv
Move ifupdown2addons into ifupdown2 pacakge Ticket: CM-3864 Reviewed By: Testing Done: Tested build and install open item: - cleanup stale ifupdown2-addons package files
2014-10-09 16:02:46 -07:00
post-down,usercmds
new ifupdown2 link module to create dummy devices Ticket: CM-3525 Reviewed By: CCR-3326 Testing Done: Tested creating dummy devices using ifupdown2 This is modification to gospos loopback module. It solves the same purpose ie using linux dummy device like a loopback device but there were objections on calling it loopback so i have renamed it to link and i have changed it into a generic module that can do any 'ip link'. Can be extended for link args in the future. below example creates a loopy device $ifquery loopy auto loopy iface loopy link-type dummy $ifup loopy $ifquery -c loopy auto loopy iface loopy [pass] link-type dummy [pass] (cherry picked from commit 1151420408a53c106d29183a1e0da5562c8b03a3)
2015-08-12 23:30:55 -07:00
post-down,link
Copy Permalink