pfSense

Doesn't look like the OpenVPN management interface reports this back in the status line as it does for others, at least for SSL/TLS I see no mention of the client's IPv6 IP in the CLIENT_LIST response. It does show in the ROUTING_TABLE responses but there is no way to distinguish the client's IPv6 IP in the responses from any other single IPv6 routed IP.

I checked status outputs 1, 2, and 3, no difference.

I'll have to check on static key and IPv6-native. If the above case is true, we may have to push this back to 2.2 and hope they address it upstream in the meantime, or patch it ourselves.

If nothing else, we could add the OpenVPN routing table output to the status page, as it does show what networks are routed to each connected user/common name. Not at clean/nice as seeing it on a single row though.

After poking some more there just isn't a way to get the info from the management interface that I can see. If you connect a tunnel up to an IPv6 peer the management interface just leaves the field blank in the output.

The routing table method will have to do for now.

This still isn't entirely possible in the most current version of OpenVPN (2.3.3 as of this update) for mixed IPv4 and IPv6 setups. OpenVPN reports the IPv6 routes for the internal routing table OK, but it does not print the IPv6 address along with the IPv4 address in a mixed/dual setup. For IPv6 only clients it's OK.

Link to the OpenVPN Wiki article on IPv6 support in their management interface:
http://community.openvpn.net/openvpn/wiki/IPv6SupportInManagementInterface

Moving this off to a future version to revisit at a later time. The above link mentions a patch being reviewed, but the last update is 12 months ago.

still missing in most recent OpenVPN currently available, 2.3.8.

It's finally there in OpenVPN 2.4!

And since it's caused the status page to report fields incorrectly, it needs to come in for pfSense 2.4

Applied in changeset bffa3185a63cbdd727701704d3b82abd7c61a78c.

Works!