SSH question

[Fred Smith]

Hi all!

I feel dumb having to ask this, I feel I should know the answer, but
can't dredge it up.

I've recently installed F20 on my old eeepc, where it seems to run fine,
btw, but I can't for the life of me figure out how to connect to it from
another system with ssh.

I've made sure that sshd is installed, and "systemctl list-unit-files"
shows it as enabled. As far as I can figure out how to use the relatively
new firewall app (and I have to admit some hesitance there since I'm
not sure I really DO understand it...) the necessary ports are open.

however when I attempt to connect to it with ssh from another box I get
I get an instantaneous "ssh: connect to host 192.168.2.117 port 22:
connection refused".  And when I attempt to connect back to itself:
"ssh -X fredex@localhost" I get the same thing.

If someone can give me a whack on the head (designed to joggle my brains
a bitg--in a good way) I'd appreciate the guidance.

thanks!

[Ed Greshko]

On 06/13/14 06:12, Fred Smith wrote:
> Hi all!
>
> I feel dumb having to ask this, I feel I should know the answer, but
> can't dredge it up.
>
> I've recently installed F20 on my old eeepc, where it seems to run fine,
> btw, but I can't for the life of me figure out how to connect to it from
> another system with ssh.
>
> I've made sure that sshd is installed, and "systemctl list-unit-files"
> shows it as enabled. As far as I can figure out how to use the relatively
> new firewall app (and I have to admit some hesitance there since I'm
> not sure I really DO understand it...) the necessary ports are open.
>
> however when I attempt to connect to it with ssh from another box I get
> I get an instantaneous "ssh: connect to host 192.168.2.117 port 22:
> connection refused".  And when I attempt to connect back to itself:
> "ssh -X fredex@localhost" I get the same thing.
>
> If someone can give me a whack on the head (designed to joggle my brains
> a bitg--in a good way) I'd appreciate the guidance.

Just a bit of information.....

If you see "No route to host" on an ssh connection it would indicate the port is closed.
When you see "connection refused" it means there is no process bound to the open port.

So you should see....

[egreshko@meimei ~]$ netstat --tcp -ap | grep ssh
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN      -                  
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN      -

and ....

[egreshko@meimei ~]$ ps -eaf | grep sshd
root      1269     1  0 Jun12 ?        00:00:00 /usr/sbin/sshd -D

and ...

[egreshko@meimei ~]$ systemctl status sshd.service
sshd.service - OpenSSH server daemon
   Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)
   Active: active (running) since Thu 2014-06-12 08:48:39 CST; 21h ago
 Main PID: 1269 (sshd)
   CGroup: /system.slice/sshd.service
           └─1269 /usr/sbin/sshd -D

[Alchemist]

2014-06-13 1:12 GMT+03:00 Fred Smith :
> Hi all!
>
> I feel dumb having to ask this, I feel I should know the answer, but
> can't dredge it up.
>
> I've recently installed F20 on my old eeepc, where it seems to run fine,
> btw, but I can't for the life of me figure out how to connect to it from
> another system with ssh.
>
> I've made sure that sshd is installed, and "systemctl list-unit-files"
> shows it as enabled. As far as I can figure out how to use the relatively
> new firewall app (and I have to admit some hesitance there since I'm
> not sure I really DO understand it...) the necessary ports are open.
>
> however when I attempt to connect to it with ssh from another box I get
> I get an instantaneous "ssh: connect to host 192.168.2.117 port 22:
> connection refused".  And when I attempt to connect back to itself:
> "ssh -X fredex@localhost" I get the same thing.
>
> If someone can give me a whack on the head (designed to joggle my brains
> a bitg--in a good way) I'd appreciate the guidance.
>
> thanks!

"connection refused" by receiving RST packet means port is closed, and no
process listens on port as Ed said

look through
a) if it runs on correct port (22) and interfaces

egrep "^Port|ListenAddress" /etc/ssh/sshd_config && netstat -ntlp | grep
sshd

b) check again for running firewall rules to filter inbound traffic with
tcp-reset option (I doubt, because "ssh -X fredex@localhost" fails too)

c) test manually

nc -4vi1 localhost 22

from remote pc
nc -4vi1 192.168.2.117 22

try to restart service, then and check logs

