Code commit here: https://github.com/sskaje/vyos-1x/tree/T4930

This should be fixed by

@sdwilsh Are you good to close this out? The change in ipv6 should be handled by the updated version now in main

On hold befor the time we rework the op mode system not to use the old Vyatta's code at all

Tried to apply multi_to_list function to ConfigTree().to_json() but it works only for the full config or if pass the path.
The problem is described in the comment on closing the pull request: link. For now there is no way to pass the argument before the filter (json) to the function after the filter

Yes, I linked the article for background why the MTU setting is helpful, this applies to Podman as well as Docker.

We use podman for containers.
Eq command for the podman:

vyos@r14:~$ sudo podman network create pod-net2 --opt mtu=1200
pod-net2
vyos@r14:~$

Check:

vyos@r14:~$ sudo podman network inspect pod-net2
[
     {
          "name": "pod-net2",
          "id": "f1ec367ee95ee0f5b644b7fb96faffa6cf499490e3ff5e8f3915182639302cc7",
          "driver": "bridge",
          "network_interface": "podman1",
          "created": "2024-11-18T10:08:28.26831792Z",
          "subnets": [
               {
                    "subnet": "10.89.0.0/24",
                    "gateway": "10.89.0.1"
               }
          ],
          "ipv6_enabled": false,
          "internal": false,
          "dns_enabled": true,
          "options": {
               "mtu": "1200"
          },
          "ipam_options": {
               "driver": "host-local"
          }
     }
]
vyos@r14:~$

Since Ipsec secrets al already maintaned in Json config that handle correctly quoting
Is still possible relax the check on the " (double quotes) and let him be saved and commited.
The check is also in commiting phase
I.e.

@rob, we may need a bit of help with this from you

I was looking for this too, and actually started to play with the code of the module to get this feature in a few weeks ago. I've submitted my changes as a draft PR on Github. I've been playing with managing my VyOS config from SCM for my home lab. It's important when I for example remove a firewall rule, it is also deleted in the running config, instead of being orphaned. It seems to work pretty well in my setup, but I am uncertain if nothing breaks in other workflows.

Ready for review.

I've got a fix for this in the works.

For support requests, use forum.vyos.io

Use forum.vyos.io for support requests

When trying to make a non-working peer via the command reset vpn ipsec site-to-site peer RIGHT
Gives an error

PR https://github.com/vyos/vyos-build/pull/839

As covered in last comment, all matters have been addressed, but for (then) open question re firewall migration. If that recurs, or still present, we will open a specific task.

As discussed a workaround is available, and preferable to the danger over usefulness of backporting to 1.3.x.

Adding that the long standing issue in T6543 is being addressed in the work of T6718, which provides a replacement to legacy loadConfig; the legacy code will not be corrected.

The only piece remaining here is a backport for Equuleus.

The specific high priority issue here was addressed in T6131; the general question of support for ZeroTier is in T6455. Closing this task as stated.

This will have a simple solution as a corollary of the work T6718: put on hold for now, pending restatement in terms of that work.