From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: mlan@cpu.lu
Cc: geert@linux-m68k.org, ultrapenguin@netscape.net,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Rsync access through NAT?
Date: Tue, 24 Apr 2001 22:51:10 +0200 [thread overview]
Message-ID: <3AE5E73E.76FAA847@iiic.ethz.ch> (raw)
In-Reply-To: 200104242000.WAA00723@piglet.grunz.lu
Michel Lanners wrote:
> >> > 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.....
> >
> > Then why can I ping penguinppc.org without problems? Because my AXP
> > firewall still runs 2.2.x?
>
> Maybe because the NAT function on my Cisco 803 is to blame?
NAT is also a suspect of mine - it's the commonality between our cases.
> Cisco might 'accidentaly' support it in normal packet forwarding, but might
> not when doing NAT, since the IP header may need to be rewritten-- probably
> without the ECN bits.
I must admit I don't really know anything about ECN but that the name of the
/proc file is tcp_ecn, right? It kinda implies that ECN is only involved with
TCP, not ICMP or UDP or whatever. In particular, UDP worked fine (DNS lookups)
when TCP didn't.
--
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/
next prev parent reply other threads:[~2001-04-24 20:51 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
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 [this message]
[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=3AE5E73E.76FAA847@iiic.ethz.ch \
--to=michdaen@iiic.ethz.ch \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
--cc=ultrapenguin@netscape.net \
/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).