journalctl -xb _COMM=sshd
> .----    Fred Smith   /
> ( /__  ,__.   __   __ /  __   : /
>  /    /  /   /__) /  /  /__) .+'           Home:
> [e-mail]
> /    /  (__ (___ (__(_ (___ / :__
> 781-438-5471
> -------------------------------- Jude 1:24,25
>
> --
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

[Ed Greshko]

On 06/13/14 06:31, Ed Greshko wrote:
> If you see "No route to host" on an ssh connection it would indicate the port is closed.

I should have used the term "filtered".  Meaning "a" firewall rule is in place.  It could be a firewall on the receiving machine....or it could be a firewall between the two machines.

"closed" should be used to describe a port with no firewall blockage.....but with no process running on the port.
> When you see "connection refused" it means there is no process bound to the open port.

[Fred Smith]

On Fri, Jun 13, 2014 at 06:31:39AM +0800, Ed Greshko wrote:
> On 06/13/14 06:12, Fred Smith wrote:
> > Hi all!
> >
> > I feel dumb having to ask this, I feel I should know the answer, but
> > can't dredge it up.
> >
> > I've recently installed F20 on my old eeepc, where it seems to run fine,
> > btw, but I can't for the life of me figure out how to connect to it from
> > another system with ssh.
> >
> > I've made sure that sshd is installed, and "systemctl list-unit-files"
> > shows it as enabled. As far as I can figure out how to use the relatively
> > new firewall app (and I have to admit some hesitance there since I'm
> > not sure I really DO understand it...) the necessary ports are open.
> >
> > however when I attempt to connect to it with ssh from another box I get
> > I get an instantaneous "ssh: connect to host 192.168.2.117 port 22:
> > connection refused".  And when I attempt to connect back to itself:
> > "ssh -X fredex@localhost" I get the same thing.
> >
> > If someone can give me a whack on the head (designed to joggle my brains
> > a bitg--in a good way) I'd appreciate the guidance.
>
> Just a bit of information.....
>
> If you see "No route to host" on an ssh connection it would indicate the port is closed.
> When you see "connection refused" it means there is no process bound to the open port.
>
> So you should see....
>
> [egreshko@meimei ~]$ netstat --tcp -ap | grep ssh
> (Not all processes could be identified, non-owned process info
>  will not be shown, you would have to be root to see it all.)
> tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN      -                  
> tcp6       0      0 [::]:ssh                [::]:*                  LISTEN      -
>
> and ....
>
> [egreshko@meimei ~]$ ps -eaf | grep sshd
> root      1269     1  0 Jun12 ?        00:00:00 /usr/sbin/sshd -D
>
> and ...
>
> [egreshko@meimei ~]$ systemctl status sshd.service
> sshd.service - OpenSSH server daemon
>    Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)
>    Active: active (running) since Thu 2014-06-12 08:48:39 CST; 21h ago
>  Main PID: 1269 (sshd)
>    CGroup: /system.slice/sshd.service
>            └─1269 /usr/sbin/sshd -D

Thanks... Yeah, all three of those commands give the output you show.

Any further thoughts?

[Fred Smith]

On Thu, Jun 12, 2014 at 07:29:00PM -0400, Fred Smith wrote:
> On Fri, Jun 13, 2014 at 06:31:39AM +0800, Ed Greshko wrote:
> > On 06/13/14 06:12, Fred Smith wrote:
> > > Hi all!
> > >
> > > I feel dumb having to ask this, I feel I should know the answer, but
> > > can't dredge it up.
> > >
> > > I've recently installed F20 on my old eeepc, where it seems to run fine,
> > > btw, but I can't for the life of me figure out how to connect to it from
> > > another system with ssh.
> > >
> > > I've made sure that sshd is installed, and "systemctl list-unit-files"
> > > shows it as enabled. As far as I can figure out how to use the relatively
> > > new firewall app (and I have to admit some hesitance there since I'm
> > > not sure I really DO understand it...) the necessary ports are open.
> > >
> > > however when I attempt to connect to it with ssh from another box I get
> > > I get an instantaneous "ssh: connect to host 192.168.2.117 port 22:
> > > connection refused".  And when I attempt to connect back to itself:
> > > "ssh -X fredex@localhost" I get the same thing.
> > >
> > > If someone can give me a whack on the head (designed to joggle my brains
> > > a bitg--in a good way) I'd appreciate the guidance.
> >
> > Just a bit of information.....
> >
> > If you see "No route to host" on an ssh connection it would indicate the port is closed.
> > When you see "connection refused" it means there is no process bound to the open port.
> >
> > So you should see....
> >
> > [egreshko@meimei ~]$ netstat --tcp -ap | grep ssh
> > (Not all processes could be identified, non-owned process info
> >  will not be shown, you would have to be root to see it all.)
> > tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN      -                  
> > tcp6       0      0 [::]:ssh                [::]:*                  LISTEN      -
> >
> > and ....
> >
> > [egreshko@meimei ~]$ ps -eaf | grep sshd
> > root      1269     1  0 Jun12 ?        00:00:00 /usr/sbin/sshd -D
> >
> > and ...
> >
> > [egreshko@meimei ~]$ systemctl status sshd.service
> > sshd.service - OpenSSH server daemon
> >    Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)
> >    Active: active (running) since Thu 2014-06-12 08:48:39 CST; 21h ago
> >  Main PID: 1269 (sshd)
> >    CGroup: /system.slice/sshd.service
> >            └─1269 /usr/sbin/sshd -D

Oh duh, please ignore this. too many keyboards sitting in front of me,
I ran it on the wrong one.

I'll get back later with info from the right one.

Fred
> Thanks... Yeah, all three of those commands give the output you show.
>
> Any further thoughts?
>
> -- 
> ---- Fred Smith -- [e-mail] -----------------------------
>     "Not everyone who says to me, 'Lord, Lord,' will enter the kingdom of
>      heaven, but only he who does the will of my Father who is in heaven."
> ------------------------------ Matthew 7:21 (niv) -----------------------------
>
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

[William Oliver]

On Thu, 12 Jun 2014, Fred Smith wrote:
> Hi all!
>
> I feel dumb having to ask this, I feel I should know the answer, but
> can't dredge it up.
>
> I've recently installed F20 on my old eeepc, where it seems to run fine,
> btw, but I can't for the life of me figure out how to connect to it from
> another system with ssh.
>
> I've made sure that sshd is installed, and "systemctl list-unit-files"
> shows it as enabled. As far as I can figure out how to use the relatively
> new firewall app (and I have to admit some hesitance there since I'm
> not sure I really DO understand it...) the necessary ports are open.
>
> however when I attempt to connect to it with ssh from another box I get
> I get an instantaneous "ssh: connect to host 192.168.2.117 port 22:
> connection refused".  And when I attempt to connect back to itself:
> "ssh -X fredex@localhost" I get the same thing.
>
> If someone can give me a whack on the head (designed to joggle my brains
> a bitg--in a good way) I'd appreciate the guidance.
>
> thanks!

Here are the things that have kept sshd from working on new installations for me in the past.  I don't know which, if any, would apply to Fedora 20 today.

1) As I remember, some ssh setups come configured so that they will only talk to localhost (though that may be ftp, not ssh).

2) For some reason, I commonly had a problem with SeLinux blocking ssh.  I turn it off.

3) Sometimes I forget to set up the rsa keys and nothing will authenticate.

billo

[Ed Greshko]

On 06/13/14 07:57, Bill Oliver wrote:
> On Thu, 12 Jun 2014, Fred Smith wrote:
> > Hi all!
> >
> > I feel dumb having to ask this, I feel I should know the answer, but
> > can't dredge it up.
> >
> > I've recently installed F20 on my old eeepc, where it seems to run fine,
> > btw, but I can't for the life of me figure out how to connect to it from
> > another system with ssh.
> >
> > I've made sure that sshd is installed, and "systemctl list-unit-files"
> > shows it as enabled. As far as I can figure out how to use the relatively
> > new firewall app (and I have to admit some hesitance there since I'm
> > not sure I really DO understand it...) the necessary ports are open.
> >
> > however when I attempt to connect to it with ssh from another box I get
> > I get an instantaneous "ssh: connect to host 192.168.2.117 port 22:
> > connection refused".  And when I attempt to connect back to itself:
> > "ssh -X fredex@localhost" I get the same thing.
> >
> > If someone can give me a whack on the head (designed to joggle my brains
> > a bitg--in a good way) I'd appreciate the guidance.
> >
> > thanks!
>
> Here are the things that have kept sshd from working on new installations for me in the past.  I don't know which, if any, would apply to Fedora 20 today.
> As I remember, some ssh setups come configured so that they will only talk to localhost (though that may be ftp, not ssh).

