Age | Commit message (Collapse) | Author |
|
|
|
Commit 472c9568 ("isis: T3693: Adding IPv6 redistribution to ISIS") did not
pass rendering, am exception got thrown:
jinja2.exceptions.UndefinedError: 'dict object' has no attribute 'protocol'
This commit fixes the templateing code.
|
|
|
|
The class ConfigTreeActiveQuery uses configtree to access tag node
values; note that this will only report saved configuration data.
|
|
l2tpv3: T1594: Fix timeout before set l2tpv3 interface
|
|
|
|
In some cases, we need to wait until local address is assigned.
And only then l2tpv3 tunnel can be configured.
For example when ipv6 address is in "tentative" state
or we wait for some routing daemon/route for a remote address.
|
|
Add the following new commands:
* show bgp mac hash
* show bgp martian next-hop
* show bgp memory
* show bgp next-hop
* show bgp next-hop detail
* show bgp next-hop ip
* show bgp next-hop ip detail
* show bgp statistics
* show bgp statistics-all
* show bgp wide
* show bgp cidr-only
* show bgp cidr-only wide
* show bgp ipv4 wide
* show bgp ipv6 wide
|
|
|
|
isis: T3693: Adding IPv6 redistribution to ISIS
|
|
In this commit we add the ability to redistribute into
ISIS for IPv6 address family.
|
|
|
|
For more information see:
* https://programmersought.com/article/62242485344/
* https://www.spinics.net/lists/netdev/msg332453.html
* https://github.com/FRRouting/frr/blob/master/doc/user/Useful_Sysctl_Settings.md
|
|
Recommended by FRR best deafults
https://github.com/FRRouting/frr/blob/master/doc/user/Useful_Sysctl_Settings.md
|
|
bgp: T1176: Add solo option for neighbor
|
|
|
|
|
|
configd: T3694: always set script.argv
|
|
Commit f520182b ("vyos.util: add is_systemd_service_running() helper function")
added a new helper function that can be used to check if a systemd service is
running.
Drop all custom implementations in favor of this library call.
|
|
Test is a specified systemd service is actually running.
Returns True if service is running, false otherwise.
|
|
Several scripts imported by vyos-configd (including
src/conf_mode/protocols_static.py) rely on argv for operating on VRFs.
Always setting script.argv in src/services/vyos-configd ensures those
scripts will operate on the default VRF when called with no arguments.
Otherwise, a stale argv might cause those scripts to operate on the last
modified VRF instead of the default VRF.
|
|
|
|
dhcp-server: T2432: Run dhcpd in group vyattacfg to allow recreate le…
|
|
|
|
|
|
|
|
|
|
$ generate ipsec mac-ios-profile <connection> remote <ip>
|
|
The migrator from 20-to-21 is required as 19-to-20 on VyOS 1.3 - thus simply
rename/reorder the two migrators to not break things the hard way when
upgrading from 1.3 -> 1.4.
|
|
|
|
|
|
set vpn ipsec remote-access connection rw authentication client-mode 'eap-radius'
set vpn ipsec remote-access connection rw authentication id '192.0.2.1'
set vpn ipsec remote-access connection rw authentication server-mode 'x509'
set vpn ipsec remote-access connection rw authentication x509 ca-certificate 'CAcert_Class_3_Root'
set vpn ipsec remote-access connection rw authentication x509 certificate 'vyos'
set vpn ipsec remote-access connection rw esp-group 'ESP-RW'
set vpn ipsec remote-access connection rw ike-group 'IKE-RW'
set vpn ipsec remote-access connection rw local-address '192.0.2.1'
set vpn ipsec remote-access connection rw pool 'ra-rw-ipv4'
set vpn ipsec remote-access connection rw unique 'never'
set vpn ipsec remote-access pool ra-rw-ipv4 name-server '192.0.2.2'
set vpn ipsec remote-access pool ra-rw-ipv4 prefix '192.168.22.0/24'
set vpn ipsec remote-access radius nas-identifier 'fooo'
set vpn ipsec remote-access radius server 172.16.100.10 key 'secret'
|
|
|
|
As this is only related to remote-access, keeping it under "options" simply
feels wrong.
|
|
pki: T3642: Add ability to write generated certificates/keys to files
|
|
|
|
(cherry picked from commit 7292631373ea50f9908796ef2eda32e672d1df2e)
|
|
filenames
|
|
|
|
As the keys are now stored inside the CLI configuration and no longer in a file
on the filesystem, this command is no longer required.
Also there are dedicated CLI commands available to display the additional
Wireguard information.
- show interfaces wireguard wg10
- show interfaces wireguard wg10 summary
|
|
As the keys are now stored inside the CLI configuration and no longer in a file
on the filesystem, this command is no longer required.
|
|
As the keys are now stored inside the CLI configuration and no longer in
a file on the filesystem, this command is no longer required.
|
|
bridge: op-mode: T3698: Support bridge monitoring
|
|
Per interface public-key can now be retrieved via:
vyos@vyos:~$ show interfaces wireguard wg10 public-key
+XZr0oUjYRQuB/kcO1f+puOjKkiOWBG8eZX1Jpyq2n0=
|
|
|
|
|
|
Update/refresh of DNS records is now handled internally by Strongswan.
|
|
|
|
bridge: op-mode: T3667: Fix displaying members of a specific bridge interface
|
|
pki: https: T3642: Migrate HTTPS to use PKI configuration
|