Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
The final boss of the internet
...this is Jackass.
Truncated IP. I don't remember the rules though. It's probably equivalent to 0.0.0.0 which is localhost.
@vintprox not really.
Yes it is situation dependent, but 0.0.0.0 has nothing to do with localhost.
It usually means "non routeable".
It's widely used to match all known addresses to a port (eg 0.0.0.0:80) or as an address for a default gateway.
There are things like Zero / mDNS / Bonjour / AVAHI / DHCP Discover / APIPA and I guess a few more who may utilize this.
localhost is DNS. And tricky, because localhost can be anything. Usually 127.0.0.1 on an loopback device, but it mustn't be that way.
korrat6461yAccording to Wikipedia it could be a truncated IP address, as @gronostaj said. The rule is simple: stretch the last value over the remaining bytes. So 0 is 0.0.0.0.
The same page also lists 0.0.0.0/8 as a a special address block indicating the current network. However, according to RFC1122 it's only valid as the source address of an IP packet and only during initialization (Section 18.104.22.168).
That RFC also says that some hosts use 0.0.0.0 as a broadcast address, and therefore it should be accepted as such (Section 3.3.6).
But 0 could also be a hostname (RFC1123, Section 2.1).
Thanks everyone, though what I cannot understand, I have lots of http only connections tracked and they are all for one second duration. Even though I have nginx force redirection https and drop all connections made to IP instead of domain