linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Dänzer <daenzerm@student.ethz.ch>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: TCP problems in 2.4
Date: Tue, 05 Sep 2000 23:28:25 +0200	[thread overview]
Message-ID: <39B56579.9AEED836@student.ethz.ch> (raw)
In-Reply-To: 39B4B5A4.502388B@relog.ch


Michel Dänzer wrote:
>
> I rsynced bitkeeper test 8 a few days ago and the same TCP problems I had
> experienced with pmac-devel are still there.
>
> I suspect it's the TCP congestion notification, will try without that, has
> anyone tried it?

That seems to be the case, it works here with a different ISDN router. I'll
try at the other place with this feature disabled and report success or
failure (just in case anyone is interested :)


Michel


--
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86 and The DRI Project

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-09-05 21:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-05  8:58 TCP problems in 2.4 Michel Dänzer
2000-09-05 21:28 ` Michel Dänzer [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=39B56579.9AEED836@student.ethz.ch \
    --to=daenzerm@student.ethz.ch \
    --cc=linuxppc-dev@lists.linuxppc.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).