Sat, Mar 15
Thu, Mar 13
Hey guys. Is there any reason why this issue was changed from "possibly destroys the router" (which is true if using conntrack and rebooting the system) to => perfectly compatible?
Wed, Mar 12
Tue, Mar 4
Mon, Mar 3
Wed, Feb 26
Alright - I've created PRs https://github.com/vyos/vyos-1x/pull/4371 and https://github.com/vyos/vyos-documentation/pull/1603 for this one.
Tue, Feb 25
Fri, Feb 21
@talmakion I think it good idea is removed , this attribute was added by cisco in the early day of internet, as you mentioned , it can be solved using 0:0 in a RM.
Can't reproduce the issue
Looks like this was deprecated in FRR a while ago: https://github.com/FRRouting/frr/commit/81a57d81812115bdbab25168e86e509e2db607a1
Thu, Feb 20
Wed, Feb 19
Tue, Feb 18
Mon, Feb 17
Feb 14 2025
hsflowd expects the agent-address to be chosen from addresses it can see in it's own namespace.
Feb 8 2025
Feb 7 2025
Feb 6 2025
I suppose we could just add a "guesstimate" check, say, 2GB of free space. At the moment, rolling release images are about 600M, 2GB should be enough for a while, hopefully.
Feb 5 2025
Feature no longer required for my initial use-case -closing
Confirmed for:
- 1.4.1
- 1.4-stable-202502050953
- 1.5-stream-202502051856