- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Yesterday
Tue, Jan 7
Mon, Jan 6
Replacement PR: https://github.com/vyos/vyos-1x/pull/4282
Canceling PR 4273 because it has several commits that go in the wrong direction. Will submit a new PR with a different approach.
@kevinrausch You see the kernel and local routes as the newest version uses FRR 10.2.x T6747
Sun, Jan 5
In T7001#211515, @c-po wrote:@nekocentral this is currently working as expected as all the guest agents got removed from the generic image which is shipped as rolling binary.
I totally understand the issue and need here - as I am also affected by this change. It was placed on the agenda for the next maintainer meeting.
tmp['address_info'] looks like
Sat, Jan 4
I tested the following builds using the same config noted above:
vyos-1.5-rolling-202412050007-generic-amd64.iso - works vyos-1.5-rolling-202412060007-generic-amd64.iso - works vyos-1.5-rolling-202412160007-generic-amd64.iso - works vyos-1.5-rolling-202412310006-generic-amd64.iso - fails vyos-1.5-rolling-202501031241-generic-amd64.iso - fails
Fri, Jan 3
Given that firewall global-options sets sysctl manually and system option performance [throughput|latency] uses pre-built tuned profiles, there isn't a good way to handle this. We should probably cross-check to see if the user is trying to apply both of these options and display a message saying that configuring both options at the same time may lead to inadvertent squashing of their desired settings.
Usually I'm not a fan of changing default behavior, but I agree that there probably isn't much value in knowing the server version with how vyos manages the nginx config as a black box.