From: Michel Lanners <mlan@cpu.lu>
To: rrschulz@cris.com
Cc: Paul.Mackerras@cs.anu.edu.au, linuxppc-user@lists.linuxppc.org,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Inbound TCP Circuits over PPP Stall; MTUs and Kppp
Date: Mon, 27 Sep 1999 21:57:52 +0200 (CEST) [thread overview]
Message-ID: <199909271957.VAA00313@piglet.cpu.lu> (raw)
In-Reply-To: <v04210100b415499d9a1c@[206.173.234.127]>
Hi all,
On 27 Sep, this message from Randall R Schulz echoed through cyberspace:
> At Paul M.'s suggestion, I tried using the "novj" option (only) in my
> ~/.ppprc file. I made several tests against a few files on a couple
> of different servers.
>
> The good news (at least as far as it offers a work-around): It does
> appear that disabling Van Jacobsen compression alleviates the symptom.
Aha...
> However, I did also discover that even with VJ compression left
> enabled, not all remote hosts experience this problem.
[snip]
> On the other hand, transferring files from "ftp.xemacs.org" (a.k.a.
> "gwyn.tux.org") is virtually impossible while VJ compression is
> enabled but works just fine with VJ disabled. In this case, my guess
> is that this host *does* run Linux.
>
> It does also appear to be data related (not surprising if it's a
> problem with the implementation of the compression algorithm, whether
> in LinuxPPC 2.2.6 or whatever's running on ftp.xemacs.org). In
> particular this file:
> <ftp://ftp.xemacs.org/pub/xemacs/docs/letter/internals-letter.pdf.gz>
> will stall the TCP circuit after just a few K have been transferred.
> I repeated this twice and (like every file I tried) and it does
> transfer fine with VJ off.
OK, I saw similar things as well. I had more trouble with the
ftp.linuxppc.org server at that time (running some 2.1.x kernel), than
with my provider's HP server...
> So, it may be the case that the LinuxPPC code in my kernel is OK (as
> evidenced by the fact that connecting to ftp.cris.com works OK) but
> that the implementation on ftp.xemacs.org is not correct or fully
> compliant with the VJ specification. It's also possible that my
> kernel's VJ code has a bug that is somehow tolerated by
> ftp.cris.com's VJ code.
EEeeeepppp.... wrong conclusion here ;-). VJ compression is only active
on your PPP link, not end-to-end. So the remote server knows nothing of
the VJ copmpression your machine negotiates with the access server at
your provider.
Which brings us to another variable in the connection chain: the access
server at your provider. In my case, it was a Cisco 2509 with
USRobotics modems. You might want to check with your provider, just in
case... If it really is a VJ problem, then the provider's box could
have an influence, too.
> One last question: Can I turn VJ compression on and off while a PPP
> link is active, or must I choose before connecting?
I don't think Linux's PPP can renegotiate link parameters. In any case,
the remote end must then be prepared to renegotiate as well...
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-27 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-26 1:49 Inbound TCP Circuits over PPP Stall; MTUs and Kppp Randall R Schulz
1999-09-26 6:38 ` Michel Lanners
1999-09-26 21:19 ` Randall R Schulz
1999-09-27 7:07 ` Geert Uytterhoeven
1999-09-27 0:14 ` Paul Mackerras
1999-09-27 16:35 ` Randall R Schulz
1999-09-27 19:57 ` Michel Lanners [this message]
1999-09-28 15:58 ` Lou Langholtz
1999-09-28 16:02 ` Geert Uytterhoeven
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=199909271957.VAA00313@piglet.cpu.lu \
--to=mlan@cpu.lu \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.org \
--cc=rrschulz@cris.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.