Geek Answers Handbook

Ping and use three octets of ipv4 address. Why does it work?

By chance I had a typo and I found that I can ping and ssh to the IP address 10.8.290... there is no right octet. Can someone explain this to me? Is this part of the protocol or some kind of linux-black-magic (I use Debian)?

user@ws:~$ ping -c3 10.8.290
PING 10.8.290 (10.8.1.34) 56(84) bytes of data.
64 bytes from 10.8.1.34: icmp_req=1 ttl=62 time=0.910 ms
64 bytes from 10.8.1.34: icmp_req=2 ttl=62 time=0.686 ms
64 bytes from 10.8.1.34: icmp_req=3 ttl=62 time=0.708 ms

--- 10.8.290 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.686/0.768/0.910/0.100 ms
user@ws:~$ ssh root@10.8.290
The authenticity of host '10.8.290 (10.8.1.34)' can't be established.
ECDSA key fingerprint is 21:bd:7e:fb:1e:6d:1e:c1:e9:11:c0:a9:73:a8:cf:85.
Are you sure you want to continue connecting (yes/no)? no
Host key verification failed.
+4
source share
1 answer

, 290 ip-. 0 255, 256. IPv4 4 , 290 , 4- → 290 - 256 = > 34

. ping target C inet_aton() (aton ascii ). pinging 10.8.1.34.

, , ping ( Windows, BSD) .

+3

More articles:


All Articles