PR https://github.com/vyos/vyos-1x/pull/981
vyos@r4-1.3# set interfaces ethernet eth0 ipv6 address eui64 2001:db8::/64
[edit]
vyos@r4-1.3# commit
ru[edit]
vyos@r4-1.3# run show int
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address S/L Description
--------- ---------- --- -----------
eth0 192.168.122.14/24 u/u
2001:db8::5054:ff:fe5d:4609/64Reproducible on my side, too.
To fix the bug :
How does e.g. syslog-ng behave?
This is a typo in the documentation. In the real system, the facility is called security, but it is deprecated at least from the 2004 year.
The problem that I see in names is that it seems that different systems and software may use slightly different names for facilities. So, could be a good idea to do the two things:
Once i dropped that repo everything started to work again... and while it may be a temporary thing, i think that this sort of illustrates the problem with reliance on external repos. Its probably safer to mirror their content into something that can be relied upon to stay live as companies are bought and sold all the time, resources vanish, and licenses change from real FOSS to semi-permissive .
I do have similar problems with a VyOS VM inside Proxmox.
I can not reproduce the issue for 1.4 and 1.3 release. Maybe a temporary image build issue with the upstream repositories.
Now the last part left is to add minisign signature verification to the add system image script. For now, we should keep the old GPG verification code just in case someone wants to downgrade, or if we have to re-introduce GPG signatures for whatever reason.