Closed ajs124 closed 3 years ago
Hello, I'm a bot and I thank you in the name of the community for opening this issue.
To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.
The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it.
If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them.
Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel.
Describe the bug DHCPv6 works (slightly) differently from v4 and is also configured (slightly) differently from it. Namely, the configuration defined here is wrong.
hardware ethernet
cannot be matched, because DHCPv6 does not provide it.fixed-address
should also befixed-address6
.To Reproduce Steps to reproduce the behavior:
dhcp6.machines
dhcp6.service
failing to start.Expected behavior I did not expect DHCPv6 to work this way. We cannot fix that, though. In my (short) research, I also did not find an easy way to match for the hardware address and instead opted to use the clients' host names.
Maintainer information: