Re: ssh-ing in inside private network

From	Brian <ad44@cityscape.co.uk>
Newsgroups	linux.debian.user
Subject	Re: ssh-ing in inside private network
Date	2016-03-31 14:40 +0200
Message-ID	<riK3g-531-13@gated-at.bofh.it> (permalink)
References	<riJgS-4jD-23@gated-at.bofh.it> <riJAd-4KT-11@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Thu 31 Mar 2016 at 13:28:57 +0200, tomas@tuxteam.de wrote:

> On Thu, Mar 31, 2016 at 12:43:49PM +0100, Lisi Reisz wrote:
> > I want all the computers on my private network to be able to shh into each 
> > other.  In Jessie, what do I have to do where in what config file?  
> > Presumably some port is shut??
> 
> 0. Each computer should be able to "see" port 22 (ssh) of each other's
>    (I'm assuming you go with the default port for ssh, this can be
>    changed, but I wouldn't do that without some reason)
> 
> 1. Each computer should have an SSH server running (on Debian that would
>    be package openssh-server: in Debian it has priority "optional": I'd
>    double-check that it's installed)
> 
> 3. To connect, you need also an openssh-client (since this has priority
>    "standard" n Debian, chances are that it's there already)
>    You can check all these three by trying from each host "ssh user@the-other-host"
>    and studying the responses.
> 
> Since your question was pretty general, I preferred to go with a terse,
> bird's perspective answer. Let's tackle the details when they come up.

There is also dropbear as a lightweight SSH2 server and client. Using
it in preference to openssh is useful for resource constrained machines.

Thread

ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-03-31 13:50 +0200
  Re: ssh-ing in inside private network <tomas@tuxteam.de> - 2016-03-31 14:10 +0200
    Re: ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-03-31 14:30 +0200
      Re: ssh-ing in inside private network <tomas@tuxteam.de> - 2016-03-31 15:10 +0200
        Re: ssh-ing in inside private network David Wright <deblis@lionunicorn.co.uk> - 2016-03-31 20:20 +0200
      Re: ssh-ing in inside private network Brian <ad44@cityscape.co.uk> - 2016-03-31 16:10 +0200
        Re: ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-31 21:40 +0200
          Re: ssh-ing in inside private network John Hasler <jhasler@newsguy.com> - 2016-05-31 22:10 +0200
          Re: ssh-ing in inside private network Joe <joe@jretrading.com> - 2016-05-31 23:00 +0200
            Re: ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-01 00:30 +0200
              Re: ssh-ing in inside private network Joe <joe@jretrading.com> - 2016-06-01 09:50 +0200
          Re: ssh-ing in inside private network Stephen Powell <zlinuxman@fastmail.com> - 2016-06-01 01:00 +0200
            Re: ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-01 01:30 +0200
              Re: ssh-ing in inside private network Stephen Powell <zlinuxman@fastmail.com> - 2016-06-01 01:50 +0200
                Re: ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-01 02:20 +0200
                Re: ssh-ing in inside private network John Hasler <jhasler@newsguy.com> - 2016-06-01 02:30 +0200
                Re: ssh-ing in inside private network Richard Hector <richard@walnut.gen.nz> - 2016-06-01 09:50 +0200
                Re: ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-01 12:30 +0200
          Re: ssh-ing in inside private network Richard Hector <richard@walnut.gen.nz> - 2016-06-01 01:00 +0200
            Re: ssh-ing in inside private network John Hasler <jhasler@newsguy.com> - 2016-06-01 01:20 +0200
            Re: ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-01 01:20 +0200
              Re: ssh-ing in inside private network Dan Purgert <dan@djph.net> - 2016-06-01 14:20 +0200
                Re: ssh-ing in inside private network Mark Fletcher <mark27q1@gmail.com> - 2016-06-01 15:50 +0200
                Re: ssh-ing in inside private network Dan Purgert <dan@djph.net> - 2016-06-01 17:00 +0200
                Re: ssh-ing in inside private network David Wright <deblis@lionunicorn.co.uk> - 2016-06-01 20:00 +0200
                Re: ssh-ing in inside private network Dan Purgert <dan@djph.net> - 2016-06-02 22:20 +0200
                Re: ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-03 11:10 +0200
                Re: ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-03 11:10 +0200
                Running without X was: Re: ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-03 11:30 +0200
                Re: Running without X was: Re: ssh-ing in inside private network Dan Purgert <dan@djph.net> - 2016-06-03 15:50 +0200
                Re: Running without X was: Re: ssh-ing in inside private network David Wright <deblis@lionunicorn.co.uk> - 2016-06-03 16:40 +0200
                Re: Running without X was: Re: ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-03 18:40 +0200
          Re: ssh-ing in inside private network David Wright <deblis@lionunicorn.co.uk> - 2016-06-02 00:10 +0200
            Re: ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-03 11:00 +0200
              Re: ssh-ing in inside private network Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-03 11:40 +0200
      Re: ssh-ing in inside private network Bob Bernstein <poobah@ruptured-duck.com> - 2016-03-31 19:50 +0200
    Re: ssh-ing in inside private network Brian <ad44@cityscape.co.uk> - 2016-03-31 14:40 +0200
      Re: ssh-ing in inside private network <tomas@tuxteam.de> - 2016-03-31 15:20 +0200
        Re: ssh-ing in inside private network Brian <ad44@cityscape.co.uk> - 2016-03-31 15:50 +0200
          Re: ssh-ing in inside private network <tomas@tuxteam.de> - 2016-03-31 16:20 +0200

csiph-web