FS#46157 - [networkmanager] VPN connection no longer auto discovers MTU

Attached to Project: Arch Linux
Opened by Scott Coil (sylphid) - Monday, 31 August 2015, 01:58 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 15 March 2017, 13:29 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

On versions of networkmanager > 1.0.2 connecting to a vpn using openconnect through nm-applet no longer auto discovers the mtu. I have traced this back to this commit upstream:

http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=9b79e6c732ffb2fb105647c1465070d36a6cc180

I'm also attaching a patch to work around this issue. Note that the patch is not likely to be clean for upstream.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 15 March 2017, 13:29 GMT
Reason for closing:  Fixed
Additional comments about closing:  https://cgit.freedesktop.org/NetworkMana ger/NetworkManager/commit/?id=e0fa48f224 abcb73a1a129f10050f7cd942ee629
Comment by Greg Ziskind (gziskind) - Monday, 28 September 2015, 18:37 GMT
I am seeing this error as well, although it does work correctly when VPN connection is initiated from the command line.

Any status on when this will be incorporated into a release?
Comment by Luc des Trois Maisons (ShroudedNight) - Wednesday, 30 September 2015, 07:39 GMT Comment by Dan Ziemba (zman0900) - Friday, 16 October 2015, 23:14 GMT
I am also having this problem when using networkmanager to set up vpnc vpn connection. NetworkManager leaves mtu at 1500, but using vpnc command directly (with no custom mtu specified in config) sets mtu to 1412. Can we have the upstream patch applied please? Here is the Fedora bug where they have confirmed the upstream patch to work: https://bugzilla.redhat.com/show_bug.cgi?id=1244547
Comment by Dan Ziemba (zman0900) - Friday, 23 October 2015, 03:07 GMT
After upgrading to NetworkManager 1.0.7-1, this problem is fixed for me.
Comment by mariakatosvich (mariakatosvich) - Saturday, 11 June 2016, 07:04 GMT
I am seeing this error as well, although it does work correctly when VPN connection is initiated from the command line.
Thanks
http://qwikfix.co.uk/sky-customer-services/

Loading...