I think you're mixing that up with sendmail.  sshd will, by default, bind to all interfaces on port 22.
> For some reason, I commonly had a problem with SeLinux blocking ssh.  I turn it off.

Never had a problem with ssh and selinux.  Don't turn things off blindly.  If you think you have a selinux issue, investigate.
> Sometimes I forget to set up the rsa keys and nothing will authenticate.

When the sshd is started for the first time, the server certs will be generated.

[William Oliver]

On Fri, 13 Jun 2014, Ed Greshko wrote:
> > Here are the things that have kept sshd from working on new installations for me in the past.  I don't know which, if any, would apply to Fedora 20 today.
> > As I remember, some ssh setups come configured so that they will only talk to localhost (though that may be ftp, not ssh).
>
> I think you're mixing that up with sendmail.  sshd will, by default, bind to all interfaces on port 22.

Yep, that's what I was thinking about.  Sorry, that's what I get from shooting from the hip.
> > For some reason, I commonly had a problem with SeLinux blocking ssh.  I turn it off.
>
> Never had a problem with ssh and selinux.  Don't turn things off blindly.  If you think you have a selinux issue, investigate.

Our mileage certainly varies with this one.  Unfortunately, I hop around distros, so I can't remember if it was Fedora I had this issue with.  Nonetheless, I've had cases where SeLinux was blocking these ports.
> > Sometimes I forget to set up the rsa keys and nothing will authenticate.
>
> When the sshd is started for the first time, the server certs will be generated.

Yes, I know.  However, I have, in the past, managed to screw things up tinkering with things, and had a hell of a time making it right again.

billo

[Fred Smith]

On Fri, Jun 13, 2014 at 06:31:39AM +0800, Ed Greshko wrote:
> On 06/13/14 06:12, Fred Smith wrote:
> > Hi all!
> >
> > I feel dumb having to ask this, I feel I should know the answer, but
> > can't dredge it up.
> >
> > I've recently installed F20 on my old eeepc, where it seems to run fine,
> > btw, but I can't for the life of me figure out how to connect to it from
> > another system with ssh.
> >
> > I've made sure that sshd is installed, and "systemctl list-unit-files"
> > shows it as enabled. As far as I can figure out how to use the relatively
> > new firewall app (and I have to admit some hesitance there since I'm
> > not sure I really DO understand it...) the necessary ports are open.
> >
> > however when I attempt to connect to it with ssh from another box I get
> > I get an instantaneous "ssh: connect to host 192.168.2.117 port 22:
> > connection refused".  And when I attempt to connect back to itself:
> > "ssh -X fredex@localhost" I get the same thing.
> >
> > If someone can give me a whack on the head (designed to joggle my brains
> > a bitg--in a good way) I'd appreciate the guidance.
>
> Just a bit of information.....
>
> If you see "No route to host" on an ssh connection it would indicate the port is closed.
> When you see "connection refused" it means there is no process bound to the open port.
>
> So you should see....
>
> [egreshko@meimei ~]$ netstat --tcp -ap | grep ssh
> (Not all processes could be identified, non-owned process info
>  will not be shown, you would have to be root to see it all.)
> tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN      -                  
> tcp6       0      0 [::]:ssh                [::]:*                  LISTEN      -
>
> and ....
>
> [egreshko@meimei ~]$ ps -eaf | grep sshd
> root      1269     1  0 Jun12 ?        00:00:00 /usr/sbin/sshd -D
>
> and ...
>
> [egreshko@meimei ~]$ systemctl status sshd.service
> sshd.service - OpenSSH server daemon
>    Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)
>    Active: active (running) since Thu 2014-06-12 08:48:39 CST; 21h ago
>  Main PID: 1269 (sshd)
>    CGroup: /system.slice/sshd.service
>            └─1269 /usr/sbin/sshd -D

Ah, yeah. these showed that it wasn't actually running. not sure why,
I used the gui services tool to enable and start it, or I think I did...
but a quick "systemctl start sshd.service" and "systemctl enable sshd.service"
seems to have fixed me up.

thanks Ed!