linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: rrschulz@cris.com
Cc: linuxppc-user@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: Inbound TCP Circuits over PPP Stall; MTUs and Kppp
Date: Sun, 26 Sep 1999 08:38:05 +0200 (CEST)	[thread overview]
Message-ID: <199909260638.IAA00291@piglet.cpu.lu> (raw)
In-Reply-To: <v04210101b4132312764f@[206.173.234.57]>


Hi all,

On  25 Sep, this message from Randall R Schulz echoed through cyberspace:
> In my lonely quest to solve the problem I'm having with the stalling 
> of inbound (only, it seems) TCP streams over PPP (but not local 
> loopback, it seems), I'm reaching the grasping at straws stage.

I've had that same problem repeatedly in the past; I don't see it now
because I don't use PPP anymore.

What was weired for me is that the problem seemed to depend on file
content, so the actual data transfered did make a difference.

For instance, I always had problems with the glibc RPM files.
Downloading them to a different machine at my provider, gzip'ing them
there, I was able to download them to my box without a problem.

> By using tcpdump, I have discovered what seems to be a relevant fact: 
> When the stream stalls, the sending side (always the remote) is 
> resending the same range of bytes (sequence numbers) over and over 
> again with an inter-packet arrival time that increases gradually 
> until it reaches about two minutes where it holds until one side or 
> the other gives up and closes the stream. Each such packet has the 
> PUSH flag set and elicits an ACK from my system, but for whatever 
> reason, the remote just keeps sending repetitions of a packet 
> containing the same range of sequence numbers (with a total of 1448 
> data bytes each).

Does your box send out the ACK's for the incoming data? In that case,
either these never reach the remote end, or the ACK packets contain
some form of error...


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/

  reply	other threads:[~1999-09-26  6:38 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 [this message]
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
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=199909260638.IAA00291@piglet.cpu.lu \
    --to=mlan@cpu.lu \
    --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 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).