#isckea — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #isckea, aggregated by home.social.
-
Oh, that's why me KEA dhcpv6 configuration wasn't working:
1) I'd converted the configuration over from my prior isc-dhcpv6 one.
2) The configuration has some fixed address assignments, specified via duid, but these weren't working.
3) The dhcpv6 'ADVERTISE' message in this case was saying "Server could not select subnet for this client".It turns out that the example configuration makes NO MENTION of needing an `"interface": "..."` stanza within the `"subnet6"` section. This is to tell the server the network is local and that, yes, it can reach such clients.
-
Oh, that's why me KEA dhcpv6 configuration wasn't working:
1) I'd converted the configuration over from my prior isc-dhcpv6 one.
2) The configuration has some fixed address assignments, specified via duid, but these weren't working.
3) The dhcpv6 'ADVERTISE' message in this case was saying "Server could not select subnet for this client".It turns out that the example configuration makes NO MENTION of needing an `"interface": "..."` stanza within the `"subnet6"` section. This is to tell the server the network is local and that, yes, it can reach such clients.
-
Oh, that's why me KEA dhcpv6 configuration wasn't working:
1) I'd converted the configuration over from my prior isc-dhcpv6 one.
2) The configuration has some fixed address assignments, specified via duid, but these weren't working.
3) The dhcpv6 'ADVERTISE' message in this case was saying "Server could not select subnet for this client".It turns out that the example configuration makes NO MENTION of needing an `"interface": "..."` stanza within the `"subnet6"` section. This is to tell the server the network is local and that, yes, it can reach such clients.
-
Oh, that's why me KEA dhcpv6 configuration wasn't working:
1) I'd converted the configuration over from my prior isc-dhcpv6 one.
2) The configuration has some fixed address assignments, specified via duid, but these weren't working.
3) The dhcpv6 'ADVERTISE' message in this case was saying "Server could not select subnet for this client".It turns out that the example configuration makes NO MENTION of needing an `"interface": "..."` stanza within the `"subnet6"` section. This is to tell the server the network is local and that, yes, it can reach such clients.
-
Oh, that's why me KEA dhcpv6 configuration wasn't working:
1) I'd converted the configuration over from my prior isc-dhcpv6 one.
2) The configuration has some fixed address assignments, specified via duid, but these weren't working.
3) The dhcpv6 'ADVERTISE' message in this case was saying "Server could not select subnet for this client".It turns out that the example configuration makes NO MENTION of needing an `"interface": "..."` stanza within the `"subnet6"` section. This is to tell the server the network is local and that, yes, it can reach such clients.