Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A...
by U8dcN7vx on Tuesday October 29, 2019 @12:13AM
(#21384205)
I raise you ...
$ ping 1.1 PING 1.1 (1.0.0.1) 56(84) bytes of data. 64 bytes from 1.0.0.1: icmp_seq=1 ttl=56 time=26.0 ms ...
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A...
by chmod775 on Tuesday October 29, 2019 @12:23AM
(#21384230)
I raise you ...
$ ping 0
PING 0 (127.0.0.1) 56(84) bytes of data.
Note that this may default to 0.0.0.0 instead depending on what you're running, which is technically the correct interpretation. I'm not sure who is doing the shenanigans here.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A...
by U8dcN7vx on Tuesday October 29, 2019 @12:28AM
(#21384246)
Touche!
All zeros is self, which is to say generally the same as 127.1.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A...
by ATsch on Tuesday October 29, 2019 @01:58AM
(#21384551)
Neat, I didn't know about this. If we relax the restrictions on being publicly routed, I can raise you
$ ping ::
PING ::(::) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.071 ms
though, shorter by one character.
While automatically assigned IPv6 addresses will usually use the full 128 bits (last half is random), manually assigned addresses usually don't. So e.g. one of my servers is 2a00:1234:8::10, which is pretty easy to remember. There's going to be no way around memorizing the first two or three colon sections, which are assigned to you, but the last part is going to be as easy to remember as you make it.
2600::1, owned by sprint, which is the shortest pingable IP address I know, is exactly as long as 1.1.1.1, the shortest possible IPv4 address.