Using 1.2-rolling-201908171107 I configured:

set service dns forwarding domain example.com server '172.16.10.1'
set service dns forwarding listen-address '172.18.201.10'
set service dns forwarding name-server '1.1.1.1'

1. OpenVPN site-to-site

This error won't be fixed as the new Python/XML implementation of OpenVPN has been merged into current and will appear in the next rolling release.

This is actually invalid. There is no way with the current CLI design to specify the local address node with an optional subnet-mask leaf node.

Hello Harliff,

We also can add show protocols bfd peer counters and for peer show protocols bfd peer x.x.x.x counters

vyos@vyos-rtr01# run show protocols bfd peer counters | strip-private 
BFD Peers:
	peer xxx.xxx.0.4 local-address xxx.xxx.0.1 vrf default
		Control packet input: 0 packets
		Control packet output: 988 packets
		Echo packet input: 0 packets
		Echo packet output: 0 packets
		Session up events: 0
		Session down events: 0
		Zebra notifications: 0

A note when stating to convert physical interfaces.

I've made some hacks to get vyatta-config-sync working with ssh-keys (and working at all).

Please keep this in mind when rewriting dummy/loopback interfaces: https://phabricator.vyos.net/T1467

@c-po
I have some new findings. When I upgrade to a new rolling release (tested with the one from 11.08.2019 and 12.08.2019), I do 'add system image ...', then reboot, then the forwarders are missing in recursor.conf:

Hi Donny,

Not sure if you're still looking into this, but the following script works perfectly for me on the crux branch:

https://vyos.readthedocs.io/en/equuleus/contributing/vyos-api/interface-config.html#interface-config
https://vyos.readthedocs.io/en/latest/contributing/vyos-api/interface-config.html

I have added two PRs with some fixes and new features. The most valuable changes:

• Fixed the bug, which prevents to change or delete BFD peers with custom options. For example, when any of source address/interface, multihop was used, such peers could not be deleted or changed.
• Added configuration checks, which should prevent adding BFD option to BGP neighbors or peer-groups without corresponding peers configuration in protocols bfd. If BGP and BFD configurations are out of sync, BGP sessions could be very unstable.
• Added configuration check, which should prevent to delete peers from protocols bfd if they are still used in BGP.
• Some other small fixes and changes.

Also, was added several new options:
BFD configuration:

set protocols bfd peer IP echo-mode
set protocols bfd peer IP interval echo-interval

BGP configuration:

set protocols bgp ASN neighbor IP bfd check-control-plane-failure

I cannot reproduce this issue on VyOS 1.2.0-rolling+201908050337. @OlegGardash can you try on last rolling release?

Is this still an issue?

Most of these files are autogenerated and dont need to be saved across reboots.. is it possible to make them in a overlay that does not save to disk? Or another aproach is to just delete them when the device starts (before or when vyatta starts)

https://github.com/vyos/vyos-1x/commit/d96cfc8a5b1e9f9a3484a4c4036dddabfc588f5b
While documentation is on its way, below is a very small example on how to use it:

https://www.freedesktop.org/software/systemd/man/systemd.network.html

dhcp can be done via systemd or the traditional isc-dhcp client, which way should we go? systemd.networkd does link detection too and stops dhcp if the link is lost and starts it again when the link returns to state up.

@Dmitry PR merged in, you can test it in the next rolling tomorrow.

PR 98
added next commands for ipv6 configuration

I have almost all requested stuff implemented, plus some more like setting mtu, mac address etc. I'm planning to include that into vyos-1x after testing.

I'd like to make it more generic anyway, so basically it will be come a wrapper for the ip commands plus some check/find function maybe (like what mac belongs to what interface, bonding etc).