User Details
- User Since
- Jan 8 2024, 5:46 PM (99 w, 3 d)
Yesterday
Thu, Nov 6
Nov 3 2025
Oct 31 2025
Oct 30 2025
Oct 29 2025
Oct 1 2025
Sep 30 2025
Sep 29 2025
Sep 28 2025
Sep 25 2025
vyos-1x PR: https://github.com/vyos/vyos-1x/pull/4752
Sep 22 2025
Sep 20 2025
vyos-build PR to add zerotier binary: https://github.com/vyos/vyos-build/pull/1041
Sep 19 2025
PR for fix: https://github.com/vyos/vyos-1x/pull/4733
Looks like all of the calls to the script for the reset-ip-bgp.xml.in file are wrong. I originally was making a dedicated reset_bgp.py script before just incorporating it into bgp.py. I must have forgot to update those. I'll make a PR to fix it.
Sep 18 2025
Sep 17 2025
A quick flyby review shows the number of lines of code could be reduced by quite a bit. This isn't conclusive for a direction one way or the other. Just informational. Less code does not necessarily equal better:
Sep 16 2025
Adding to this conversation. The one benefit to how things are currently being done is that changes to a single section (firewall, policy, conntrack, nat) just requires a simple delete of the entire table, then an atomic load of the updated config.
Sep 15 2025
Sep 13 2025
Sep 12 2025
Sep 11 2025
Sep 10 2025
Sep 9 2025
Sep 6 2025
Sep 5 2025
Sep 3 2025
I found a companion issue to this and created a task for it:
https://vyos.dev/T7781
! In T7760#233813, @L0crian wrote:
Quick note on this. It'll maintain the existing AS-Path in the advertisements, but it COULD change the behavior of route rejection on received routes.
Sep 2 2025
Sep 1 2025
Do you mean to manipulate the start order of the containers? If so, I don’t think it’d solve the issue. On a suitably fast system, all of the containers would start within a fraction of a second of each other. So it’d be a race condition that would almost always fail.
Aug 31 2025
Aug 29 2025
Aug 28 2025
Quick note on this. It'll maintain the existing AS-Path in the advertisements, but it COULD change the behavior of route rejection on received routes.
Aug 26 2025
Aug 25 2025
Aug 21 2025
Aug 20 2025
Aug 19 2025
Has Podman 5.4 been evaluated at all? It seems like 5.4 introduced a new feature that would solve this in the cleanest way:
Aug 11 2025
Aug 7 2025
Aug 5 2025
I just noticed this was mentioned as being added to 1.4.3 in the release notes:
Other resolved issues