| Age | Commit message (Collapse) | Author |
|---|
|
cpo@PE1:~$ show bgp vrf all
Instance default:
No BGP prefixes displayed, 0 exist
Instance red:
BGP table version is 1, local router ID is 10.2.1.1, vrf id 11
Default local pref 100, local AS 100
Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
i internal, r RIB-failure, S Stale, R Removed
Nexthop codes: @NNN nexthop's vrf id, < announce-nh-self
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 10.2.1.0/24 0.0.0.0 0 32768 ?
Displayed 1 routes and 1 total paths
Instance blue:
BGP table version is 1, local router ID is 10.1.1.1, vrf id 10
Default local pref 100, local AS 100
Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
i internal, r RIB-failure, S Stale, R Removed
Nexthop codes: @NNN nexthop's vrf id, < announce-nh-self
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 10.1.1.0/24 0.0.0.0 0 32768 ?
Displayed 1 routes and 1 total paths
|
|
This change makes it easier to group all BGP related operational level command
building blocks in one place.
|
|
|
|
After commit 73557d68 ("bgp: T1711: remove ASN tagNode and move to 'local-as'")
when the BGP tag node was removed there is no need anymore for a script based
completion helper, we can rather rely on the build in "path" variant.
|
|
nat: op-mode: T3435: Filter extra rules that should not be processed
|
|
This was not possible due to a regression in iproute2 where the erspan_dir key
did not have a value. See [1] for more information.
[1]: https://lore.kernel.org/netdev/3ac544c09842410fb863b332917a03ad@poessinger.com/
|
|
|
|
This is a fix for commit 6f6f45c5 ("bgp: T3463: change no-ipv4-unicast order
when applying configuration") as this changed the handling of the "else" path,
which lead to failing smoketests as the "no bgp ebgp-requires-policy" option
was no longer set.
|
|
protocols: fix "bad" design and non working route-maps containing hyphens
|
|
The "no bgp default ipv4-unicast" option must be applied to FRR before adding
any neighbor to the system. If this is not the case, neighbors will start
exchanging v4 routes over v6 peers.
|
|
|
|
The introduction of key_mangling=('-', '_') when working with get_config_dict()
caused more harm then good. This commit extends common helpers and adds new
helpers when verifying the existence of route-maps, access-lists or prefix-lists.
|
|
|
|
|
|
|
|
Port over the regex used in the old node.def code-base and make this limitation
also live on the new CLI interface.
|
|
|
|
|
|
Commit 548d9057e3e (vrf: T3344: move dynamic routing protocols under "vrf name
<name> protocols") temporary removed the possibility to specify the VNI for a
given VRF to to changing of the CLI configuration nodes.
As VNI is set inside zebra, we can re-use the now widely deployed frr python
library to configure and change the configuration without any interference to
other FRR daemons.
|
|
Instead of having a dedicated ERSPAN interface type, rather move the specifics
into "interface tunnel". A migrator is not needed as there is yet no LTS release
with this feature and this is considered experimental.
|
|
For L2TPv3 to properly work there must be a routing entry present for the
remote side of the tunnel, or use a directly connected subnet.
|
|
|
|
RFC7348 recommends VXLAN tunnels preserve a 1500 byte MTU.
|
|
interfaces: dhcp-client: T3454: add reject option
|
|
When configuring a BGP neighbor via an interface, FRR requires that the
peer-group and remote-as node from under the interface statement is used.
This is now enforced by a verify() check.
|
|
|
|
When loading a configuration for BGP that contains the graceful-restart
options, the frr-reload script will not return 0, but the config is accepted.
This is a false positive, and related to https://github.com/FRRouting/frr/issues/8403
|
|
|
|
|
|
mode rules
|
|
|
|
Add a new CLI command "monitor log colored" to run the log file monitoring
through grc (https://github.com/garabik/grc).
|
|
|
|
Sometimes a modem might give a local IP before it retrieves a WAN IP.
This can be an issue with failover routes,
since the default route will get overridden.
|
|
frr: T3217: Ability to save routing configs
|
|
|
|
|
|
Commit 5b22ebae ("T3170: check if any generated node.def files are empty") added
an initial test to find empty node.def files created by build-command-templates
or build-command-op-templates.
The problem was that GNU find always returns 0, thus the condition to bail out
on error was always met. This has been corrected to return false on hits only.
|
|
... this has been migrated to vyos-1x.
|
|
This reverts commit d8c27642a3753513ae1d3c433fa46858a5ee946c.
|
|
T3170: check if any generated node.def files are empty.
|
|
Currently if there are XML nodes defined in multiple places it can and will
happen that one overrides the other. In this case, the "protocols static arp"
definition file overwrites the node.def file in the "protocols static" folder
that had a priority - the priority is essential for l2tpv3 to work.
|
|
conf-mode: Add Dvorak layout
|
|
|
|
frr: T3217: Fix permissions for saved configs
|
|
|
|
When validating FRR profiles, only load the configuration for each individual
profile instead of all profiles. This is done by a new argument to getFRRconfig()
named endsection='^!' which tells what is the delimiter when a config section
of FRR ends, this is usually "^!", but for BFD profiles this is "^ !", as this
is a new level under the FRR CLI.
|
|
|
|
|
|
|
