IPv6 default route not set using OpenConnect

[shouldbe q931]

On Fri, Mar 15, 2013 at 2:36 PM, shouldbe q931 <shouldbeq931 at gmail.com> wrote:
> On Fri, Mar 15, 2013 at 12:46 AM, David Woodhouse <dwmw2 at infradead.org> wrote:
>> On Fri, 2013-03-15 at 00:36 +0000, shouldbe q931 wrote:
>>> Calling openconnect manually with the updated vpnc-script, IPv6 works
>>> as expected and DNS works as expected, if I use NetworkManager to
>>> initiate the VPN, IPv6 has the same problem, and the DNS servers are
>>> not set
>>
>> Thanks for testing.
>>
>> Please could you file a bug in bugzilla.gnome.org?
>>
>> --
>> dwmw2
>>
>
> bug has been filed.
>
> Cheers
>
> Arne

As per https://bugzilla.gnome.org/show_bug.cgi?id=695914

I tried Ubuntu 13.04

Ubuntu 13.04 X64
network-manager 0.9.8.0-1ubuntu2
network-manager-openconnect    0.9.6.0ubuntu1
network-manager-openconnect-gnome  0.9.6.0ubuntu1
dnsmasq-base 2.65-1ubuntu1
openconnect 4.07-1

The profile I am connecting to has a split include for IPv4 with two
/24 subnets, and a full include on IPv6

Selecting a different profile just for OpernConnect isn't an option as
the profile is selected with an LDAP map.

Calling OpenConnect manually works for IPv6 and DNS :-)  however for
users that are not sudoers, this is not an option :-(

Using the Network Manager plugin works for IPv6 in that I have IPv6
connectivity, but DNS still fails :-(

Manually adding an IPv4 DNS server did not improve matters, but
manually adding an IPv6 DNS server did.

So if the network that is being connected to has a DNS server
accessible over IPv6, there is a work around.

As it is reasonable to expect that a remote access VPN that provided
IPv6 would have a DNS server with an IPv6 static address I'd say that
it's a valid workaround, but it would be nicer it it "just worked".

Cheers

Arne