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

Groups > comp.os.linux.networking > #3903 > unrolled thread

ping to non-existent addresses on the local loopback succeed!

Started by"Charles T. Smith" <cts.private.yahoo@gmail.com>
First post2016-11-02 15:19 +0000
Last post2016-11-03 08:51 +0000
Articles 7 — 4 participants

Back to article view | Back to comp.os.linux.networking

Contents

  ping to non-existent addresses on the local loopback succeed! "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2016-11-02 15:19 +0000
    Re: ping to non-existent addresses on the local loopback succeed! "Carlos E.R." <robin_listas@invalid.es> - 2016-11-02 16:26 +0100
      Re: ping to non-existent addresses on the local loopback succeed! "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2016-11-02 15:39 +0000
        Re: ping to non-existent addresses on the local loopback succeed! Andy Furniss <spam@spam> - 2016-11-02 15:52 +0000
          Re: ping to non-existent addresses on the local loopback succeed! "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2016-11-02 16:32 +0000
      Re: ping to non-existent addresses on the local loopback succeed! Pascal Hambourg <pascal@plouf.fr.eu.org> - 2016-11-03 07:41 +0100
        Re: ping to non-existent addresses on the local loopback succeed! "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2016-11-03 08:51 +0000

#3903 — ping to non-existent addresses on the local loopback succeed!

From"Charles T. Smith" <cts.private.yahoo@gmail.com>
Date2016-11-02 15:19 +0000
Subjectping to non-existent addresses on the local loopback succeed!
Message-ID<nvd05h$pk3$1@dont-email.me>
Can someone explain to me why?

E.g.

$ ping 127.0.2.1
PING 127.0.2.1 (127.0.2.1) 56(84) bytes of data.
64 bytes from 127.0.2.1: icmp_seq=1 ttl=64 time=0.064 ms
...

Or

$ sudo ifconfig lo:130 10.1.35.130

$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet 10.1.35.130/24 scope global lo:130
       valid_lft forever preferred_lft forever
    inet 10.1.35.131/24 scope global secondary lo:131
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
...

>ping 10.1.35.144
PING 10.1.35.144 (10.1.35.144) 56(84) bytes of data.
64 bytes from 10.1.35.144: icmp_seq=1 ttl=64 time=0.062 ms
...

[toc] | [next] | [standalone]

#3904

From"Carlos E.R." <robin_listas@invalid.es>
Date2016-11-02 16:26 +0100
Message-ID<27dped-40d.ln1@Telcontar.valinor>
In reply to#3903
On 2016-11-02 16:19, Charles T. Smith wrote:
> Can someone explain to me why?
> 
> E.g.
> 
> $ ping 127.0.2.1
> PING 127.0.2.1 (127.0.2.1) 56(84) bytes of data.
> 64 bytes from 127.0.2.1: icmp_seq=1 ttl=64 time=0.064 ms
> ...

Works as expected.
All 127.*.*.* addresses do exist.

-- 
Cheers, Carlos.

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

#3905

From"Charles T. Smith" <cts.private.yahoo@gmail.com>
Date2016-11-02 15:39 +0000
Message-ID<nvd1ar$pk3$2@dont-email.me>
In reply to#3904
On Wed, 02 Nov 2016 16:26:58 +0100, Carlos E.R. wrote:

> On 2016-11-02 16:19, Charles T. Smith wrote:
>> Can someone explain to me why?
>> 
>> E.g.
>> 
>> $ ping 127.0.2.1
>> PING 127.0.2.1 (127.0.2.1) 56(84) bytes of data.
>> 64 bytes from 127.0.2.1: icmp_seq=1 ttl=64 time=0.064 ms
>> ...
> 
> Works as expected.
> All 127.*.*.* addresses do exist.

Thank you.

But why?

Where would I look for an explanation of that?

Is there a keyword for that phenomena that I can use to search the internet?

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

#3906

FromAndy Furniss <spam@spam>
Date2016-11-02 15:52 +0000
Message-ID<e-6dnWGDcLBFlofFnZ2dnUU78fWdnZ2d@brightview.co.uk>
In reply to#3905
Charles T. Smith wrote:
> On Wed, 02 Nov 2016 16:26:58 +0100, Carlos E.R. wrote:
>
>> On 2016-11-02 16:19, Charles T. Smith wrote:
>>> Can someone explain to me why?
>>>
>>> E.g.
>>>
>>> $ ping 127.0.2.1 PING 127.0.2.1 (127.0.2.1) 56(84) bytes of
>>> data. 64 bytes from 127.0.2.1: icmp_seq=1 ttl=64 time=0.064 ms
>>> ...
>>
>> Works as expected. All 127.*.*.* addresses do exist.
>
> Thank you.
>
> But why?
>
> Where would I look for an explanation of that?
>
> Is there a keyword for that phenomena that I can use to search the
> internet?

