summaryrefslogtreecommitdiff
path: root/interface-definitions/protocols-bfd.xml.in
AgeCommit message (Collapse)Author
2022-04-29xml: T4047: use full string match in the regex validatorChristian Poessinger
2021-12-09xml: T4058: provide building block for BFD profilesChristian Poessinger
2021-12-09xml: include: create dedicated bfd subfolderChristian Poessinger
2021-12-04bfd: T4044: add VRF support for peersChristian Poessinger
2021-11-07xml: provide and use common interface-name building blocksChristian Poessinger
2021-02-15bfd: T3310: implement peer profile supportChristian Poessinger
2021-02-15bfd: T3310: migrate to get_config_dict() and FRR reloadChristian Poessinger
2020-07-26Fix a typo in BFD command help.Daniil Baturin
2019-12-06T1843: run interface-definitions though GCC preprocessorChristian 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.