Fri, Apr 23
Looks good on 1.3-rolling-202104220921:
Mon, Apr 12
sudo journalctl -b
Apr 5 2021
Turns out this is not a VyOS limitation but is a Linux Kernel/iproute2 limitation.
Apr 2 2021
This can be reproduced with the following config on 1.4
Apr 1 2021
Mar 22 2021
@c-po, you cherry-picked the wrong commit: equuleus needs the fix from current, not crux.
Mar 20 2021
Service still with no description VyOS 1.3-beta-202103170443
Mar 18 2021
Mar 17 2021
This is still a problem, I have just upgraded from 1.2.6-S1 to 1.2.7-epa1 and had two conntrackd's running on the primary router.
Mar 15 2021
Waiting on backport to 1.3.
Mar 14 2021
Mar 11 2021
The same bug with 1.2.7-epa1
set interfaces dummy dum0 set interfaces ethernet eth1 address dhcp set load-balancing wan interface-health eth1 nexthop dhcp set load-balancing wan rule 1 inbound-interface dum0 set load-balancing wan rule 1 interface eth1 commit
email@example.com:~$ show wan-load-balance Interface: eth1 Status: active Last Status Change: Thu Mar 11 09:31:54 2021 +Test: ping Target: Last Interface Success: 0s Last Interface Failure: 2m35s # Interface Failure(s): 0
Fixed in VyOS 1.4-rolling-202103110218
set system syslog global facility all level 'info' set system syslog global facility protocols level 'debug' set system syslog host 192.168.122.1 facility all level 'all' set system syslog host 192.168.122.1 port '514' set system syslog host 2001:db8::2 facility all level 'all' set system syslog host 2001:db8::3 facility all level 'all' set system syslog host 2001:db8::3 port '514' set system syslog host 2001:db8::4 facility all level 'all' set system syslog host 2001:db8::4 port '514'
Mar 9 2021
PR for "current" https://github.com/vyos/vyos-1x/pull/764
Expected format @[2001:db8::2]:514
Mar 6 2021
For 1.2 this could be evaluated in the tunnels node.def file by something like: