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.

    • Dave@lemmy.nz
      1·
      3 hours ago

      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.

    • jetOPAEnglish
      12·
      10 hours ago

      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