DHCPv6 for IPv6 network allocation

[regulad]

A note for the community

Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.

Disclaimer

• I have read and understood the disclaimer.
• I plan to implement the feature myself.

Subsystem

None

Feature description

JetKVM should be able to request a IPv6 address via DHCPv6. Currently, this is not possible. JetKVM cannot join networks that use DHCPv6 for address assignment.

[MichaelKing1832]

My experience is that my JetKVM is getting a DHCPv6 address from my router. JetKVM App: 0.5.4, System: 0.2.7

My router is an ASUS RT-BE86U running current ASUS firmware, and set for "stateless" auto configuration in the LAN settings.
This "stateless" method is known as the SLAAC method, while DHCPv6 would be designated as not stateless, stateful, or disabled stateless.

With SLAAC, clients use anycast packets for RS (Router Solicitation) and the router sends RA (Router Advertising) packets in response or periodically broadcasts them. This only enables the client to self-configure their own IPv6 address in the subnet advertised by the router. Their hasn't been consensus/standardization in the RFCs on using RA responses to include DNS server settings, vlan tagging and more.

Generally speaking, it is a bad idea to use both SLAAC and DHCPv6. If JetKVM did add support for DHCPv6, it would add complexity to the UI because the user would need to configure whether the JetKVM device would use SLAAC or DHCPv6.

[regulad]

RAs can also have a bit set that instructs clients to go through a stateful address derivation process with a DHCPv6 server. The JetKVM should at the very least respect this setting, and and the SLAAC option in the options should be changed to "Respect RAs."

…

On Tue, Apr 7, 2026 at 12:36 AM Michael K ***@***.***> wrote: *MichaelKing1832* left a comment (jetkvm/kvm#1351) <#1351 (comment)> My experience is that my JetKVM is getting a DHCPv6 address from my router. JetKVM App: 0.5.4, System: 0.2.7 My router is an ASUS RT-BE86U running current ASUS firmware, and set for "stateless" auto configuration in the LAN settings. This "stateless" method is known as the SLAAC method, while DHCPv6 would be designated as not stateless, stateful, or disabled stateless. With SLAAC, clients use anycast packets for RS (Router Solicitation) and the router sends RA (Router Advertising) packets in response or periodically broadcasts them. This only enables the client to self-configure their own IPv6 address in the subnet advertised by the router. Their hasn't been consensus/standardization in the RFCs on using RA responses to include DNS server settings, vlan tagging and more. Generally speaking, it is a bad idea to use both SLAAC and DHCPv6. If JetKVM did add support for DHCPv6, it would add complexity to the UI because the user would need to configure whether the JetKVM device would use SLAAC or DHCPv6. — Reply to this email directly, view it on GitHub <#1351 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMQAOMR7BIGEAI7ZWKNCC2T4USATJAVCNFSM6AAAAACXBKAKYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOJWGQ3TSMJRGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[MichaelKing1832]

I was about to add to my earlier comment that all that may be needed is for JetKVM to add "accept_ra 1" to their inet6 interface definition.