[PATCH] Re: OpenConnect, Juniper and NetworkManager

[Ian Turner]

OK, patches attached. Feedback welcome; if the response here is positive
(or silent), then I will go ahead and submit to GNOME and KDE.

On 02/21/2016 02:52 PM, David Woodhouse wrote:
>>  and also fixing some other OpenConnect/NetworkManager
>> issues (for example, currently user specified ipv4 configuration is
>> ignored).
> Hm, do you have a bug number for the that one? I personally run a
> NetworkManager configuration which eschews the server-provided IPv4
> configuration (a full tunnel with the default route) and sets up a
> bunch of explicit routes for a split tunnel. It works fine.
What I'm finding is that if I set the IPv4 configuration to manual, it
is ignored by NetworkManager. But I don't think this is a Juniper issue,
as we just pass the config off to NetworkManager with their VPN API.

--Ian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: network-manager-openconnect.patch
Type: text/x-patch
Size: 9200 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20160508/a9ad6573/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plasma-nm.patch
Type: text/x-patch
Size: 4130 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20160508/a9ad6573/attachment-0001.bin>