| Age | Commit message (Collapse) | Author |
|---|
|
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
}
|
