Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #231758 > unrolled thread

Re: identifying my LInux machine on my LAN

Started byIL Ka <kazakevichilya@gmail.com>
First post2021-02-16 18:00 +0100
Last post2021-02-17 18:20 +0100
Articles 8 — 3 participants

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: identifying my LInux machine on my LAN IL Ka <kazakevichilya@gmail.com> - 2021-02-16 18:00 +0100
    Re: identifying my LInux machine on my LAN Kenneth Parker <sea7kenp@gmail.com> - 2021-02-16 19:00 +0100
      Re: identifying my LInux machine on my LAN Paul Scott <waterhorse@ultrasw.com> - 2021-02-16 20:00 +0100
        Re: identifying my LInux machine on my LAN Paul Scott <waterhorse@ultrasw.com> - 2021-02-16 21:00 +0100
          Re: identifying my LInux machine on my LAN IL Ka <kazakevichilya@gmail.com> - 2021-02-16 21:10 +0100
            Re: identifying my LInux machine on my LAN Paul Scott <waterhorse@ultrasw.com> - 2021-02-17 17:50 +0100
              Re: identifying my LInux machine on my LAN IL Ka <kazakevichilya@gmail.com> - 2021-02-17 18:10 +0100
                Re: identifying my LInux machine on my LAN - some success Paul Scott <waterhorse@ultrasw.com> - 2021-02-17 18:20 +0100

#231758 — Re: identifying my LInux machine on my LAN

FromIL Ka <kazakevichilya@gmail.com>
Date2021-02-16 18:00 +0100
SubjectRe: identifying my LInux machine on my LAN
Message-ID<BJbRF-5I1-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Check that
* connection is not blocked by firewall: ``sudo iptables -L``
* your ssh is listening for port 22: ``ss -l -t``
* your ip address is correct: ``ip addr``

On Tue, Feb 16, 2021 at 7:50 PM Paul Scott <waterhorse@ultrasw.com> wrote:

> My LAN used to have 1 or two computers and/or debices and my Debian
> Linux machine on it.  I used to be able to log in either on the LAN from
> my wife's Windows computer or from outside the LAN with my Debian laptop
> with ssh or Windows machines on which I had installed putty or Bitvise.
>
> I have dynamic DNS hosted by Dyn and I use ddclient.
>
> I currently use DHCP for my Debian machine and have also attempted to
> connect with its local IP from the Windows machine on the LAN.
>
> Now all methods fail.
>
> I don't remember if attachments are allowed but I will attach one
> example of a failure as I possible clue.
>
> TIA for any help,
>
> Paul
>
>
>

[toc] | [next] | [standalone]

#231760

FromKenneth Parker <sea7kenp@gmail.com>
Date2021-02-16 19:00 +0100
Message-ID<BJcNH-6gc-5@gated-at.bofh.it>
In reply to#231758

[Multipart message — attachments visible in raw view] — view raw

On Tue, Feb 16, 2021, 11:56 AM IL Ka <kazakevichilya@gmail.com> wrote:

> Check that
> * connection is not blocked by firewall: ``sudo iptables -L``
> * your ssh is listening for port 22: ``ss -l -t``
> * your ip address is correct: ``ip addr``
>

I would add:  Check if openssh-server is installed.

>
> On Tue, Feb 16, 2021 at 7:50 PM Paul Scott <waterhorse@ultrasw.com> wrote:
>
>> My LAN used to have 1 or two computers and/or debices and my Debian
>> Linux machine on it.  I used to be able to log in either on the LAN from
>> my wife's Windows computer or from outside the LAN with my Debian laptop
>> with ssh or Windows machines on which I had installed putty or Bitvise.
>>
>> I have dynamic DNS hosted by Dyn and I use ddclient.
>>
>> I currently use DHCP for my Debian machine and have also attempted to
>> connect with its local IP from the Windows machine on the LAN.
>>
>> Now all methods fail.
>>
>> I don't remember if attachments are allowed but I will attach one
>> example of a failure as I possible clue.
>>
>> TIA for any help,
>>
>> Paul
>>
>
Kenneth Parker

