From: ultrapenguin@netscape.net (jeramy b smith)
To: mlan@cpu.lu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Rsync access through NAT?
Date: Tue, 24 Apr 2001 13:48:07 -0400 [thread overview]
Message-ID: <5C7B5EF3.57179C98.A41E0FAA@netscape.net> (raw)
In-Reply-To: 200104240553.HAA01467@piglet.grunz.lu
I'm not sure. The routers are cisco 55xx and 75xx with the latest firmware loaded. From there it hits the SprintLink and Abovenet clouds. I wish there was a tool that could do an point to point traceroute like journey and stop when it hits a hop that doesn't support ECN. Or does traceroute do this when used with 2.4 and ECN support on?
-jeramy b smith
mlan@cpu.lu 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.....
>
--
-jeramy b smith
"Linux is Fun!" -Linus Torvalds
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-24 17:48 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 [this message]
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=5C7B5EF3.57179C98.A41E0FAA@netscape.net \
--to=ultrapenguin@netscape.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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).