On Wed, 2018-01-17 at 09:41 +0100, Nikos Mavrogiannopoulos wrote: > Hi, > ?I got a report in ocserv that openconnect would not see an IPv6 DNS > address. Checking it further it seems that openconnect client would > only set INTERNAL_IP4_DNS with the contents of whatever the servers > provided (ipv4 or ipv6 address). As ocserv may send an IPv6 address, > that would be wrong. > > The attached patch can make openconnect set INTERNAL_IP6_DNS instead, > however vpnc-script doesn't seem to anything with that variable. > > Is there already some handling of IPv6 DNS addresses that I'm missing, > or it is not supported at this point? The INTERNAL_IP4_DNS variable is misnamed. For addresses and routes it makes sense to have separate configuration for IPv6 vs. Legacy IP. There is no such distinction for DNS. You don't have separate DNS servers for IPv6 lookups vs. legacy lookups. All the DNS servers go into the *same* list. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20180117/86d0841d/attachment.bin>