>

[toc] | [prev] | [next] | [standalone]

#231761

FromPaul Scott <waterhorse@ultrasw.com>
Date2021-02-16 20:00 +0100
Message-ID<BJdJM-6OJ-3@gated-at.bofh.it>
In reply to#231760

[Multipart message — attachments visible in raw view] — view raw

On 2/16/21 10:50 AM, Kenneth Parker wrote:
>
>
> On Tue, Feb 16, 2021, 11:56 AM IL Ka <kazakevichilya@gmail.com 
> <mailto:kazakevichilya@gmail.com>> wrote:
>
>     Check that
>     * connection is not blocked by firewall: ``sudo iptables -L``
>
paul@Joy4:~$ sudo iptables -L
[sudo] password for paul:
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

>     * your ssh is listening for port 22: ``ss -l -t``
>     * your ip address is correct: ``ip addr``
>
>
> I would add:  Check if openssh-server is installed.

I guess I lost track of this reason openssh-server wasn't installed:

b1 - #948318 - openssh-server: Unable to restart sshd restart after 
upgrade to version 8.1p1-2

Is what I get when I try to install it (on sid).

I have now installed it over that bug and will see what happens. How 
serious is that bug?

Thank you,

Paul

[toc] | [prev] | [next] | [standalone]

#231763

FromPaul Scott <waterhorse@ultrasw.com>
Date2021-02-16 21:00 +0100
Message-ID<BJeFQ-7nB-1@gated-at.bofh.it>
In reply to#231761

[Multipart message — attachments visible in raw view] — view raw

On 2/16/21 11:57 AM, Paul Scott wrote:
>
>
> On 2/16/21 10:50 AM, Kenneth Parker wrote:
>>
>>
>> On Tue, Feb 16, 2021, 11:56 AM IL Ka <kazakevichilya@gmail.com 
>> <mailto:kazakevichilya@gmail.com>> wrote:
>>
>>     Check that
>>     * connection is not blocked by firewall: ``sudo iptables -L``
>>
> paul@Joy4:~$ sudo iptables -L
> [sudo] password for paul:
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
I'm not sure if the above is Ok.
>
>
>>     * your ssh is listening for port 22: ``ss -l -t``
>>     * your ip address is correct: ``ip addr``
>>
>>
>> I would add:  Check if openssh-server is installed.
>
> I guess I lost track of this reason openssh-server wasn't installed:
>
> b1 - #948318 - openssh-server: Unable to restart sshd restart after 
> upgrade to version 8.1p1-2
>
> Is what I get when I try to install it (on sid).
>
> I have now installed it over that bug and will see what happens.  How 
> serious is that bug?
>
Installing openssh-server didn't help at least with the Bitvise from a 
Windows machine on the same LAN.

Paul

[toc] | [prev] | [next] | [standalone]

#231764

FromIL Ka <kazakevichilya@gmail.com>
Date2021-02-16 21:10 +0100
Message-ID<BJePv-7FV-1@gated-at.bofh.it>
In reply to#231763

[Multipart message — attachments visible in raw view] — view raw

>
>
> paul@Joy4:~$ sudo iptables -L
> [sudo] password for paul:
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
>
> I'm not sure if the above is Ok.
>


Your firewall is effectively off: It shouldn't block any traffic.

Installing openssh-server didn't help at least with the Bitvise from a
> Windows machine on the same LAN.
>
Check your ssh up and running: ``$ systemctl status ssh``
What about the machine's IP address and port ssh listens to? Have you
checked it?

[toc] | [prev] | [next] | [standalone]

#231802

FromPaul Scott <waterhorse@ultrasw.com>
Date2021-02-17 17:50 +0100
Message-ID<BJybv-3rO-7@gated-at.bofh.it>
In reply to#231764
On 2/16/21 1:07 PM, IL Ka wrote:
> systemctl status ssh``


paul@Joy4:~/music/pima$ systemctl status ssh``

