Turns out that 'destination-interface any' works, and I just hadn't read the help.

• trafficserver (buster native - 19.7 MB of additional disk space will be used)
• looks like squidguard can't be integrated (removing it entirely?)

fixed in https://downloads.vyos.io/rolling/current/amd64/vyos-1.3-rolling-202001211723-amd64.iso.

If this is always enabled "hardcoded" and SNMPd is not running the following will happen:

https://phabricator.vyos.net/T1977

I've created a PR in the vyos/vyos-1x repy for the config verification fix: https://github.com/vyos/vyos-1x/pull/208

I've created a PR in the vyos/vyos-documentation repo for the documentation fix: https://github.com/vyos/vyos-documentation/pull/190

This was only a problem in rolling and is fixed

Many thanks again, I much prefer having interface specific settings in a single place instead of arbitrary script locations.

PR for this fix: https://github.com/vyos/vyatta-cfg/pull/20

@bbs2web you can try use sysctl params from set

This is working nicely, many thanks!

I've attached a simple patch to expose FRRouting's built-in capability of being able to set a prefix's local administrative distance to VyOS.

I've attached a simple patch to expose FRRouting's built-in capability of being able to match on prefix's BGP local preference to VyOS.

I like the idea, but unfortunately I do not understand why there needs to be a cancel node? If maintenance mode is not activated shouldnt this be enough?

FRR build triggered, please try next rolli g

No, work would be needed to add the necessary logic to VyOS scripts.
This wasn't possible before the version of isc-dhcpd VyOS uses was
updated to one that supported PD length. But now it is at least
possible, before it wasn't possible at all.

With the above change, some 2 years later, are we able to finally use a DHCP PD for IPv6? ie does it actually work?

Ack, I have already after step 5 an issue. The uids shouldn't be an issue, since the users should be all in the same group and the group has r/w permissions.

I hacked through how to reproduce.

@kroy Can you please test with the latest rolling? I can't reproduce the issue.

@max1e6 Did you have a chance to test?

PR https://github.com/vyos/vyatta-cfg-quagga/pull/40 also need add script migration

set protocols bgp 65535 neighbor 192.168.255.10 enforce-first-as

Look like FRR changes commands for this feature, now this option per neighbour.

https://github.com/vyos/vyos-1x/commit/742da889afa4375d5b6cb98dada7f2d3ec2f0326
@Xesxen http://dev.packages.vyos.net/repositories/current/pool/main/v/vyos-1x/vyos-1x_1.3.0-16_all.deb addresses that issue for the rolling release.

We took other steps that allows us to take the image back to a manageable size, and this task lost its immediate relevance.

@jestabro yup, go ahead please and let me know when I can close it or if you can you can close as well.

Yes, thanks, c-po; the revised settings (above) are consistent with defaults and behaviour for both crux and equuleus.

Issue looks to be fixed in rolling version you've stated. Reboot now immediate without any hang. Thanks.

I propose in this case use set vpn l2tp remote-access outside-address 0.0.0.0. It works in current rolling.

As I recently rewrote this part in XML/Python please also check the default values in the Python script

This should be restricted by a regex

@kroy I tried just now with vyos-1.3-rolling-202001160217 in UEFI mode (even forced UEFI boot only in the BIOS to make sure) and am still having the same problem.

I will backport this, unless objections ...

For consistency with the relative sizes set by CLI in the conf_mode script (system-ip.py), the default params should be:

The size of an ARP cache entry is 384 bytes (x86-64), so the change will add ~720k -- ~3 MiB, which seems reasonable. I will add the suggested settings to sysctl defaults.

Works in 1.3-rolling-202001150217, propose cherry-pick in to crux.

Resolved in 1.3-rolling-202001150217

Copy failed too.