@j.vela please check if this option resolves the issue:
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
May 18 2026
May 18 2026
a.kudientsov added a comment to T8874: iKVM keyboard input not delivered to console after boot on Supermicro H11DSi — regression from 1.3.5 to 1.5.0.
May 17 2026
May 17 2026
mrpops2ko renamed T8881: PowerDNS refresh-on-ttl-perc, nothing-below-nxdomain, minimum-ttl-override, response policy zones (malware / adblocking) from PowerDNS refresh-on-ttl-perc, nothing-below-nxdomain, minimum-ttl-override to PowerDNS refresh-on-ttl-perc, nothing-below-nxdomain, minimum-ttl-override, response policy zones (malware / adblocking).
mrpops2ko updated the task description for T8881: PowerDNS refresh-on-ttl-perc, nothing-below-nxdomain, minimum-ttl-override, response policy zones (malware / adblocking).
c-po reopened T8847: Kernel: Enable Pressure Stall Information (PSI) metrics (CONFIG_PSI) as "In progress".
c-po renamed T8847: Kernel: Enable Pressure Stall Information (PSI) metrics (CONFIG_PSI) from Enable Pressure Stall Information (PSI) metrics to Kernel: Enable Pressure Stall Information (PSI) metrics (CONFIG_PSI).
c-po added a subtask for T8147: Update Linux Kernel to 6.18: T8496: Add kernel config needed for pwru.
c-po added a parent task for T8496: Add kernel config needed for pwru: T8147: Update Linux Kernel to 6.18.
c-po added a subtask for T8147: Update Linux Kernel to 6.18: T8879: Missing HYPERV drivers after Kernel 6.18 upgrade.
c-po added a parent task for T8879: Missing HYPERV drivers after Kernel 6.18 upgrade: T8147: Update Linux Kernel to 6.18.
c-po renamed T8879: Missing HYPERV drivers after Kernel 6.18 upgrade from Latest versions will not boot past "can't open '/sys/block/*/removable' : No such file or directory" to Missing HYPERV drivers after Kernel 6.18 upgrade.
c-po changed the status of T8879: Missing HYPERV drivers after Kernel 6.18 upgrade from Open to In progress.
Quite possibly this issue is caused by CONFIG_HYPERV_STORAGE=m removal in this PR - https://github.com/vyos/vyos-build/pull/1177
Narrowed it down to changes between 2026.05.05-0039-rolling (sig) and 2026.05.07-0040-rolling.
Also, I'm getting error
May 16 2026
May 16 2026
taylorcb added a comment to T8610: Kernel: T8610: Update Linux Kernel to 6.6.137 (fix CVE-2026-31431) aka copy.fail.
ok thanks for the info. Stream 2026.02 and 2026.03 were released very close to each other, so do you have a guesstimate on when a new version of Stream will be released? I might jump to a nightly build from early May until the next Stream is out to pick up the fix for this issue. thanks for everything!
May 15 2026
May 15 2026
PR, for the record: https://github.com/vyos/vyos-build/pull/1190
mihakralj added a comment to T8873: Add default vanity Ed25519 SSH public key for default user `vyos` in config.boot.default.
Required changes:
mihakralj updated the task description for T8873: Add default vanity Ed25519 SSH public key for default user `vyos` in config.boot.default.
c-po added a comment to T8871: Vulnerability in ptrace allows unprivileged users to read any files on the system.
We do already have a Kernel build with a custom patch.
This removes the patch and bumps to the appropriate version number: https://github.com/vyos/vyos-build/pull/1192
c-po moved T8864: Local privilege escalation in Linux kernel (Fragnesia) from Need Triage to Completed on the VyOS Rolling board.
mihakralj renamed T8873: Add default vanity Ed25519 SSH public key for default user `vyos` in config.boot.default from Add default vanity Ed25519 SSH public key for default user `vyos` user in config.boot.default to Add default vanity Ed25519 SSH public key for default user `vyos` in config.boot.default.
mihakralj updated the task description for T8873: Add default vanity Ed25519 SSH public key for default user `vyos` in config.boot.default.
mihakralj updated the task description for T8873: Add default vanity Ed25519 SSH public key for default user `vyos` in config.boot.default.
c-po added a comment to T8610: Kernel: T8610: Update Linux Kernel to 6.6.137 (fix CVE-2026-31431) aka copy.fail.
@taylorcb updating the Kernel manually is not supported by us. The next stream build will have an updated Kernel with these vulnerabilities mitigated.
taylorcb added a comment to T8610: Kernel: T8610: Update Linux Kernel to 6.6.137 (fix CVE-2026-31431) aka copy.fail.
Hi. Kind of a newbie here tracking Kernel updates with VyOS, and I'm not sure if it's appropriate to ask here? I'm running Stream 2026.03, and would like to stay on the Stream builds, so will the 6.6.137 Kernel be added to the next Stream build, or is there a way I can pull it into my current router? The nightly rolling are running are running a 6.18 Kernel, and again I really would like to stay on a Stream build to get the fix for the copy.fail vulnerability. thanks!
Viacheslav closed T8506: Kernel build process / conventions, consider using merge_config.sh as Resolved.
Viacheslav changed the status of T8781: vyos-netlinkd high CPU usage with lots of route updates from Open to Needs testing.
natali-rs1985 changed the status of T7059: High-availability virtual-server not load balancing traffic between backend servers from Open to In progress.
o.kuchmystyi changed the status of T8538: SNMP engineBoots counter is not preserved on reboot from Open to In progress.
Already fixed by https://github.com/vyos/vyos-1x/pull/5122
Consider to backport it, reopened
Viacheslav closed T8587: XML definitions use u32 type for ranges exceeding uint32 max value as Resolved.
Viacheslav changed the status of T8599: vyos-build: Fail package build if patch cannot be applied from Open to Needs reporter action.
natali-rs1985 changed the status of T8287: VPP: With disabled IPsec acceleration VPP still installs a phantom catch-all SA and policy from Open to In progress.
natali-rs1985 changed the status of T8287: VPP: With disabled IPsec acceleration VPP still installs a phantom catch-all SA and policy, a subtask of T7070: VPP related bugs the root task, from Open to In progress.
May 14 2026
May 14 2026
After the patch:
commit lock optimisation is in https://github.com/vyos/vyos-1x/pull/5200 which we might backport to 1.5.1 earlier then vyos-netlinkd
@fabrizziop https://github.com/vyos/vyos-1x/pull/5199 please sign the CLA by replying: I have read the CLA Document and I hereby sign the CLA as I put you in as author of the commit
In T8781#264420, @c-po wrote:@fabrizziop thank you for the patch. I would like to partly reuse it and add you as author. Your commit is authored by Fabrizio <fabrizzio@example.com> - is this what you wan't or what Name/Familyname/mail should I include.
@fabrizziop thank you for the patch. I would like to partly reuse it and add you as author. Your commit is authored by Fabrizio <fabrizzio@example.com> - is this what you wan't or what Name/Familyname/mail should I include.
indrajitr changed the status of T8862: DHCPv6 allow multiple IP address for host reservation from Open to In progress.
indrajitr changed the status of T8849: DHCPv6 add timezone support from In progress to Needs testing.
ssasso changed the edit policy for T8865: EVPN L3VPN incomplete frr config if more than one vrf is specified.
c-po set Forum thread to https://forum.vyos.io/t/vyos-netlinkd-high-cpu-usage/17442 on T8781: vyos-netlinkd high CPU usage with lots of route updates.
SiimS_ added a project to T8863: vyos/ifconfig/section.py does not work with enx ethernet interface names: Bugs.
c-po moved T8831: smoketests: irregular PermissionError caused by systemctl stop from Need Triage to Completed on the VyOS Rolling board.
@c-po or @dmbaturin guys, would you be open to adding ldap with sssd support without kerberos?
Copy from GH PR
[*never mind] DUID behavior. Out of the box, dhcpcd generates a per-interface DUID-LL (type 0003, derived from the interface MAC) rather than the single global DUID-LLT (type 0001) that wide-dhcpv6-client stored in /var/lib/dhcpv6/dhcp6c_duid. I think it's probably possible to come up with a migration here to keep operators' DUIDs stable, but I wasn't sure if it was worth it -- or if documenting the fact that auto DUIDs will churn is sufficient.