Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-03-04 | vrf: T31: enable vrf support for dummy interface | Christian Poessinger | |
2020-01-26 | Interfaces: unify interface help text | Christian Poessinger | |
2019-12-06 | T1843: use include files to disable interface (admin down) | Christian Poessinger | |
2019-12-06 | T1843: use include files for interface description | Christian Poessinger | |
2019-12-06 | T1843: recursively include IP address definitions in VIF/VIF-S definitions | Christian Poessinger | |
2019-12-06 | T1843: use include files for IPv4/IPv6 interface address configuration | Christian Poessinger | |
As 219779bc6151 ("T1843: run interface-definitions though GCC preprocessor") implemented the foundation of using the GCC preprocessor to make our XML definitions more lightweight this commit transforms the configuration of an IPv4/IPv6 address to this new style. It implementes it for the following interface types: * bond * bridge * dummy * ethernet * geneve * loopback * vxlan * wireguard * wireless | |||
2019-12-06 | T1843: run interface-definitions though GCC preprocessor | Christian Poessinger | |
A lot of XML code is duplicated (VLAN, interface address) for instance. Such XML definitions should be moved to feature.xml.i files and then just pulled in via GCC preprocessor #include definition in e.g. bond or ethernet definitions. This will give us the ability to single-source repeating node definitions as: * Interface Address * Interface Description * Interface Disable * VLAN (both vif-s and vif-c) The .in suffix of the interface-definitions is a marker that those files are input files to the GCC preprocessor. They will be rendered into proper XML files in the build directory. Some node definitions have been reworder to remove escaped double quote occurances which would have been warned about by the GCC preprocessor. |