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.

  • wise_pancake@lemmy.ca
    link
    fedilink
    arrow-up
    1
    ·
    7 months ago

    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.

    • jet@hackertalks.comOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 months 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