<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/data/templates/frr/zebra.route-map.frr.j2, 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>2025-05-29T12:35:09+00:00</updated>
<entry>
<title>zebra: T7349: Added importing routes from non to the kernel routing table</title>
<updated>2025-05-29T12:35:09+00:00</updated>
<author>
<name>aapostoliuk</name>
<email>108394744+aapostoliuk@users.noreply.github.com</email>
</author>
<published>2025-05-29T12:35:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=a439be2447f5f7e8be19c6f5b86f8dcc3d056385'/>
<id>urn:sha1:a439be2447f5f7e8be19c6f5b86f8dcc3d056385</id>
<content type='text'>
* zebra: T7349: Added importing routes from non to the kernel routing table

Added importing routes from non to the kernel routing table.

---------

Co-authored-by: Christian Breunig &lt;christian@breunig.cc&gt;</content>
</entry>
<entry>
<title>frr: T6746: handle "system ip" and "system ipv6" with FRRender class</title>
<updated>2024-12-16T21:24:50+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-12-11T20:07:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=2e4725cd77a33f91e091d86d94056f43dafd153d'/>
<id>urn:sha1:2e4725cd77a33f91e091d86d94056f43dafd153d</id>
<content type='text'>
FRR 10.2 will use "[no] ip forwarding" and "[no] ipv6 forwarding" to enable or
disable IP(v6) forwarding. We no longer rely on sysctl as this was overridden
by FRR later on.

Remove code path for sysctl setting and solely rely on FRR.
</content>
</entry>
<entry>
<title>T6001: add option to disable next-hop-tracking resolve-via-default</title>
<updated>2024-02-16T07:32:52+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-02-15T21:54:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=ece0e768f36e52f8964823d891264d7c187204ec'/>
<id>urn:sha1:ece0e768f36e52f8964823d891264d7c187204ec</id>
<content type='text'>
* set system ip nht no-resolve-via-default
* set system ipv6 nht no-resolve-via-default
</content>
</entry>
<entry>
<title>T5150: initial VRF support for Kernel/Zebra route-map filtering</title>
<updated>2023-04-13T07:01:31+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-04-10T08:57:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=b454ddc8c2cc0edbdc832bd60ef03a1819a6d8d6'/>
<id>urn:sha1:b454ddc8c2cc0edbdc832bd60ef03a1819a6d8d6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>T5150: initial implementation of new Kernel/Zebra route-map support</title>
<updated>2023-04-13T07:01:31+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-04-08T20:09:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=3f4de1390d6459cdd17dd1b6f22b1a3aec002671'/>
<id>urn:sha1:3f4de1390d6459cdd17dd1b6f22b1a3aec002671</id>
<content type='text'>
It is possible to install a route-map which filters the routes between routing
daemons and the OS kernel (zebra)

As of now this can be done by e.g.
* set protocols ospf route-map foo
* set protocols ospfv3 route-map foo
* set protocols bgp route-map foo

Which in turn will install the following lines into FRR
* ip protocol ospf route-map foo
* ipv6 protocol ospf6 route-map foo
* ip protocol bgp route-map foo

The current state of the VyOS CLI is incomplete as there is no way to:
* Install a filter for BGP IPv6 routes
* Install a filter for static routes
* Install a filter for connected routes

Thus the CLI should be redesigned to close match what FRR does for both the
default and any other VRF

* set system ip protocol ospf route-map foo
* set system ipv6 protocol ospfv3 route-map foo
* set system ip protocol bgp route-map foo
* set system ipv6 protocol bgp route-map foo

The configuration can be migrated accordingly. This commit does not come with
the migrator, it will be comitted later.
</content>
</entry>
</feed>
