64 bytes from 1.1.1.1: icmp_seq=65534 ttl=58 time=27.968 ms
64 bytes from 1.1.1.1: icmp_seq=65535 ttl=58 time=28.634 ms
64 bytes from 1.1.1.1: icmp_seq=0 ttl=58 time=28.161 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=28.966 ms
I had a terminal open, running ping to monitor my internet connection earlier. Today I noticed it was close to looping, and I set an alarm to make sure I could watch it loop back to 0.
I don’t know how dull it is, but I think I have 2**16 bits of dullness here.
You must log in or register to comment.
I had an old router where if the wifi was bad I would set the ping interval very short and DOS it into rebooting itself.
It worked and I didn’t have to stand up to reboot it.
I don’t know how dull it is, but I think I have 2**16 bits of dullness here.
Actually you just have 16 bits of unsigned dullness.
How many things will break if Cloudflare would block pings to 1.1.1.1.
Ohh, many things! I’m sure its hard coded by this point into lots of “robust” shell scripts and as a magic number in yaml files all over the world.
Cloud computing would die immediately
It was only a few years back (2018) that Cloudflare released 1.1.1.1. I remember reading a cool post about how when they turned it on (which I believe was earlier than this public announcement) they got significant volumes of traffic from all the equipment assuming 1.1.1.1 was not a valid address (up to that point it was not allocated to anyone).
I wish I could find the post but can’t find the one I was thinking of. It had details of the specific volume of traffic and the sources.
That’s amazing!
This is actually quite interesting, well done sir.
