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

currently OSPF smoketests fail b/c of https://github.com/FRRouting/frr/issues/14910

Good day

Tested in VyOS 1.4-rolling-202311100309

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

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

Tested on VyOS 1.4-rolling-202311100309

• IKEv1
• 2 proposals
• the pfs is enabled

You can use GraphQL query. It shows you what does container.py for raw format

set service https api graphql
set service https api keys id KID key 'foo'

Query

curl -k --raw 'https://localhost/graphql' \
    -H 'Content-Type: application/json' \
    -d '{"query":" { ShowImageContainer (data: {key: \"foo\"}) {\n  success\n  errors\n  data {\n    result\n  }\n}\n}\n"}'

For example

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

https://github.com/FRRouting/frr/pull/14887

Seems like it's the same for the other functions
sudo podman ps --all vs. sudo podman ps --all --format='{{json .}}'
sudo podman network ls vs. sudo podman network ls --format='{{json .}}'

The implementation in file container.py has the command podman image ls which is ok when called from shell.
When called from API it should have been podman image ls --format='{{json .}}'

Seems like I was wrong, the content is returned but not in structured json format.
For further automation it would be nice to have json objects instead of a string which needs to be parsed by the client.

Great addition, it has one minor bug.

The problem is that, comparing to command output on 1.3, it only show the leases granted by the router (and doesn't contain leases granted by the second router, regardless of states primary|secondary.
So user might think synchronization between routers defined in fail-over mode is broken.
But this is not the case. As explained in the description, all information about leases, granted by both routers, is present on lease files on both routers.

PR for 1.5 https://github.com/vyos/vyos-1x/pull/2544

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