summaryrefslogtreecommitdiff
path: root/interface-definitions/include/ospf
AgeCommit message (Collapse)Author
2021-12-09xml: include: create dedicated bfd subfolderChristian Poessinger
2021-11-27ospf: T3753: adjust to CLI options new in FRR 8.0Christian Poessinger
FRR 7.5 router ospf passive-interface default no passive-interface eth0.202 Changed int FRR 8 to interface eth0.202 no ip ospf passive ! router ospf ospf router-id 172.18.254.202 log-adjacency-changes detail passive-interface default
2021-09-26ospf: T3757: add completion help when refering to area IDChristian Poessinger
This extends commit 6f87d8c910 ("ospf: T3757: support to configure area at an interface level") with a completion helper to show which Area ID is already in use when configuring the area for an interface.
2021-09-26ospfv3: T3859: add "log-adjacency-changes" CLI commandChristian Poessinger
2021-09-21xml: ospf: fix routing-passive-interface-xml.i includeChristian Poessinger
Commit a8b2e52148d ("xml: Update routing-passive-interface-xml.i file extension to standard .xml.i") only altered the RIP include statement but did not alter the OSPF include.
2021-08-29ospf: T3236: add possibility to redistribute "table"Christian Poessinger
Add new CLI command: * "set protocols ospf redistribute table <n>"
2021-08-29ospf: xml: T3236: update help stringsChristian Poessinger
2021-08-15ospf: T3757: support to configure area at an interface levelChristian Poessinger
FRR supports configuring either network prefixes per area, or assign an interface to an area to participate in the routing process. This is already well known from other venders and supported by FRR. A valid VyOS OSPF configuration would then look like: vyos@vyos# show protocols ospf { interface dum0 { area 0 } interface eth0.201 { area 0 authentication { md5 { key-id 10 { md5-key vyos } } } dead-interval 40 hello-interval 10 priority 1 retransmit-interval 5 transmit-delay 1 } log-adjacency-changes { detail } parameters { abr-type cisco router-id 172.18.254.201 } passive-interface default passive-interface-exclude eth0.201 }
2021-05-06vrf: ospf: T3523: add route-map support for kernel routesChristian Poessinger
2021-05-06xml: routing: use common router-id include fileChristian Poessinger
2021-05-06ospf: xml: T3236: restructure include files and make them easier to recognizeChristian Poessinger
2021-05-02Improve the OSPF CLI help strings.Daniil Baturin
(Capitalization fixes, more consice wording etc.)
2021-04-08ospf: T2271: zebra route-map can only be set for default VRFChristian Poessinger
2021-03-21xml: isis: ospf: re-arrange include blocksChristian Poessinger
2021-03-14xml: include: fix typo on include commentChristian Poessinger
When including XML files they all contained a comment from where the snipped had actually been included from. The comment had been "included start" and "included end" instead of "include start" and "include end". This commit corrects the glitch.
2021-03-14xml: ospf: consolidate router-id and distance settings in common include filesChristian Poessinger
2021-03-14xml: include: move route-map from ospf to generic sectionChristian Poessinger
2021-03-13vrf: ospf: T2271: re-arrange xml include building blocksChristian Poessinger
In order to fully re-use the XML based OSPF CLI definition for per-VRF routing, the file structure needs to be reorganized and the common OSPF definition is moved to its dedicated ospf-common-config.xml.i file, which can then be fully re-included at the VRF level. As the amount of include files now has reached a certain amount, this also introduces "per topic" subdirectories on the filesystem to keep a clean structure.