- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Dec 6 2023
Dec 5 2023
Dec 4 2023
tested on 1.5/1.4 :
Dec 3 2023
Added PR for documentation here https://github.com/vyos/vyos-documentation/pull/1169
PR for 1.4 https://github.com/vyos/vyos-1x/pull/2568
Wouldnt this break things with compatibility with other vendors?
Dec 2 2023
PR 1.5/1.4 : https://github.com/vyos/vyos-1x/pull/2564
@Viacheslav, updated PR https://github.com/vyos/vyos-1x/pull/2562
Looks like, we still need to keep /etc/avahi/services because avahi-daemon chroot to that location at startup. This is set up at build time via AVAHI_CONFIG_DIR and there is no way to change it at runtime.
Cannot pass smoketest, @indrajitr could you re-check?
DEBUG - Running Testcase: /usr/libexec/vyos/tests/smoke/cli/test_service_mdns-repeater.py
DEBUG - test_service_dual_stack (__main__.TestServiceMDNSrepeater.test_service_dual_stack) ... FAIL
DEBUG - test_service_ipv4 (__main__.TestServiceMDNSrepeater.test_service_ipv4) ... FAIL
DEBUG - test_service_ipv6 (__main__.TestServiceMDNSrepeater.test_service_ipv6) ... FAIL
DEBUG -
DEBUG - ======================================================================
DEBUG - FAIL: test_service_dual_stack (__main__.TestServiceMDNSrepeater.test_service_dual_stack)
DEBUG - ----------------------------------------------------------------------
DEBUG - Traceback (most recent call last):
DEBUG - File "/usr/libexec/vyos/tests/smoke/cli/test_service_mdns-repeater.py", line 47, in tearDown
DEBUG - self.assertTrue(process_named_running('avahi-daemon'))
DEBUG - AssertionError: None is not true
DEBUG -
DEBUG - ======================================================================
DEBUG - FAIL: test_service_ipv4 (__main__.TestServiceMDNSrepeater.test_service_ipv4)
DEBUG - ----------------------------------------------------------------------
DEBUG - Traceback (most recent call last):
DEBUG - File "/usr/libexec/vyos/tests/smoke/cli/test_service_mdns-repeater.py", line 47, in tearDown
DEBUG - self.assertTrue(process_named_running('avahi-daemon'))
DEBUG - AssertionError: None is not true
DEBUG -
DEBUG - ======================================================================
DEBUG - FAIL: test_service_ipv6 (__main__.TestServiceMDNSrepeater.test_service_ipv6)
DEBUG - ----------------------------------------------------------------------
DEBUG - Traceback (most recent call last):
DEBUG - File "/usr/libexec/vyos/tests/smoke/cli/test_service_mdns-repeater.py", line 47, in tearDown
DEBUG - self.assertTrue(process_named_running('avahi-daemon'))
DEBUG - AssertionError: None is not true
DEBUG -
DEBUG - ----------------------------------------------------------------------
DEBUG - Ran 3 tests in 11.145s
DEBUG -
DEBUG - FAILED (failures=3)Dec 1 2023
Nov 30 2023
Tested in VyOS 1.3.4
Tested in VyOS 1.4-rolling-202311100309
Nov 29 2023
currently OSPF smoketests fail b/c of https://github.com/FRRouting/frr/issues/14910
Good day
Tested in VyOS 1.4-rolling-202311100309
Nov 28 2023
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
Nov 27 2023
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.
Nov 26 2023
PR for 1.5 https://github.com/vyos/vyos-1x/pull/2544
