[RC5] Linux as gateway.
Bryan Craig Edwards
edwardsc at se40.corona.navy.mil
Fri Sep 4 14:50:28 EDT 1998
I'm betting the Linux box is blocking uncommon ports like 2064. Have you
tried using any of the "proxy" setting in the client. Usually you can use
http encoding and go through port 80 to the proxy (which is almost alway
open for web browsing). Otherwise, have the Linux admin "punch" a hole on
port 2064 for your machine.
Other thoughts and opinions are welcome!
From: Gary Stainburn <gary.stainburn at ringways.co.uk>
To: rc5 at lists.distributed.net <rc5 at lists.distributed.net>
Date: Friday, September 04, 1998 2:04 AM
Subject: [RC5] Linux as gateway.
>this is more of a Linux problem than an rc5 problem, but maybe one of you
out there has had this problem. I have an IBM RS6000 F50 running aix 4.2 on
a network that is connected to the internet through a PC running Linux and
masquerading. If I ping us.v27.distributed.net (or whatever it is) from the
RS then everything works, but if I try to run rc5des the comms fails, and if
I try to ping on port 2046 (or whatever) then the ping also fails. Has
anyone got any ideas how I can fix or at least trace the fault.
>To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
>rc5-digest subscribers replace rc5 with rc5-digest
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest
More information about the rc5