● ssh.service - OpenBSD Secure Shell server
      Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor 
preset: enabled)
      Active: active (running) since Tue 2021-02-16 11:53:13 MST; 21h ago
        Docs: man:sshd(8)
              man:sshd_config(5)
    Main PID: 359457 (sshd)
       Tasks: 3 (limit: 16625)
      Memory: 3.5M
         CPU: 28.076s
      CGroup: /system.slice/ssh.service
              ├─359457 sshd: /usr/sbin/sshd -D [listener] 1 of 10-100 
startups
              ├─390020 sshd: unknown [priv]

              └─390021 sshd: unknown [net]


ssh and Bitvise still fail t o connect

Paul

[toc] | [prev] | [next] | [standalone]

#231805

FromIL Ka <kazakevichilya@gmail.com>
Date2021-02-17 18:10 +0100
Message-ID<BJyuR-3Ol-9@gated-at.bofh.it>
In reply to#231802

[Multipart message — attachments visible in raw view] — view raw

>
>
> paul@Joy4:~/music/pima$ systemctl status ssh``
>
> ● ssh.service - OpenBSD Secure Shell server
>       Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor
> preset: enabled)
>       Active: active (running) since Tue 2021-02-16 11:53:13 MST; 21h ago
>         Docs: man:sshd(8)
>               man:sshd_config(5)
>     Main PID: 359457 (sshd)
>

And what about the ip address and port number?

Check your ip:
$ ip addr

Check which ports are opened:
$ sudo ss -tl4p

Check which ip/port ssh is configured for
$ sudo sshd -T | grep list



ssh and Bitvise still fail t o connect
>

 Try to ping it from your Windows machine.
c:\> ping [your_linux_ip_addr]
does it work?
Then, try to connect to port 22 using telnet to see if connection could be
made.

In Admin powershell
PS C:\>  Enable-WindowsOptionalFeature -Online -FeatureName TelnetClient
PS C:\>  telnet [your_linux_ip_addr]

[toc] | [prev] | [next] | [standalone]

#231806 — Re: identifying my LInux machine on my LAN - some success

FromPaul Scott <waterhorse@ultrasw.com>
Date2021-02-17 18:20 +0100
SubjectRe: identifying my LInux machine on my LAN - some success
Message-ID<BJyEx-3Ux-1@gated-at.bofh.it>
In reply to#231805

[Multipart message — attachments visible in raw view] — view raw

On 2/17/21 10:03 AM, IL Ka wrote:
>
>
>     paul@Joy4:~/music/pima$ systemctl status ssh``
>
>     ● ssh.service - OpenBSD Secure Shell server
>           Loaded: loaded (/lib/systemd/system/ssh.service; enabled;
>     vendor
>     preset: enabled)
>           Active: active (running) since Tue 2021-02-16 11:53:13 MST;
>     21h ago
>             Docs: man:sshd(8)
>                   man:sshd_config(5)
>         Main PID: 359457 (sshd)
>
Before replying to your help below I can now connect from my Mac on the 
same LAN both with ssh to the IP of this machine and through my dynamic 
DNS address.  I'll try Bitvise from the local Windows machine soon.
>
> And what about the ip address and port number?
>
> Check your ip:
> $ ip addr
I should have replied ealier that the above gives the correct IP address.
>
> Check which ports are opened:
> $ sudo ss -tl4p
>
> Check which ip/port ssh is configured for
> $ sudo sshd -T | grep list
>
paul@Joy4:~/music/pima$ sudo sshd -T | grep list
listenaddress [::]:22
listenaddress 0.0.0.0:22
permitlisten any

I'll try the following in a while/

>
>  Try to ping it from your Windows machine.
> c:\> ping [your_linux_ip_addr]
> does it work?
> Then, try to connect to port 22 using telnet to see if connection 
> could be made.
>
> In Admin powershell
> PS C:\>  Enable-WindowsOptionalFeature -Online -FeatureName TelnetClient
> PS C:\>  telnet [your_linux_ip_addr]
>
Thank you,

Paul

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web