User Details
- User Since
- Dec 21 2023, 4:42 AM (102 w, 3 d)
Aug 5 2025
Aug 4 2025
Jul 16 2025
Jul 15 2025
Jul 14 2025
Jul 13 2025
Jul 7 2025
Resolved by T7424 and https://github.com/vyos/vyos-build/pull/983.
Jun 30 2025
Commands also affected:
Jun 29 2025
Jun 3 2025
Caused by this commit that merges iproute2-next into the main branch of iproute2 and introduced in v6.15.0 which was pushed to debian-backports a couple of days ago.
Apr 23 2025
Apr 2 2025
Feb 5 2025
For anyone else who finds this in their travels, trying to figure out why 1.4.1 broke their DHCPv6 with custom DUID: the workaround steps detailed are not sufficient to restore DHCPv6 functionality. Removing the custom DUID from the VyOS configuration leaves invalid data in /var/lib/dhcpv6/dhcp6c_duid, causing DHCPv6 solicits to be ignored by the server as they don't contain a valid DUID.
Dec 23 2024
Can't be bothered trying to contribute to this project any more.
Dec 20 2024
Dec 19 2024
Also just discovered this at the end of the configure results output before kea starts building:
Dec 18 2024
Nov 1 2024
Jun 14 2024
Jun 12 2024
@aidan-gibson You can build current with the microcode packages included by passing the following to the build script:
Apr 19 2024
This is the result of buster-backports being removed from the main repository server: https://backports.debian.org/news/Removal_of_buster-backports_from_the_debian_archive/
Apr 10 2024
Confirmed this is now fixed.
Mar 15 2024
Feb 2 2024
Jan 18 2024
I've traced the issue back to a USB device that creates an Ethernet interface on the OS. I suspect that the issue was caused by the USB device not being ready by the time ddclient tried to start and bind to configured interfaces, causing the boot time configuration to fail. Given that this is an edge case that would rarely occur, and now that I have replaced the USB device with an actual Ethernet device, I'm happy to close this bug report.
Jan 17 2024
I've done more investigation of this issue today, and I believe I understand the cause.
Jan 14 2024
I haven't had the chance to test this, but the following should be sufficient to replicate the behaviour:
Jan 9 2024
Maybe making the size of the ramdisk configurable via CLI would be wise? I feel that there's enough variation in hardware configurations out there that hard-coding a value would cause problems.
Jan 3 2024
PR submitted: https://github.com/vyos/vyos-1x/pull/2746