I use conntrack-sync at home between my two Vyos routers, this gives great failover and all my sessions just keep working. I love it, it's a great Vyos feature.
I recently realised however that the multicast traffic it uses was also forwarding onto my Wireless APs creating a lot of unnecessary multicast traffic. So I moved to using the Unicast (UDP) conntrack-sync feature, which works just as well.
The problem is, if I reboot my router, the mcast config re-appears in the configuration.
Example:
[email protected]:~$ show configuration commands | match mcast [email protected]:~$ reboot Are you sure you want to reboot this system? [y/N] y Connection to ferrari-sec.muppetz.com closed by remote host. Connection to ferrari-sec.muppetz.com closed. {13:08}~ ➭ fb Welcome to VyOS The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri Nov 20 13:07:11 2020 from radio.muppetz.com [email protected]:~$ show configuration commands | match mcast set service conntrack-sync mcast-group '225.0.0.50'
You can see that after the reboot, the mcast-group command has re-appeared in the config.
The whole conntrack-sync config now looks like:
[email protected]:~$ show configuration commands | match conntrack-sync set service conntrack-sync accept-protocol 'tcp,udp,icmp' set service conntrack-sync disable-external-cache set service conntrack-sync event-listen-queue-size '8' set service conntrack-sync expect-sync 'all' set service conntrack-sync failover-mechanism vrrp sync-group 'failover-group' set service conntrack-sync interface eth1 peer '192.168.0.250' set service conntrack-sync mcast-group '225.0.0.50' set service conntrack-sync sync-queue-size '8'
Conntrack sync is still using the UDP peer:
[email protected]:~$ show conntrack-sync statistics <snip snip> UDP traffic (active device=eth1): 57392 Bytes sent 3981432 Bytes recv 1359 Pckts sent 49281 Pckts recv 0 Error send 0 Error recv
so it appears that the bug is mostly cosmetic.
However, I don't think rebooting the router should cause additional lines of configuration to be added to the router.
Thanks!