On Tue, 11 Dec 2018 12:53:03 -0700, stan wrote:
I think I understand better what is happening. Whether I can help I
don't know. A summary:
You have no problem with your ISP (Comcast). Your problem is with the
third party that handles your private domain for email. When you try to
connect to that site via ssh, the connection attempts time out.
Yes, exactly.
This sounds like an ssh configuration issue, not a firewall issue.
I'm
not very familiar with ssh since I don't use it a lot, but here goes.
Are you using key based login rather than password login?
No; I don't even know what the former is.
If you are, is it possible the keys are incorrect with f29, and you
need
to generate new keys?
Have you tried using the -v option to ssh, the verbose option for
debugging so you can see what is happening with the connection process?
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: connect to address 208.100.51.176 port 999: Connection timed out
ssh: connect to host beartooth.info port 999: Connection timed out
[btth@localhost ~]$
Perhaps someone more knowledgeable about ssh will immediately point
to
the problem for you.
I hope the above helps someone. I've been using ssh ever since
telnet became unsafe, and never thought to look at options, fool that I
am. It has just worked for about twenty years.