Opened 6 years ago

Last modified 22 months ago

#243 assigned Feature Wish

Allow IPV6 addresses in dhcp-options

Reported by: dennisd Owned by: Gert Döring
Priority: major Milestone: release 2.5
Component: IPv6 Version: OpenVPN git master branch (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords: dhcp
Cc: Heiko Hund

Description

It looks like the check in options.c "if (ip_addr_dotted_quad_safe (parm)) /* FQDN -- IP address only */" stops IPv6 addresses used in dhcp-options from being set up on the client.

The PUSH seems to be working ok.

Fri Dec 07 11:36:31 2012 OpenVPN 2.3_rc1 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Nov 6 2012

Fri Dec 07 11:36:36 2012 Options error: dhcp-option parameter DNS '2001:470:xxxx:xxxx::1' must be an IP address
Fri Dec 07 11:36:36 2012 Options error: dhcp-option parameter NTP '2001:470:xxxx:xxxx::1' must be an IP address

Change History (8)

comment:1 Changed 5 years ago by doktornotor

Can this be fixed please? Highly annoying.

comment:2 Changed 5 years ago by Samuli Seppänen

Keywords: dhcp added; DHCP IPV6 DHCP-OPTION removed
Owner: set to Gert Döring
Status: newassigned

comment:3 Changed 5 years ago by Gert Döring

Cc: Heiko Hund added

This can not actually be fixed. IPv4 DHCP is not able to convey IPv6 addresses to the client, so even if we would accept the IPv6 addresses, there is nothing in the DHCP protocol we could put them to.

To signal IPv6 DNS, NTP, etc. servers you'd need to use DHCPv6, which we currently do not implement (and implementing would be a major undertaking).

We are currently rewriting the way IP-related information (IPv4/IPv6 address, routes, ...) are signalled to windows by means of a dedicated service. I'm copying d12fk so he can spend a few thoughts on this, and whether we can use this for IPv6 info as well.

comment:4 Changed 5 years ago by Gert Döring

Type: Bug / DefectFeature Wish
Version: 2.3-beta / 2.3-RCgit master branch

... and it definitely will not go into the 2.3.x train, as the new "tell windows!" machinery will only be added to 2.4

comment:5 Changed 5 years ago by Gert Döring

Milestone: release 2.4

comment:6 Changed 23 months ago by Gert Döring

whee... just rediscovered that we already HAVE a trac ticket for this - the discussion on the mailing list got re-started just a week ago, and everyone had forgotten :-) "bump!"

comment:7 Changed 22 months ago by selvanair

Version 2.4 now has a new dhcp-option type to set IPv6 dns server addresses:

--dhcp-option DNS6 2001:4860:4860::8888

Could be used multiple times (up to 4 DNS addresses). IPv6 NTP addresses is still not supported.

Will be available in 2.4_beta2 release.

commit 94bfc256d4e96e6e91fa5a518352d758c09800f3
Author: Gert Doering <gert@…>
Date: Mon Nov 21 17:42:42 2016 +0100

Stub implementation of "--dhcp-option DNS6 <v6addr>"

commit 786e06ade9f5dfad8ac360499187fa8e536d15cb
Author: Selva Nair <selva.nair@…>
Date: Mon Nov 21 22:12:12 2016 -0500

Handle --dhcp-option DNS6 on Windows using netsh

commit 29d0f5d4fd5422a1f9d60d49c8842c95433009aa
Author: Selva Nair <selva.nair@…>
Date: Sun Nov 13 20:45:12 2016 -0500

Set IPv6 DNS servers using interactive service

comment:8 Changed 22 months ago by Gert Döring

Milestone: release 2.4release 2.5

Heh, we just barely made it :-)

Bumping this ticket to release/2.5 - next thing is "all the other things people may want to signal using XXXv6" as 2.5 is supposed to be usable without IPv4 in the tunnel.

Not making any promises on delivery date...

Thanks, Selva for the great last-minute work on this for 2.4 :-)

Note: See TracTickets for help on using tickets.