If someone can confirm I'm linking to the correct github repo (there are two cloud init ones under vyos), I could submit a pull request for this. @syncer, @Unicron?

cf. T1001 as a related issue:

So testing done so far:

The real problem is the config parser it seems as it can not deal with special characters used in a pre-login banner.

PR #158 https://github.com/vyos/vyos-1x/pull/158

Confirmed fixed in

vyos@mke-fw1:~$ show version
Version:          VyOS 1.2-rolling-201911051339
Built by:         [email protected]
Built on:         Tue 05 Nov 2019 13:39 UTC
Build UUID:       3863567b-039d-4fdd-90cc-eda2e1b11bc6
Build Commit ID:  33c865b2ada281

Ah you were using bleeding edge equuleus builds. Ddclient 3.9.0 has been added to recent rolling image.

In 1.2.3 build this error does not appear and it seems to work correctly

Upgraded to 1.3-rolling-201911041446 and the config file issue is still present.

After adding the missing command set high-availability vrrp sync-group sync member int1, we have a new error when starting conntrackd

Confirmed using a copy of the Hyper-V VM

ppp0 not renaming to pppoe0 on 1.8.0 https://community.ui.com/questions/ppp0-not-renaming-to-pppoe0-on-1-8-0/b4aeea88-5d52-4222-b065-e6903afdda9a

600MB

that's really strange. As I can reproduce the problem on both intances in 100% of the cases. But not the same config and not the same inital VyOS version.
Can I do some troubleshooting steps for you?
I can also give you the vhd, but on a private channel if possible (is it possible on slack?)

This is weird. I can not reproduce it either with VMWare vSpher enot using Hyper-V.

1vCPU, 512MB RAM

What is your VMs CPU/RAM configuration?

Well, then there is a bug in the interface renaming script with later ifupdown scripts which should be fixed.

No good I'm afraid. NAT is not working set to pppoe0 and is still offering ppp0.

the interface name ppp0 is wrong. If we configure it to be pppoe0 on the CLI it should also have this name on the bare linux system. This sounds a bit like: T1242 which was fixed in commit https://github.com/vyos/vyatta-cfg-op-pppoe/commit/4330d41fcda30553ca1b3e2588d05eebdd59fc80

Interface doesn't work if changed to ppp0. The interface seems to expect pppoe0 and everything else seems to expect ppp0. pppoe0 is still showing as 'coming up', even though everything seems to be working

More info,

You have to add a sync-group.
set high-availability vrrp sync-group intgroup member int1
set service conntrack-sync failover-mechanism vrrp sync-group intgroup

After a bit of fiddling, I have found the problem. The config.boot conversion from 1.2 to 1.3 did not chnage the NAT interface entries from pppoe0 to ppp0. Once changed, all is working. As can be seen below, NAT & monitor traffic interface expect ppp0, whilst the actual interface and firewall zones expect pppoe0. I think this is a little confusing and should probably be made consistent one way or the other.. pppoe0: is also still showing as "Coming up" even though everything appears to work so there is still a reporting problem there at the very least.

Wait, Argo tunnel uses Cloudflare's WARP VPN system, which under the hood is basically wireguard...

Confirmed still present in VyOS 1.3-rolling-201911030242

Tested using the below configuration on VyOS 1.2-rolling-201911030217

I've used the following script to get the argo tunnel running and encrypting dns, i then use 127.0.0.1 as the system nameserver and as the dns forwarder's only upstream nameserver. Works well so far but the integration is lacking with the vyos config

At first glance this looks like a very "easy" priority issue. Bonding interfaces are set up before the ethernet interfaces (makes no sense though).

@starcraft66 is it working as expected?

Hi, the routes are there.

As you pass auth and get the config sent, can you please check that you have a default route set up? Ideally that should happen automatically. It looks like your ISP offers you IPv6 which seems rejected as unknown by the pppoe client, but that't not the primary issue. Check if your default route is being set up.

Complete

To fix this inconsistancy the output of show int ethernet | json should be:

{
       "eth0": {
            "address": "10.10.10.10/24"
        }
}

PR #26 https://github.com/vyos/vyatta-cfg-vpn/pull/26

Merged to equuleus branch.

PR: https://github.com/vyos/vyos-1x/pull/156

The ddclient config file got moved to /etc/ddclient/ddclient.conf but ddclient is still trying to load /etc/ddclient.conf in the latest VyOS 1.3 rolling image.

PR #38