User Details
- User Since
- Jan 1 2022, 7:33 PM (120 w, 4 d)
Feb 13 2024
I believe it was an issue with my DNS server. Nevertheless, the issue cannot be reproduced so the bug report can be closed.
Sep 5 2023
@n.fort
Nope, no VRF set up.
@Viacheslav
I will check it today or tomorrow. But I believe I know the culprit, the new firewall rules didn't allow my VyOS instance to contact the CoreDNS (set to host mode) container that is hosted as a container in VyOS. I was unable to ping 127.0.0.1 as well as all of my VyOS's IP addresses.
Aug 15 2023
Apr 30 2023
If I pre-load my zone firewall with the new interface format (pod-$containerName) and upgrade to vyos-1.4-rolling-202304290647, it seems to upgrade seamlessly
Apr 29 2023
Dec 15 2022
Certbot (specifically certbot/dns-cloudflare container) is another situation where a command & argument is required. Currently, I get around it by running a task-schedule to run the podman command directly (its a task because the container runs to completion). But having a way to do this via VyOS CLI would be extra helpful.
Dec 7 2022
I can confirm the firewall errors are fixed in the newest rolling VyOS 1.4-rolling-202212070318
Dec 6 2022
Oct 24 2022
A simple work around could be to trigger a podman start command when a restart container $CONTAINER_NAME is entered. If the pod isnt already running or in a stopped state, it will look at the config and start it up.
Mar 11 2022
You are correct, my config is not correct.
Mar 8 2022
Jan 3 2022
I was able to test and get a screenshot of the exact error eapol spits out when using certstore as well.