VyOS 1.2.2 maintenance release is now available. Our customers and active contributors who have a subscription can download the images from the support portal, and everyone can also build it from the crux
branch of the vyos-build repository.
Cloud images are taking a bit longer to complete, but they also will be available in a couple of days. Images for Amazon EC2 and Microsoft Azure are already available.
We are also introducing VyOS on the Packet Cloud with this release.
There are now options for per-interface MSS clamping. For example:
set firewall options interface eth0 adjust-mss 1300
set firewall options interface eth0 adjust-mss6 1300
set protocols bgp 65535 neighbor 192.0.2.10 capability extended-nexthop
set protocols bgp 65535 parameters bestpath as-path multipath-relax
set protocols bgp 65535 neighbor 192.0.2.10 remote-as <internal|external>
set protocols bgp 64840 neighbor 192.0.2.10 interface [v6only] <remote-as ...|peer-group ...>
set protocols bgp 64800 neighbor 191.0.2.10 local-as 64800 no-prepend
set policy route-map Test rule 10 set community additive
set interfaces ethernet eth0 ipv6 ospfv3 network <broadcast|point-to-point>
Due to an oversight, VRRP scripts could not use arguments, so you couldn't easily reuse the same script in multiple groups. That's no longer the case. You can pass any arguments to those scripts now:
# show high-availability vrrp { group Test { health-check { script "/config/scripts/pinger.sh 192.0.2.100" } interface eth0 transition-script { backup "/config/scripts/vrrp-state.sh backup 192.0.2.10" master "/config/scripts/vrrp-state.sh master 192.0.2.10" } virtual-address 192.0.2.10/24 vrid 10 } }
The new config parser could originally be used only from OCaml and Python programs, but now its capabilities are also available to shell scripts through the vyos-config-file-query
utility.
If you want to add some kind of a custom initialization procedure, you can call your script in /config/scripts/vyos-preconfig-bootup.script. We are not aware of anyone doing that yet, but if you make something interesting, let us know.
vyos@vyos# /usr/bin/vyos-config-file-query --file /config/config.boot --return-value --path "system host-name" vyos vyos@vyos# /usr/bin/vyos-config-file-query --help usage: vyos-config-file-query [-h] -p PATH -f FILE [-s SEPARATOR] [-j] (--return-value | --return-values | --list-nodes | --exists) optional arguments: -h, --help show this help message and exit -p PATH, --path PATH VyOS config node, e.g. "system config-management commit-revisions" -f FILE, --file FILE VyOS config file, e.g. /config/config.boot -s SEPARATOR, --separator SEPARATOR Value separator for the plain format -j, --json --return-value Return a single node value --return-values Return all values of a multi-value node --list-nodes List children of a node --exists Check if a node exists
return_effective_values()
function now correctly returns a list rather than a string (T1505)