On 12/12/18 5:25 AM, Rick Stevens wrote:
I just did the same. From a Spectrum IP here in Orange County, CA,
the system doesn't respond (and Spectrum is a Comcast company).
From a monitoring system in our ASN (a /22 network), it works peachy:
Interesting....
Could you try it a second time? I ask since I tried from Taiwan. The first attempt..
[egreshko@meimei etc]$ ssh -v beartooth(a)beartooth.info -p 999
OpenSSH_7.9p1, OpenSSL 1.1.1 FIPS 11 Sep 2018
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config
debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for *
debug1: Connecting to beartooth.info [208.100.51.176] port 999.
debug1: Connection established.
.
.
.
The authenticity of host '[beartooth.info]:999 ([208.100.51.176]:999)' can't
be established.
ECDSA key fingerprint is SHA256:KC2aZ8T2NiqBIcjVVrhwXfPgHunj2BtECvty3QGEzxc.
Are you sure you want to continue connecting (yes/no)? no
The second time...
[egreshko@meimei etc]$ ssh -v beartooth(a)beartooth.info -p 999
OpenSSH_7.9p1, OpenSSL 1.1.1 FIPS 11 Sep 2018
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config
debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for *
debug1: Connecting to beartooth.info [208.100.51.176] port 999.
ssh: connect to host beartooth.info port 999: Connection timed out
This happens with a system that is behind a router and the router is not pingable.
If I try from another host that is directly connected to the Internet and is pingable
then
connections work all the time.
I get the feeling the folks at Netwisp, Inc. are doing something to "prevent"
hacking.
--
Right: I dislike the default color scheme Wrong: What idiot picked the default color
scheme