linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ethan Benson <erbenson@alaska.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Rsync access through NAT?
Date: Tue, 24 Apr 2001 15:13:43 +0200	[thread overview]
Message-ID: <3AE57C07.B06406B5@iiic.ethz.ch> (raw)
In-Reply-To: Pine.LNX.4.05.10104240948110.22858-100000@callisto.of.borg


Geert Uytterhoeven wrote:
>
> On Mon, 23 Apr 2001, Ethan Benson wrote:
> > On Tue, Apr 24, 2001 at 07:53:38AM +0200, Michel Lanners wrote:
> > > I have ECN compiled in all my 2.4 kernels. They are building right now
> > > without ECN.... We'll see.
> > >
> > > <a compile & reboot later>
> >
> > there is a sysctl variable that disables this at runtime you know ;-)
> > i don't remember where it is offhand, sysctl -a | grep ecn or find
> > /proc -name '*ecn*' -print should find it.
> >
> > > Yup, that seems to be the problem. rsync works again for me on
> > > penguinppc. So I guess that some device close to penguinppc.org doesn't
> > > support ECN.....
> >
> > probably turning on ecn is more trouble then its worth right now,
> > unfortuanatly...
>
> | tux$ cat /proc/sys/net/ipv4/tcp_ecn
> | 1
> | tux$
>
> I have it enabled on all my machines running 2.4.x. So far no problems.

You're lucky, it used to keep me from establishing any TCP connections to the
outside world through an ISDN router.


--
Earthling Michel Dänzer (MrCooper)    \   Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast   \        XFree86 and DRI project member

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

  reply	other threads:[~2001-04-24 13:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0104170144460.14396-100000@ash.penguinppc.org>
2001-04-17 15:31 ` Rsync access through NAT? Michel Lanners
2001-04-17 16:36   ` jeramy b smith
2001-04-24  5:53     ` Michel Lanners
2001-04-24  7:14       ` Ethan Benson
2001-04-24  7:48         ` Geert Uytterhoeven
2001-04-24 13:13           ` Michel Dänzer [this message]
2001-04-24 17:48       ` jeramy b smith
2001-04-24 19:12         ` Geert Uytterhoeven
2001-04-24 20:00           ` Michel Lanners
2001-04-24 20:51             ` Michel Dänzer
     [not found] <200104250459.XAA22227@lists.linuxppc.org>
2001-04-25 21:57 ` Peter Cordes

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=3AE57C07.B06406B5@iiic.ethz.ch \
    --to=michdaen@iiic.ethz.ch \
    --cc=erbenson@alaska.net \
    --cc=geert@linux-m68k.org \
    --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).