[Dxspider-support] Connection Closed by Foreign Host

[Dave Trainor]

Its actually not on port 23, my firewall rule is.  The box itself is
listening on 27753 and I have a firewall port forwarding rule that listens
on the assigned IP address and port forwards port 23 to 27753 on the
actual box.    So its really not on port 23, this keeps the box safe as
all other ports are not accessible.  I know this rule is working fine
since I have many other users, its only this one.

Not to complicate things but I also have a port forwarding rule that
publishes port 80 for the web server, but it is port 80 to port 80.

I probably should have pointed this out as you are 100% right on why not
to have it actually running on port 23. And you did make it clear in the
manual. No problem at all there.

 I was just trying to simplify the question to the group and not throw in
too many variables.  I am quite confident the firewall rules are correct
and not part of this.   The cluster machine is in a managed data center.

73 - Dave N8ZFM




On 1/29/15, 5:16 AM, "Dirk Koopman" <djk at tobit.co.uk> wrote:

>It is *SPECIFICALLY* not "recommended" to run a DXSpider installation on
>port 23. Apart from the security aspects (one has to run as root to be
>able to do it all), port 23 has a load of hidden protocol associated
>which DXSpider does not support well or (mostly) at all.
>
>I thought I had made this abundantly clear in the installation manual,
>but it seems I was wrong.
>
>My (slightly politer version of) Linus Torvalds moment:
>
>In this case, I am sorry but, if it breaks you get to keep all the pieces.
>
>Dirk G1TLH
>
>On 29/01/15 00:25, Dave Trainor wrote:
>> I have a report from a user on the KY4XX-3 cluster that my telnet
>> connection is returning the following on a connect:
>>
>> telnet dxc.ky4xx.com
>>
>> Trying 198.73.30.100...
>>
>> Connected to dxc.ky4xx.com (198.73.30.100).
>>
>> Escape character is '^]'.
>>
>> Connection closed by foreign host.
>>
>> However I have node links up and running just fine, and other users
>> connected via telnet, the only difference is that my other users are
>> using various windows telnet programs and this error above is from a
>> user running Linux and telnetting from the bash command prompt, as far
>> as I know that should make no difference.
>>
>> Anyone able to test for me and let me know what they get?  Or any ideas
>> on what might be happening? If I have one person getting denied a
>> connection then I have many more I don¹t know about so am concerned to
>> get this figured out.
>>
>> The error would normally indicate that telnet/DXSpider is not listening
>> on the port, but it Is, since I have other users on and working fine, am
>> stumped at the moment.
>>
>> System is dxc.ky4xx.com (198.73.30.100) on port 23, also web cluster
>> page on port 80
>>
>> The user that gets the above, gets the web page in a browser just fine,
>> and is able to connect to other clusters.
>>
>> Thanks,
>>
>> Dave N8ZFM, sysop of KY4XX-3  dxc.ky4xx.com
>>
>>
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at dxcluster.org
>> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>
>
>_______________________________________________
>Dxspider-support mailing list
>Dxspider-support at dxcluster.org
>http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>--
>This message was scanned by ESVA and is believed to be clean.
>Click here to report this message as spam.
>http://h0stname/cgi-bin/learn-msg.cgi?id=ACD3928C6A.9983A
>
>