I once watched some police procedural show (don’t remember which copaganda it was exactly) where they were trying to track someone’s location online. Couldn’t stop laughing when they showed an IPv4 address starting with 624.
Mind you, that’s for the same reason all American phone numbers in shows have a 555 prefix – showing a real address could lead to liability if e.g. someone tries to launch an attack on that address they saw on TV.
Unlike phone numbering schemes, the IPv4 address space has no well-known area reserved for fictitious addresses. Sure, you could use something like 192.0.2.0/24, 198.51.100.0/24, or 203.0.113.0/24 (test networks for use in documentation), but those aren’t well-known outside of certain circles.
So they just go with completely invalid addresses because that’s easy.
The Chad move would be to have one such scene that looks normal to casual observers, but then turns out the hacker has an automated scanning tool running in the background of the screen, while they’re just typing nonsense in the command prompt.
If we go outside of dottted decimal notation of IPv4, we can have addresses starting with 624. They can also be in decimal, octal, and hexadecimal.
Oh, and IPv4 also supports shortening from middle right in dotted decimal. For example, 127.0.0.1 is too long, often you may be able to use 127.1.
Or you can go to Cloudflare’s https://1.1/
While you can convert (or rather represent) an ipv4 as decimal, op indirectly stated that they were in dotted decimal notation and as such the leading 624 doesn’t work in that context.
Also shortening ipv4 is cursed, why must you share this knowledge?
Also also, curious to note that glibc parses 1 as ipv4 0.0.0.1 and not ipv6 ::1, probably because they predate ipv6.
I once watched some police procedural show (don’t remember which copaganda it was exactly) where they were trying to track someone’s location online. Couldn’t stop laughing when they showed an IPv4 address starting with 624.
Mind you, that’s for the same reason all American phone numbers in shows have a 555 prefix – showing a real address could lead to liability if e.g. someone tries to launch an attack on that address they saw on TV.
Unlike phone numbering schemes, the IPv4 address space has no well-known area reserved for fictitious addresses. Sure, you could use something like 192.0.2.0/24, 198.51.100.0/24, or 203.0.113.0/24 (test networks for use in documentation), but those aren’t well-known outside of certain circles.
So they just go with completely invalid addresses because that’s easy.
Just use 127.0.0.1 as the address and let hackers try to attack it.
I’m in
The Chad move would be to have one such scene that looks normal to casual observers, but then turns out the hacker has an automated scanning tool running in the background of the screen, while they’re just typing nonsense in the command prompt.
He’s too good, I can’t trace his ip!
They should’ve traced his ipv6, while 624::/16 isn’t currently allocated, it is at least usable if we need it.
Well, well, well.
If we go outside of dottted decimal notation of IPv4, we can have addresses starting with 624. They can also be in decimal, octal, and hexadecimal.
Oh, and IPv4 also supports shortening from middle right in dotted decimal. For example, 127.0.0.1 is too long, often you may be able to use 127.1.
Or you can go to Cloudflare’s https://1.1/
While you can convert (or rather represent) an ipv4 as decimal, op indirectly stated that they were in dotted decimal notation and as such the leading 624 doesn’t work in that context.
Also shortening ipv4 is cursed, why must you share this knowledge?
Also also, curious to note that glibc parses 1 as ipv4 0.0.0.1 and not ipv6 ::1, probably because they predate ipv6.