I think this ticket can now be closed now that it has been merged.

https://github.com/vyos/vyos-1x/pull/4843

https://github.com/vyos/vyos-1x/pull/4842

wdctl can be used to check for the presence of a watchdog. Note if the watchdog isn't being managed via systemd (or similar) it will be kept alive by a kernel watchdog process.

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

Been testing, driver module loading is not always automatic. It is likely best to allow an option to specify the module to load. The vyos config syntax could likely be based this https://github.com/vyos-legacy/vyatta-watchdog/blob/current/README.md

From my experience having systemd manage the watchdog has been very stable.
I would not recommend using using watchdogd to manage the hardware watchdog, it is ancient and doesn't integrate well with systemd.

In T5192#162346, @c-po wrote:

RNDIS is once more on the "removal" list of the Linux Kernel.
https://www.phoronix.com/news/Linux-Disabling-RNDIS-Drivers

We should not bet on this feature that's why it will be disabled in 1.5 and 1.4 releases

I think there is a similar issue for wireguard static routes. In 1.5-rolling-202412310006 the routes are not being added. Works fine in older releases.

OMG. I just spent hours trying to diagnose why I was getting Sending reply: error_code 1 with output "error". The logging really needs to be improved.

The fix has now been merged.

It appears the udev rule was originally based on https://github.com/systemd/systemd/blob/main/rules.d/60-serial.rules#L12 which has the correct rule per this PR, as mentioned above the rule was broken in https://github.com/vyos/vyos-1x/commit/fa07bc3b87be142572124a2ce5c077cb42272418

https://github.com/vyos/vyos-1x/pull/4264