Bug 486325

Summary: Wrong mtu value comes default and freezes ssh sessions
Product: [Fedora] Fedora Reporter: Orkan Dere <orkandere>
Component: NetworkManager-vpncAssignee: Dan Williams <dcbw>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 12CC: davidz, dcbw, jns, orkandere, pierre-bugzilla, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-05 07:00:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Orkan Dere 2009-02-19 12:03:01 UTC
Description of problem:
Default mtu value is set to 1412 and cannot be configured.

Version-Release number of selected component (if applicable):
I'm running NetworkManager-vpnc-0.7.0-1.svn13.fc10.i386 but all systems has this bug

How reproducible:
Easy enoguh

Steps to Reproduce:
1. connect to vpn
2. sudo ifconfig tun0 mtu 1412
3. connect a system via ssh
  
Actual results:
Ssh session freezes

Expected results:
Nothing should happen

Additional info:
Following workaround can be used with Network Manager Dispatcher script:
http://launchpadlibrarian.net/21952422/02mtu

Comment 1 Dan Williams 2009-02-19 17:23:34 UTC
What's the MTU on the device that the VPN is using?  vpnc requires only a few bytes of overhead (8) and thus it should really be using the MTU of the default device - the overhead.

Comment 2 Orkan Dere 2009-02-20 07:16:12 UTC
MTU should be 1390. This dispatcher script solved the issue on Fedora 10 but not on Fedora 9.

#!/bin/sh
#/etc/NetworkManager/dispatcher.d/02-mtu

if [ "$2" = "vpn-up" ]; then
	sleep 3
	/sbin/ifconfig "$1" mtu 1390
fi

Comment 3 Jessica Sterling 2009-03-10 16:57:20 UTC
This bug has been triaged.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 Bug Zapper 2009-06-09 11:30:23 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Pierre Ossman 2010-01-14 12:17:48 UTC
I'm suffering from this as well.

Dan, isn't the 8 bytes scenario the best-case one? What about when doing NAT tunnelling? (which I am)

I found some thread claiming that Ciscos own client uses 1300 for MTU.

Comment 7 Bug Zapper 2010-11-04 11:29:43 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Bug Zapper 2010-12-05 07:00:34 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.