https://en.wikipedia.org/wiki/Localhost

"The IPv4 loopback addresses are reserved within the IPv4 namespace by
the IETF Special Use IPv4 Addresses standard (RFC 5735).[4] The
reservation can be traced back to the November, 1986 Assigned Numbers
standard (RFC 990), which was issued at a time when the first byte of
the IP address was a signed network number that was the only portion of
the address assigned by the IETF. Reserving its highest possible network
number (127) for loopback testing eventually resulted in the excessive
reservation of 16,777,214 loopback addresses."

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

#3907

From"Charles T. Smith" <cts.private.yahoo@gmail.com>
Date2016-11-02 16:32 +0000
Message-ID<nvd4fr$pk3$3@dont-email.me>
In reply to#3906
On Wed, 02 Nov 2016 15:52:39 +0000, Andy Furniss wrote:

> Charles T. Smith wrote:
>> On Wed, 02 Nov 2016 16:26:58 +0100, Carlos E.R. wrote:
>>
>>> On 2016-11-02 16:19, Charles T. Smith wrote:
>>>> Can someone explain to me why?
>>>>
>>>> E.g.
>>>>
>>>> $ ping 127.0.2.1 PING 127.0.2.1 (127.0.2.1) 56(84) bytes of
>>>> data. 64 bytes from 127.0.2.1: icmp_seq=1 ttl=64 time=0.064 ms
>>>> ...
>>>
>>> Works as expected. All 127.*.*.* addresses do exist.
>>
>> Thank you.
>>
>> But why?
>>
>> Where would I look for an explanation of that?
>>
>> Is there a keyword for that phenomena that I can use to search the
>> internet?
> 
> https://en.wikipedia.org/wiki/Localhost
> 
> "The IPv4 loopback addresses are reserved within the IPv4 namespace by
> the IETF Special Use IPv4 Addresses standard (RFC 5735).[4] The
> reservation can be traced back to the November, 1986 Assigned Numbers
> standard (RFC 990), which was issued at a time when the first byte of
> the IP address was a signed network number that was the only portion of
> the address assigned by the IETF. Reserving its highest possible network
> number (127) for loopback testing eventually resulted in the excessive
> reservation of 16,777,214 loopback addresses."

:-)  Okay, that's good to know - it's just a fact of life.  Thank you very much!

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

#3908

FromPascal Hambourg <pascal@plouf.fr.eu.org>
Date2016-11-03 07:41 +0100
Message-ID<nvem7o$204q$1@saria.nerim.net>
In reply to#3904
Le 02/11/2016 à 16:26, Carlos E.R. a écrit :
> On 2016-11-02 16:19, Charles T. Smith wrote:
>> Can someone explain to me why?
>>
>> E.g.
>>
>> $ ping 127.0.2.1
>> PING 127.0.2.1 (127.0.2.1) 56(84) bytes of data.
>> 64 bytes from 127.0.2.1: icmp_seq=1 ttl=64 time=0.064 ms
>> ...
>
> Works as expected.

As per the following route in the "local" routing table :

ip route show table local
...
local 127.0.0.0/8 dev lo  proto kernel  scope host  src 127.0.0.1
...

Note that all these addresses are reserved to the local host, but a host 
does not have to use them all. Linux does.

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

#3909

From"Charles T. Smith" <cts.private.yahoo@gmail.com>
Date2016-11-03 08:51 +0000
Message-ID<nvetra$jfc$1@dont-email.me>
In reply to#3908
On Thu, 03 Nov 2016 07:41:59 +0100, Pascal Hambourg wrote:

> Le 02/11/2016 à 16:26, Carlos E.R. a écrit :
>> On 2016-11-02 16:19, Charles T. Smith wrote:
>>> Can someone explain to me why?
>>>
>>> E.g.
>>>
>>> $ ping 127.0.2.1
>>> PING 127.0.2.1 (127.0.2.1) 56(84) bytes of data.
>>> 64 bytes from 127.0.2.1: icmp_seq=1 ttl=64 time=0.064 ms
>>> ...
>>
>> Works as expected.
> 
> As per the following route in the "local" routing table :
> 
> ip route show table local
> ...
> local 127.0.0.0/8 dev lo  proto kernel  scope host  src 127.0.0.1
> ...
> 
> Note that all these addresses are reserved to the local host, but a host 
> does not have to use them all. Linux does.

Thank you.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.networking

csiph-web