linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan Scholz <sscholz@astaro.com>
To: linux-ppp@vger.kernel.org
Subject: Re: ppp_mppe osize issue
Date: Mon, 08 Nov 2004 09:50:54 +0000	[thread overview]
Message-ID: <418F417E.5080107@astaro.com> (raw)
In-Reply-To: <20041106000351.3d60f2ba@emach>

PPPD reduces the MTU of the interface, because MPPE encryption needs
additional 4 bytes. Windows clients do not see if that way, however.
This leads to problems, because the Windows client sends a TCP MSS
of 4 bytes too large for PPPD.
What you can do is change the PPPD, so that it does not reduce the MTU anymore.
See the patch below.

Alternatively, set the MTU of the PPP interface in the ip-up script.

Stephan


diff -u -r1.1.1.1 -r1.1.1.1.4.1
--- sources/p/pppd/pppd/ccp.c	2004/01/16 09:47:28	1.1.1.1
+++ sources/p/pppd/pppd/ccp.c	2004/10/15 15:08:50	1.1.1.1.4.1
@@ -1191,7 +1191,12 @@
  		     */
  		    mtu = netif_get_mtu(f->unit);
  		    if (mtu)
-			netif_set_mtu(f->unit, mtu - MPPE_PAD);
+		    {
+			// Removed the lowering of the MTU, because it causes
+			// problems with routing (TCP/MSS: Windows clients
+			// do not care about this reduced packet size)
+			//netif_set_mtu(f->unit, mtu - MPPE_PAD);
+		    }
  		    else
  			newret = CONFREJ;
  		}


Guy Rouillier wrote:
> (I sent this earlier this week under the subject "osize too small" and
> now realize that most spam filters probably kicked it out.  Resending...
> 
> I'm using ppp with pptp to connect to a MS server at work.  Kernel is
> 2.6.3 AMD64 on Mandrake 10.0, ppp 2.4.2.  I built this kernel myself to
> fix the 64-bit issues with ppp (fix previously reported.)   When I have
> VPN up and run a browser, it will retrieve a particular page fine the
> first time.  However, if I click the submit button on that page again
> (which transmits a bunch of data - I authored this page so know all
> about it) the browser just goes into continuous wait and never actually
> transmits anything.  I see the following in dmesg:
> 
> PPP generic driver version 2.4.2
> ppp_mppe: module license 'BSD without advertisement clause' taints
> kernel.
> PPP MPPE Compression module registered
> Module ppp_mppe cannot be unloaded due to unsafe usage in
> include/linux/module.h:503
> mppe_compress[0]: osize too small! (have: 1400 need: 1404)
> ppp: compressor dropped pkt
> mppe_compress[0]: osize too small! (have: 1400 need: 1404)
> ppp: compressor dropped pkt
> 
> What is the appropriate fix for this? ifconfig shows an MTU of 1396 for
> ppp0.  I tried specifying mtu 1500 when starting pppd, but it still ends
> up 1396.  I suppose the server end is constraining it.  Appreciate all
> suggestions - I can rebuild the kernel if necessary.
> 


-- 
Stephan Scholz <sscholz@astaro.com> | Development
Astaro AG | www.astaro.com | Phone +49-721-490069-0 | Fax -55

Documentation: http://docs.astaro.org
User Bulletin Board: http://www.astaro.org

- Certified by ICSA labs - June 2004
- Computer Reseller News: "CRN Certified Program" - June 2004
- Linux Pro Italy: Best Rating 10 out of 10 points - May 2004
- Linux Enterprise Readers' Choice Award: Best Firewall - October 2003


      reply	other threads:[~2004-11-08  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-06  5:03 ppp_mppe osize issue Guy Rouillier
2004-11-08  9:50 ` Stephan Scholz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=418F417E.5080107@astaro.com \
    --to=sscholz@astaro.com \
    --cc=linux-ppp@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).