- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 25 2024
Jul 18 2024
Jul 17 2024
This actually causes Kernel Panics during boot, so lets remove this option again.
Jul 7 2024
There are two possible places where encrypted DNS support might be desired in a standard setup where VyOS is hosting a local resolver/recursor:
Jul 3 2024
Seems to work well enough in 1.4.0. If any issues turn up, we'll make separate tasks.
Jul 2 2024
Should fix it https://github.com/vyos/vyos-1x/pull/3747
Jul 1 2024
Jun 28 2024
Jun 27 2024
Jun 26 2024
Jun 25 2024
Should this ticket be closed? I see the PRs were merged more than a month ago.
Jun 24 2024
Jun 21 2024
Created PR https://github.com/vyos/vyos-1x/pull/3698
Jun 20 2024
Jun 18 2024
Suspend/Resume is not supported operation
Note for myself:
Logs from VM:
I've modified the protocol ospf settings to check if it will affect static routing or not.
The static routing are not affected (still no route to 0.0.0.0/0):
Hi!
Recently I've note that this bug is not affects only protocol failover, but also protocol static routers.
Jun 17 2024
all work!
Thank you
@pavel-altair can you please re-test with VyOS 1.5-rolling-202406170021
Jun 16 2024
Jun 15 2024
@c-po, can you see if it's still actual, and if not, close it
Thanks!
I've created a PR for this: https://github.com/vyos/vyos-1x/pull/3655
I've created a PR with a very simple fix: https://github.com/vyos/vyos-1x/pull/3654
Jun 14 2024
I can now reproduce the issue. The reason I was unable to reproduce this was I missed out that you use an ACME certificate
vyos@vyos:~$ generate ipsec profile windows-remote-access support remote ipsec.somedomain Traceback (most recent call last): File "/usr/libexec/vyos/op_mode/ikev2_profile_generator.py", line 153, in <module> cert_data = load_certificate(pki['certificate'][cert_name]['certificate']) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^ KeyError: 'certificate' vyos@vyos:~$ show ver | match Version: Version: VyOS 1.5-rolling-202406130020 vyos@vyos:~$
Jun 13 2024
This is not the latest image. Please use 1.5-rolling-202406130020
The only reason I see why this can happen is that the config.boot format can be unexpected. But this should not happen anymore, because now Cloud-init always runs migrations before doing any work, which should always add required metadata if the original file is a valid VyOS config.