ssh to tweenex.org

[Paul Koning]

> On Aug 10, 2018, at 10:14 AM, Warner Losh via cctalk <cctalk at classiccmp.org> wrote:
> 
> On Fri, Aug 10, 2018 at 6:09 AM, Peter Corlett via cctalk <
> cctalk at classiccmp.org> wrote:
> 
>> On Fri, Aug 10, 2018 at 02:14:54AM +0200, Stéphane Tsacas via cctalk wrote:
>>> Did anyone manage to connect to tweenex,org through ssh now that telnet
>>> port is closed ?
>>> I received an mail that says :
>>> TELNET access to twenex.org has been changed to only support SSH via the
>>> SSH passthru user twenex at sdf.org.
>> 
>> I can connect to that just fine with the standard OpenSSH client:
>> 
>> abuse at panda:~$ ssh twenex at sdf.org
>> Trying 205.166.94.130...
>> Connected to 205.166.94.130.
>> Escape character is 'off'.
>> 
>> TWENEX.ORG, PANDA TOPS-20 Monitor 7.1(21733)-4
>> 
>> If new, type 'new new' ..
>> 
>> @
>> 
>>> without saying which password should be used ...
>> 
>> You don't need a password, at least not for the ssh session
>> 
> 
> 
> % ssh -v twenex at sdf.org
> OpenSSH_7.7p1, OpenSSL 1.0.2o-freebsd  27 Mar 2018
> debug1: Reading configuration data /home/imp/.ssh/config
> debug1: /home/imp/.ssh/config line 47: Applying options for *
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: Connecting to sdf.org [205.166.94.16] port 22.
> debug1: connect to address 205.166.94.16 port 22: Network is unreachable
> ssh: connect to host sdf.org port 22: Network is unreachable
> %
> 
> I wonder why I get a different IP address?

Interesting.  I get the same address as you do.  I double checked with some other DNS servers -- 8.8.8.8 is an easy one to remember and reliably reachable.  They all show the .16 address.

But I can connect just fine, so it seems that you have a connectivity issue somewhere on the path.  Traceroute to the rescue?

	paul