I’m using VyOS now for an L2TPv3 tunnel between two remote sites at work.
The first router (VM under ESXi 6.5) works perfectly.
The second router, which has been installed on a PC, can’t get to load the full configuration after reboot (the part lacking is the L2TPv3 configuration). They both have the same version.
Strangely, when I issue “load”, the router gets the full configuration loaded and asks for commit! So I guess the configuration file is OK. Yet VyOS can’t load it properly after reboot.
I tried to reinstall but I had exactly the same issue. My Hardware is a Dell OptiPlex 3050. (I don’t have other machines to test on).
Version is :
vyos@vyos:~$ sh ver
Version: VyOS 1.2.0-rolling+201904240337
Built by: autobuild@vyos.net
Built on: Wed 24 Apr 2019 03:37 UTC
Build ID: c1c591e5-9a85-4d91-8051-9e01e7f0176a
Architecture: x86_64
Boot via: installed image
System type: bare metal
Hardware vendor: Dell Inc.
Hardware model: OptiPlex 3050
Hardware S/N: Unknown
Hardware UUID: Unknown
Copyright: VyOS maintainers and contributors
Does anyone know how to debug or eventually tweak the way VyOS saves/loads its configuration ? is this a known issue ?
Can you share your config please?
Of course 
vyos@vyos:~$ sh config
interfaces {
bridge br0 {
aging 300
hello-time 2
max-age 20
priority 0
stp false
}
ethernet eth0 {
address dhcp
duplex auto
hw-id c4:12:f5:33:e5:e2
smp-affinity auto
speed auto
}
ethernet eth1 {
bridge-group {
bridge br0
}
duplex auto
hw-id 8c:ec:4b:45:ee:68
smp-affinity auto
speed auto
}
l2tpv3 l2tpeth0 {
bridge-group {
bridge br0
}
destination-port 10000
encapsulation ip
local-ip 10.1.11.67
peer-session-id 1
peer-tunnel-id 1
remote-ip 192.168.170.20
session-id 1
source-port 10000
tunnel-id 1
}
loopback lo {
}
}
protocols {
static {
route 0.0.0.0/0 {
next-hop 10.1.11.254 {
}
}
}
}
service {
ssh {
}
}
system {
config-management {
commit-revisions 100
}
console {
device ttyS0 {
speed 9600
}
}
host-name vyos
login {
user vyos {
authentication {
encrypted-password ****************
plaintext-password ****************
}
level admin
}
}
ntp {
server 0.pool.ntp.org {
}
server 1.pool.ntp.org {
}
server 2.pool.ntp.org {
}
}
syslog {
global {
facility all {
level info
}
facility protocols {
level debug
}
}
}
time-zone UTC
}
vyos@vyos:~$
can you please do it via ‘show config comm’. Easier to copy and test.
I think you don’t have an IP address by the time l2tp is supposed to start. Can you try it with static IPs?
Bingo! that should be it! I just used a static ip address and everything worked fine!
By the way I should have thought of this. Thanks a lot for your help!!