This is working again in VyOS 1.2.3 GA. I have tested both the simple configuration mentioned above and my actual configuration with a bunch of BGP peers. Thank you very much!

@sunser Did you try: set interfaces ethernet eth1 vif <vlanid> ... already?

https://phabricator.vyos.net/T1635 needs to be done first

yes, you need to be either able to resolve your endpoints name or have it in /etc/hosts mapped. The name is being resolved (or tried) when the wg command configures the tunnel. There is unfortunately not too much I can do against, unless implementing a probe service or something like that ( could be as simple as ping).

PR #142

Agreed, I'm going to workaround with set system sysctl custom, but also submit a PR: https://github.com/vyos/vyatta-cfg-system/pull/107

Guess? Wireguard coming up before vyos-hostsd?

\h is the short hostname, I thought we want to have the full one (\H)

@maznu , you can also set this manually set system sysctl custom net.ipv6.route.max_size value 143360, but seems default value is really small.

Sorry for duplicate, after T1531 seems this feature broken.
Proposed solution: change for vbash PS1='${debian_chroot:+($debian_chroot)}\u@\H:\w\$ ' to PS1='${debian_chroot:+($debian_chroot)}\u@$(hostname -f):\w\$ '

…or, indeed, it'd be great to be able to restart FRR and have it get a new config when this happened just now:

It seems like this isn't needed anymore, as the test was deleted: https://phabricator.vyos.net/rVYOSONEX6ac5271e93d06712f6e318d2f6b96280ae16f040

Duplicate of T1310. It worked in 1.2.2 but its not working as expected in 1.2.3 after using vyos-hostsd

As VyOS 1.2 rolling and also the upcoming VyOS 1.3 will use OpenVPN 2.4 (b/c Debian Buster ships OpenVPN 2.4.7) the workaround should work for quiet some time! Thanks for pointing this out.

@alainlamar as you seem to be the VyOS Wireless expert, you know why we have VLAN support on it?

sorry, but their licensing model incompatible with what we do.

ZeroTier was added to the Ubiquiti EdgeRouter (which runs a vyatta fork) as a demo. Relevant to this thread:
https://blog.kruyt.org/zerotier-on-edgerouter-p2/

Yes, this _was_ still a problem but the workaround solves the issue for
me. I've been able to upgrade the 1.1.8 instances to 1.2.3 after adding
this extra interface route.

Pull request created: https://github.com/vyos/vyos-1x/pull/141

Pull request created: https://github.com/vyos/vyos-1x/pull/140

Been pretty busy lately, but ran a quick test tonight. Wireguard keys are properly moved in my VM.

https://github.com/vyos/vyos-1x/commit/9b55f7c7b9ecc49e6efe075ad24a54baff719e8e

https://github.com/vyos/vyos-1x/commit/6956bfe0620638adbad36f8cdf6d312884ba82ff
https://github.com/vyos/vyos-1x/commit/0c6faf26823fb984b3e0a77ee014e20661163e44