Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1244547
Summary: | NetworkManager 1.0.6-2 Regression - All VPN connections get incorrect MTU and are broken | |||
---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Steve Storey <stevestorey> | |
Component: | NetworkManager | Assignee: | Lubomir Rintel <lkundrak> | |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 22 | CC: | 3maisons, bugzilla, dcbw, dennyvatwork, fedora2021q2, henryju, lkundrak, lrintel, marcel, marianne, mike, psimerda, robert.lonnqvist+redhat, thomas, todd_lewis | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | NetworkManager-1.0.6-6.fc22 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1267004 (view as bug list) | Environment: | ||
Last Closed: | 2015-10-04 22:53:02 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: |
Description
Steve Storey
2015-07-19 22:12:16 UTC
It seems that my pppe has the same error message for wrong MTU. It seems that the problem is gone now. I don't know why. It seems too early to say. It is very unstable. The wired network often gets disconnected. In my experience the MTU for the VPN pseudo-interface is being set to 1500 regardless of the MTU for the underlying carrier interface. For what the opinion of a passer-by is worth, it wasn't clear to me from the provided description (thank you for the script, btw) that the MTU setting wasn't simply missing a subtraction for overhead. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. I just wanted to confirm I have the same issue. I have to manually update the MTU of my VPN connection: # ifconfig vpn0 mtu 1402 I found this optimal value using ping -f The maximum, and typical, MTU on Cisco AnyConnect connections is 1406. I'm seeing this same issue here after updating NetworkManager. Same bug here in fedora 23, manually changing the MTU work fine NetworkManager-l2tp-0.9.8.7-4.fc23.x86_64 NetworkManager-adsl-1.0.6-5.fc23.x86_64 NetworkManager-team-1.0.6-5.fc23.x86_64 NetworkManager-glib-1.0.6-5.fc23.x86_64 NetworkManager-pptp-1.1.0-2.20150428git695d4f2.fc23.x86_64 NetworkManager-libnm-1.0.6-5.fc23.x86_64 NetworkManager-config-connectivity-fedora-1.0.6-5.fc23.x86_64 NetworkManager-wwan-1.0.6-5.fc23.x86_64 NetworkManager-vpnc-gnome-1.0.6-3.fc23.x86_64 NetworkManager-wifi-1.0.6-5.fc23.x86_64 NetworkManager-openvpn-1.0.6-3.fc23.x86_64 NetworkManager-bluetooth-1.0.6-5.fc23.x86_64 NetworkManager-vpnc-1.0.6-3.fc23.x86_64 NetworkManager-pptp-gnome-1.1.0-2.20150428git695d4f2.fc23.x86_64 NetworkManager-openvpn-gnome-1.0.6-3.fc23.x86_64 NetworkManager-1.0.6-5.fc23.x86_64 NetworkManager-openconnect-1.0.2-2.fc23.x86_64 Started getting VPN issues on F22 after NetworkManager updates I picked up today, Following were upgraded ... NetworkManager x86_64 1:1.0.6-5.fc22 NetworkManager-adsl x86_64 1:1.0.6-5.fc22 NetworkManager-bluetooth x86_64 1:1.0.6-5.fc22 NetworkManager-config-connectivity-fedora x86_64 1:1.0.6-5.fc22 NetworkManager-glib x86_64 1:1.0.6-5.fc22 NetworkManager-libnm x86_64 1:1.0.6-5.fc22 NetworkManager-team x86_64 1:1.0.6-5.fc22 NetworkManager-wifi x86_64 1:1.0.6-5.fc22 NetworkManager-wwan x86_64 1:1.0.6-5.fc22 Luckily I had another PC I hadn't upgraded to check against I can resolve by setting the mtu to match the PC that was still working, mtu was set to 1500. ifconfig vpn0 mtu 1300 VPN is Cisco AnyConnect. Confirming, I'm seeing the same problem: mtu on vpn0 is too high. (In reply to Andy Campbell from comment #9) > Started getting VPN issues on F22 after NetworkManager updates I picked up > today, I am seeing the same issue after upgrading NetworkManager to 1.0.6. MTU ends up being 1500 and the connection doesn't work. Reducing the MTU to 1400 makes it work. With NetworkManager 1.0.6 my PPTP VPN MTU is fine: ppp0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1456 but I'm experiencing this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1266440 I don't know if the bugs are related. Same bug with a workaround patch on Arch Linux: https://bugs.archlinux.org/task/46157 Also, worth noting that manually setting the MTU with e.g. "ip link set mtu 1200 dev vpn0" is not a complete workaround. It seems that immediately after the VPN interface is brought up, secondary parameters such as search domains are communicated, and in my case some of these end up only partially configured (some search domains missing etc.) after bringing up the VPN since the MTU issue was introduced. For me today's update to NetworkManager-1:1.0.6-5.fc22.x86_64 made VPN half way fail as well. I got really strange server errors reported from various of our infrastructure servers. Firing up Wireshark showed TCP reassembly errors probably due to MTU mismatch! Just DNF downgrading NetworkManager made it all work again. Let me know if you need more details and please specify what those might comprise. I can confirm the issue using NetworkManager-1.0.6-5.fc22. MTU is 1500 and reducing manually to 1406 works. Fix in review in https://bugzilla.gnome.org/show_bug.cgi?id=754781 NetworkManager-1.0.6-6.fc22 NetworkManager-openswan-1.0.6-2.fc22 NetworkManager-openvpn-1.0.6-3.fc22 NetworkManager-vpnc-1.0.6-3.fc22 network-manager-applet-1.0.6-2.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-10143 NetworkManager-1.0.6-6.fc22 NetworkManager-openswan-1.0.6-2.fc22 NetworkManager-openvpn-1.0.6-3.fc22 NetworkManager-vpnc-1.0.6-3.fc22 network-manager-applet-1.0.6-2.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-10143 Can you also push the update for fedora 23 ? Yeah, done. I can't find the update in bodhi (I wanted to test and give karma to help it reach users faster). Do you have the bodhi URL (like it is given for fedora 22 by Fedora Uppdate System) ? I manually installed it from https://bodhi.fedoraproject.org/updates/FEDORA-2015-10143 but it was missing libnm-gtk: error: Failed dependencies: libnm-gtk.so.0(libnm_gtk_1_0_6)(64bit) is needed by NetworkManager-openvpn-1:1.0.6-3.fc22.x86_64 libnm-gtk.so.0(libnm_gtk_1_0_6)(64bit) is needed by NetworkManager-openvpn-gnome-1:1.0.6-3.fc22.x86_64 libnm-gtk.so.0(libnm_gtk_1_0_6)(64bit) is needed by NetworkManager-vpnc-gnome-1:1.0.6-3.fc22.x86_64 I then just dash-dash-nodepsed that away and my VPN is working again. Hope this gets released through regular update channels soon. Thanks! Updated packages available in Fedora repos (not fedora-updates-testing, I don't know why) are not working for me. Update don't appear in bodhi I'm using the openconnect client (Cisco Anyconnect VPN server) actual packages version : NetworkManager-wifi-1.0.6-6.fc23.x86_64 NetworkManager-l2tp-0.9.8.7-4.fc23.x86_64 NetworkManager-adsl-1.0.6-6.fc23.x86_64 NetworkManager-bluetooth-1.0.6-6.fc23.x86_64 NetworkManager-pptp-1.1.0-2.20150428git695d4f2.fc23.x86_64 NetworkManager-config-connectivity-fedora-1.0.6-6.fc23.x86_64 NetworkManager-team-1.0.6-6.fc23.x86_64 NetworkManager-wwan-1.0.6-6.fc23.x86_64 NetworkManager-vpnc-gnome-1.0.6-3.fc23.x86_64 NetworkManager-openvpn-1.0.6-3.fc23.x86_64 NetworkManager-vpnc-1.0.6-3.fc23.x86_64 NetworkManager-1.0.6-6.fc23.x86_64 NetworkManager-pptp-gnome-1.1.0-2.20150428git695d4f2.fc23.x86_64 NetworkManager-openvpn-gnome-1.0.6-3.fc23.x86_64 NetworkManager-libnm-1.0.6-6.fc23.x86_64 NetworkManager-glib-1.0.6-6.fc23.x86_64 NetworkManager-openconnect-1.0.2-2.fc23.x86_64 Any chance to backport the fix on Fedora 21? NetworkManager-1.0.6-6.fc22, NetworkManager-openswan-1.0.6-2.fc22, NetworkManager-openvpn-1.0.6-3.fc22, NetworkManager-vpnc-1.0.6-3.fc22, network-manager-applet-1.0.6-2.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update NetworkManager-openswan network-manager-applet NetworkManager NetworkManager-openvpn NetworkManager-vpnc' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-10143 I can confirm that the updated packages work fine for me - thank you! This bug can be closed as far as I'm concerned - Do I close it? The bug will be automatically closed once it has been released to the stable branch. NetworkManager-1.0.6-6.fc22, NetworkManager-openswan-1.0.6-2.fc22, NetworkManager-openvpn-1.0.6-3.fc22, NetworkManager-vpnc-1.0.6-3.fc22, network-manager-applet-1.0.6-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. |