I am often on one computer in my house and I would like to SSH to another one, but often don't know the IP address of the one I want to connect to. Is there a way, from the command line, to scan the local network so I can find the computer I want to connect to?
4
-
> but often don't know the IP address of the one I want to connect to Isn't this what DNS was invented for?– Chris McKeownApr 5, 2012 at 7:37
-
1If you don't know which computers are connected to your house's network, I think you might have a problem...– MassimoApr 5, 2012 at 8:31
-
1...and how do you know you're sshing into the right one? Time to sort out your ip addresses / name lookups.– symcbeanApr 5, 2012 at 9:00
-
7In defense of Andrew: yes, it's desirable to set unchanging IPs in the DHCP lease, and to have local names. However, consider the real-world case where I just carried a headless Ubuntu PC into the office and hooked it up. For the first connection, I wanted to find the IP without carrying a keyboard and monitor over to it. To symcbean's question, it was easy to know the correct PC based on the MAC address decoding (automatically done by nmap/Zenmap) to the motherboard manufacturer, and the operating system used. Sometimes you don't know the IP and need to find it.– PhrogzNov 12, 2015 at 18:27
Add a comment
|
6 Answers
Use "nmap" - this will tell you which hosts are up on a network, and indeed which have port 22 open. You could combine it with a few other tools (like grep) to produce more targeted output if need be.
Note: do this only on YOUR network. Running up nmap or its equivalents on someone else's network is considered bad form.
sudo nmap -p 22 192.168.0.0/24
answered Apr 5, 2012 at 7:07
-
bluebitter.de/portscn2.htm Use BluePortScan if you want a more simple thing than nmap– Gk.Apr 5, 2012 at 7:16
-
9
-
4
From the command line you could use:
sudo nmap -sS -p 22 192.168.10.0/24
Substitute for the local address space on your network. I sometimes use this when I plug in a headless rasberry pi and want to find where to ssh to.
-
12Exactly one of the use-cases that lead me to ask this question. Thanks!– AndrewNov 14, 2015 at 20:27
-
nmap -p 22 --open -sV 192.168.178.0/24
-
How is this different than the other answers? How do we know that is my local network?– chicksFeb 16, 2018 at 22:13
-
3It does not require
sudoand can be used with Android NetworkMapper Jul 17, 2018 at 15:05 -
11I prefer this answer. The addition of
--openremoved a lot of crud from the output and actually showed me the machine I was looking for. Oct 27, 2018 at 6:11 -
2adding
-oG -cleans up the output even more– user512619Sep 10, 2020 at 11:56 -
@VadymTyemirov for other's information it is the
-sSflag that requiressudo– icc97Mar 28 at 17:04
You can manually telnet each ip at port 22.
If successful you should see the OpenSSH version string.
The process of checking each ip in the subnet can be done by means of the 'for' directive.
I would advise against checking port 22 only. Not all SSH servers use port 22 by default. For instance, OpenSSH in Termux on my Android phone uses port 8022.
Instead, use nmap's powerful version detection feature, and check all ports:
% nmap -sV 192.168.68.0/24 | grep -wE '(scan report|ssh)'
Nmap scan report for 192.168.68.1
22/tcp open ssh Dropbear sshd (protocol 2.0)
Nmap scan report for 192.168.68.100
22/tcp open ssh Dropbear sshd 2015.67 (protocol 2.0)
Nmap scan report for 192.168.68.101
Nmap scan report for 192.168.68.103
Nmap scan report for 192.168.68.105
8022/tcp open ssh OpenSSH 9.1 (protocol 2.0)
Also, it's a common tactic among sysadmins to change services like SSH to a weird high port in an attempt to hide it. Although that doesn't really apply in your situation, since you probably administer your own LAN machines.
If you just want the hostnames/ips and don't want the other info:
sudo nmap -sS -p 22 192.168.1.0/24 | grep report
