Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
message
|
|
rename t0 to drift
add subnemu for 2fa to make it more readable
|
|
|
|
Commit 9f20bee81c ("T1376: improve show_dhcp and show_dhcpv6") added the tab
completion helper to list the availbale IP pools to query. This was done by
calling a python script which then called cli-shell-api which resulted in a
penalty by the Python interpreter startup.
This can be solved by directly using the cli-shell-api wrapper available
as <path> in op-mode - as also seen for DHCPv6.
|
|
|
|
|
|
This makes understanding the code easier what is "really" called without
opening the man page.
|
|
(cherry picked from commit b4b2c91127289c7b62afb24304054d57357a48c5)
|
|
The current command to restart any of the FRR processes is:
vyos@vyos:~$ restart frr
Possible completions:
<Enter> Execute the current command
bfdd Restart Bidirectional Forwarding Detection daemon
bgpd Restart Border Gateway Protocol daemon
ospf6d Restart OSPFv3 daemon
ospfd Restart OSPFv2 daemon
ripd Restart Routing Information Protocol daemon
ripngd Restart RIPng daemon
staticd Restart Static Route daemon
zebra Restart IP routing manager daemon
From a real-life example: Two engineers needed 5 minutes to figure it is under
"restart frr" - that is why this commit drops the artificial "frr" level on the
op-mode commands to restart routing protocol daemons.
It's less intuitive to have "restart frr ospfd" or "restart frr bgpd" compared
to "restart ospf" and "restart bgp" - we have the same for "restart ssh" or
"restart snmp" and not "restart openssh sshd".
This commit also drops the d (daemon) suffix of the op-mode comamands so the
commands align with the VyOS CLI, else there would be a miss-understanding from
ospf6d to ospfv3.
(cherry picked from commit 8ad8b0d51bf21c583e6d687576cb1a61195e7215)
|
|
|
|
Commit a30d74f4 (container: op-mode: T3765: add "connect container mysql-server")
added a CLI op-mode command to attach to a container - users typically not want
to attach and consume stdout (can be done via logs) but rather wan't to debug
inside the container image.
vyos@vyos:~$ connect container unifi
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 202 0.0 0.0 4640 828 pts/1 Ss 21:06 0:00 /bin/sh
root 203 0.0 0.0 34416 2872 pts/1 R+ 21:06 0:00 \_ ps faux
root 187 0.0 0.0 18388 3124 ? S 21:03 0:00 /bin/bash
root 186 0.0 0.0 4640 788 ? S 21:03 0:00 /bin/sh
root 185 0.0 0.0 4640 824 ? S 21:03 0:00 /bin/sh
root 184 0.0 0.0 4640 836 ? S 21:03 0:00 /bin/sh
root 1 0.0 0.0 18520 3228 pts/0 Ss+ 20:50 0:00 bash /usr/local/bin/docker-entrypoint.sh unifi
root 12 4.8 14.2 3688080 572756 pts/0 Sl+ 20:50 0:48 java -Dunifi.datadir=/unifi/data -Dunifi.logdir=/unifi/log -Dunifi.rundir=/var/run/unifi -
root 35 0.7 3.4 1102700 139752 pts/0 Sl+ 20:50 0:07 \_ bin/mongod --dbpath /usr/lib/unifi/data/db --port 27117 --unixSocketPrefix /usr/lib/un
Linux 57c689f739ed 5.10.60-amd64-vyos #1 SMP Fri Aug 20 14:44:59 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
|
|
|
|
|
|
|
|
|
|
|
|
That nasty workaround to always specify the same value for the node.def file
as the help text is no longer necessary after commit 17b5ac14 ("T3165: op-mode:
prevent override of populated node.def file with empty content".
The redundant definitions are no longer necessary.
|
|
|
|
|
|
container.xml.in file
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Triggers the same code as "generate pki wireguard key-pair" which makes it easier
for users switching from 1.3 -> 1.4.
|
|
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
|
|
|
|
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=
|
|
|
|
|
|
|
|
|
|
generate ipsec mac-ios-profile <connection> remote <ip|fqdn>
will generate a matching IPSec profile which can be loaded on an iOS device.
|