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.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Feb 5 2025
In T6445#191023, @Viacheslav wrote:The config-sync is not a HA.
I don't think config-sync should save, reboot, or do something else.
Imagine if, due to config-sync, you lose access to the secondary node and if it was saved by config-sync.That is completely wrong behavior. However, we need to think about how to integrate this feature correctly.
fix for another git commit archive related problem:
https://github.com/vyos/vyos-1x/pull/4333
looks like the problem was fixed in this task: T7048
Feb 4 2025
I'm willing to work on this issue to implement solution proposed by @Viacheslav.
The bug is not reproduced via API
Feb 3 2025
Probably simial issue https://vyos.dev/T7129
Feb 2 2025
Working on this one. The changes are more significant than I expected, partially due to address being plural now.
PR submitted
I've got a patch nearly ready
Feb 1 2025
Tested as working in: VyOS 1.5-rolling-202502011110
Fixed by adding required permission
