| Age | Commit message (Collapse) | Author |
|---|
|
vyos@vyos:~$ show protocols bfd peer
BFD Peers:
peer 172.18.1.2 interface eth0.701
ID: 3762227714
Remote ID: 3787683864
Status: up
Uptime: 24 minute(s), 54 second(s)
Diagnostics: ok
Remote diagnostics: ok
Local timers:
Receive interval: 300ms
Transmission interval: 300ms
Echo transmission interval: 50ms
Remote timers:
Receive interval: 300ms
Transmission interval: 300ms
Echo transmission interval: 50ms
peer 172.18.0.2 interface eth0.700
ID: 3132309989
Remote ID: 859733951
Status: up
Uptime: 25 minute(s), 24 second(s)
Diagnostics: ok
Remote diagnostics: ok
Local timers:
Receive interval: 300ms
Transmission interval: 300ms
Echo transmission interval: 50ms
Remote timers:
Receive interval: 300ms
Transmission interval: 300ms
Echo transmission interval: 50ms
vyos@vyos:~$ show protocols bfd peer
Possible completions:
<Enter> Execute the current command
172.18.0.2 Show Bidirectional Forwarding Detection (BFD) peer status
172.18.1.2
vyos@vyos:~$ show protocols bfd peer 1
172.18.0.2 172.18.1.2
vyos@vyos:~$ show protocols bfd peer 172.18.0.2
BFD Peer:
peer 172.18.0.2 interface eth0.700
ID: 3132309989
Remote ID: 859733951
Status: up
Uptime: 25 minute(s), 29 second(s)
Diagnostics: ok
Remote diagnostics: ok
Local timers:
Receive interval: 300ms
Transmission interval: 300ms
Echo transmission interval: 50ms
Remote timers:
Receive interval: 300ms
Transmission interval: 300ms
Echo transmission interval: 50ms
|
|
|
|
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
}
|
|
[ firewall options interface wg01 ]
Traceback (most recent call last):
File "/usr/libexec/vyos/conf_mode/firewall_options.py", line 139, in <module>
apply(c)
File "/usr/libexec/vyos/conf_mode/firewall_options.py", line 97, in apply
if tcp['new_chain4']:
TypeError: 'NoneType' object is not subscriptable
delete [ firewall options ] failed
delete [ firewall ] failed
Commit failed
|
|
|
|
- added a validator for checking if the address is any cidr noted address
|
|
|
|
[ config ] T1447: Python subprocess called without import in host_nam…
|
|
|
|
|
|
|
|
|
|
dicts.
|
|
- checking if the hostname has changed, otherwise the script and systemd try to restart
rsyslogd at the same time, at the end it's not started at all.
|
|
|
|
|
|
|
|
|
|
It may be better to crash the process in that situation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
They are widely referenced by command templates, but a process started as a service
doesn't automatically get them.
|
|
This reverts commit 685b1e0d050c7883303733d710327161fe046b60.
|
|
* bgp-address-family:
T849: move BGP peer-group node to ipv4 address family
|
|
To have a consitent IPv4/IPv6 CLI a lot of BGP neighbor nodes have been
migrated. The IPv4 peer-group has been forgotten, leaving a non consistent CLI.
Previously:
-----------
neighbor 2001:DB8:FFFF::1 {
address-family {
ipv6-unicast {
peer-group iBGP
}
}
peer-group iBGP
}
Now:
----
neighbor 2001:DB8:FFFF::1 {
address-family {
ipv6-unicast {
peer-group iBGP
}
}
address-family {
ipv4-unicast {
peer-group iBGP
}
}
}
|
|
|
|
|
|
Accessing Kernel DMI data (under /sys/class/dmi) requires elevated permission
and thus retrieving a Board Serial/UUID was not possible.
version.py is now called via sudo to gether all facts.
|
|
|
|
... to have the same pattern as the DHCPDv6 lease file
|
|
A wrong lease file caused the show command to fail:
vyos@vyos:~$ show dhcpv6 server leases
Traceback (most recent call last):
File "/usr/libexec/vyos/op_mode/show_dhcpv6.py", line 81, in <module>
leases = get_leases(lease_file, state='active')
File "/usr/libexec/vyos/op_mode/show_dhcpv6.py", line 44, in get_leases
leases = IscDhcpLeases(lease_file).get()
File "/usr/lib/python3/dist-packages/isc_dhcp_leases/iscdhcpleases.py", line 110, in get
with open(self.filename) as lease_file:
FileNotFoundError: [Errno 2] No such file or directory: '/config/dhcpdv6.leases'
|
|
|
|
functions under it.
This is required for programs running outside a CLI session, like the future API daemon.
|
|
The merge config script restores the ability to restrict changes to a
specified path. In the initial implementation, the path was checked for
validity only with respect to the effective config; fix to allow valid
paths from merge config as well.
|
|
|
|
The ouput of config.show_config (cli-shell-api showConfig) does not
escape backslashes, whereas configtree expects escaped backslashes.
Values containing unescaped backslashes consequently lead to a parsing
error; cf. T1001.
|
|
|
