| Age | Commit message (Collapse) | Author |
|---|
|
Keep all FRRender stuff in one place.
|
|
|
|
|
|
When running under vyos-configd only a single apply() is done as last step in
the commit algorithm. FRRender class address is provided via an attribute from
vyos-configd process.
|
|
With FRR 10.0 daemons started to be migrated to integrated FRR mgmtd and a
northbound interface. This led to some drawbacks in the current state how
changes to FRR are handled. The current implementation will use frr-reload.py
and specifies excatly WHICH daemon needs a config update and will only replace
this part inside FRR.
With FRR10 and mgmtd when a partial configuration is sent to mgmtd, it will
remove configuration parts from other daemons like bgpd or ospfd which have
not yet been migrated to mgmtd.
It's not possible to call frr-reload.py with daemon mgmtd - it will error out.
This commit will also change the CLI for static routes:
CLI command "set protocols static route 10.0.0.0/8 next-hop 1.2.3.4 bfd multi-hop
source 1.1.1.1" will be split into:
* set protocols static route 10.0.0.0/8 next-hop 1.2.3.4 bfd source-address 1.1.1.1
* set protocols static route 10.0.0.0/8 next-hop 1.2.3.4 bfd multi-hop
To make the XML blocks reusable, and comply with the FRR CLI - this was actually
a wrong implementation from the beginning as you can not have multiple BFD
source addresses.
CLI command "set protocols static route 10.0.0.0/8 next-hop 1.2.3.4 bfd multi-hop
source 1.1.1.1 profile bar" is changed to:
* set protocols static route 10.0.0.0/8 next-hop 1.2.3.4 bfd profile bar
CLI commands "set protocols static multicast interface-route" is moved to:
* set protocols static multicast route <x.x.x.x/x> interface
To have an identical look and feel with regular static routes.
|
|
|
|
|
|
found using "git ls-files *.py | xargs pylint | grep W0611"
|
|
* set protocols bfd peer <x.x.x.x> minimum-ttl <1-254>
* set protocols bfd profile <name> minimum-ttl <1-254>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Every node in running config now has an explicit "exit" tag.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We had two places were the is_ip, is_ipv4 and is_ipv6 helpers had been defined.
All places now have been converged into vyos.template as they are used both
in the Jinja2 templates and also in our scripts.
|
|
airbag must now be explicitly installed.
the patch also allow to fully disables the installation of the logging
code at setup (and not just installing and doing nothing)
|
|
|
|
convert all call to jinja to use template.render
|
|
os.system does print the ouput of the command, run() does not.
A new function called call() does the printing and return the error code.
|
|
|
|
As little change a possible but the function call
The behaviour should be totally unchanged.
|
|
|
|
IPv6 BFD peers only require a source address unless link-local addresses are used.
|
|
* added validations for "source address IP" and "bfd peer IP"
* added check for configuring multihop together with an interface name
* fixed "show protocols bfd peer X" for peers with custom options
|
|
* added option "echo-mode" and "echo-interval" for BFD peers
* added configuration check for usage "multihop" and "echo-mode"
* added configuration check for denying deletion BFD peers, which are used in BGP configuration
* fixed deleting/changing BFD peers with custom parameters (for example multihop, local-address, etc.)
* deleted wrong skipping of configuration check for "shutdown" BFD peers
|
|
|
|
vyos@vyos# show protocols
bfd {
peer 1.1.1.1 {
interval {
receive 400
transmit 300
}
}
}
|
|
|
|
Configures the detection multiplier to determine packet loss. The remote
transmission interval will be multiplied by this value to determine the
connection loss detection timer. The default value is 3.
Example: when the local system has detect-multiplier 3 and the remote
system has transmission interval 300, the local system will detect
failures only after 900 milliseconds without receiving packets.
|
|
Place address/interface under new source node.
vyis@vyos# show protocols bfd
peer 1.1.1.1 {
source {
address 1.2.3.4
interface eth0.201
}
}
|
|
multihop tells the BFD daemon that we should expect packets with TTL less than
254 (because it will take more than one hop) and to listen on the multihop port
(4784). When using multi-hop mode echo-mode will not work (see RFC 5883 section 3).
|
|
|
|
|
|
vyos@vyos# show protocols bfd
peer 172.18.202.10 {
local-address 172.18.201.10
local-interface eth0.201
shutdown
}
peer 172.18.202.12 {
shutdown
}
|
