<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/smoketest/configs/vrf-ospf, branch feature/T9082-codeql-cpp</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2022-05-25T16:42:44+00:00</updated>
<entry>
<title>configtest: T4382: remove typo</title>
<updated>2022-05-25T16:42:44+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2022-05-24T18:42:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=b2d06425d89e1e41dba96639f419656082586c02'/>
<id>urn:sha1:b2d06425d89e1e41dba96639f419656082586c02</id>
<content type='text'>
This is a typo in vrf-ospf: 'system nt' on the line before 'system ntp'.
</content>
</entry>
<entry>
<title>vrf: T3344: move dynamic routing protocols under "vrf name &lt;name&gt; protocols"</title>
<updated>2021-03-14T13:46:01+00:00</updated>
<author>
<name>Christian Poessinger</name>
<email>christian@poessinger.com</email>
</author>
<published>2021-03-13T20:08:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=548d9057e3ed66852bb2be62fe770c265712b4f3'/>
<id>urn:sha1:548d9057e3ed66852bb2be62fe770c265712b4f3</id>
<content type='text'>
Instead of having the dynamic routing protocols OSPF and BGP residing under
the "protocols vrf &lt;name&gt; [ospf|bgp]" nodes, rather move them directly under
the "vrf name &lt;name&gt; protocols [ospf|bgp]" node. Now all VRF related parts
are placed under the same root node.

This eases the verify steps tremendously, as we do not need to check wheter a
VRF eists or not, it will always exist as we operate under a child node.
</content>
</entry>
</feed>
