From: Michel Lanners <mlan@cpu.lu>
To: jsmith@ash.penguinppc.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Rsync access through NAT?
Date: Tue, 17 Apr 2001 17:31:12 +0200 (CEST) [thread overview]
Message-ID: <200104171531.RAA00992@piglet.grunz.lu> (raw)
In-Reply-To: <Pine.LNX.4.33.0104170144460.14396-100000@ash.penguinppc.org>
Hi again,
To the list: for some time now, I've had problems accessing
penguinppc.org from my PPC machines (I've noticed it with rsync... for
www I use a proxy on i386).
Turns out the problem only occurs with 2.4 kernels:
[mlan@piglet ~]$ uname -a
Linux piglet 2.4.3-pre3 #4 Thu Apr 12 01:47:59 CEST 2001 ppc unknown
(benh's tree)
and 2.4.4-pre1 from benh on the TiBook.
Anyone else seen this? Note, with a 2.2 kernel, all is OK. I've not had
a chance to test a 2.4 kernel on i386 to see whether it's the same over
there.
I hope it doesn't matter, but I'm accessing the net through a NAT router
(which is configured OK, thanks for asking ;-)
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/
next parent reply other threads:[~2001-04-17 15:31 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 ` Michel Lanners [this message]
2001-04-17 16:36 ` Rsync access through NAT? 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
[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=200104171531.RAA00992@piglet.grunz.lu \
--to=mlan@cpu.lu \
--cc=jsmith@ash.penguinppc.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).