Why not always move to decimal output and detect on demand if colons are present or not and adjust the string? Ne need for the user to take any action at all?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Oct 16 2021
Oct 15 2021
Oct 14 2021
Yes, closing this ...
Oct 13 2021
Oct 11 2021
What about 1.3.0-epa1?
@lucasec the reason for switching to the platform UUID instead of building up out own one was that it was not "unique".
Oct 10 2021
Implemented in
The DUID is presented in binary inside /var/lib/dhcpv6/dhcp6c_duid to read it back into ASCII use: hexdump -e '"%07.7_ax " 1/2 "%04x" " " 14/1 "%02x:" "\n"' /var/lib/dhcpv6/dhcp6c_duid
Oct 9 2021
You are right @NikolayP but opening an entire subtree might be a bit of overkill.
Unfortunately reverting back the public key did not lead to any good results either.
Oct 8 2021
Oct 7 2021
We usually communicate via https://vyos.slack.com
Any chance to get remote access to the system to debug this?
Oct 5 2021
Should we expose a system-level DUID at all? If a user wants to customize it, they could always set it on a per-interface basis using the existing configuration node.
Oct 4 2021
Can we close it @Viacheslav?
what about the following:
- Add a new system ipv6 duid CLI node which acts as the general DUID used on the system and renders /var/lib/dhcpv6/dhcp6c_duid, if not overwritten at the "interface" level set interfaces ethernet eth0 dhcpv6-options duid
- If system ipv6 duid is not configured, we "generate" the DUID using the eth0 MAC address automatically and store it in /var/lib/dhcpv6/dhcp6c_duid - thus no issue on image upgrades anymore