Bug 433846 - vpnc hard-coded mtu in tun0 creation
vpnc hard-coded mtu in tun0 creation
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: vpnc (Show other bugs)
8
All Linux
low Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-02-21 13:35 EST by Brian Long
Modified: 2008-04-03 04:42 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-03 04:42:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Brian Long 2008-02-21 13:35:51 EST
Description of problem:
/etc/vpnc/vpnc-script has a hard-coded MTU of 1412 used to bring up the tun0
interface.  This is an invalid MTU if the underlying Ethernet interface (i.e.
eth0) already has a lower-than-normal MTU of 1400.  vpnc-script should read the
existing MTU from the interface and subtract a certain number of bytes to
determine its MTU instead of hard-coding 1412.

Version-Release number of selected component (if applicable):
vpnc-0.5.1-2.fc8

How reproducible:
Always

Steps to Reproduce:
1. ifconfig eth0 mtu 1400
2. vpnc Config
3. ifconfig tun0 shows mtu 1412, greater than eth0.
4. scp large file over VPN connection and scp will stall
  
Actual results:
scp stalls

Expected results:
scp finishes

Additional info:
If I edit vpnc-script and replace 1412 with 1300, scp works fine when my eth0
mtu is 1400.
Comment 1 Tomas Mraz 2008-04-03 04:42:18 EDT
Fixed in rawhide.

Note You need to log in before you can comment on or make changes to this bug.