Found this in the depths of my storage. Not sure where its from but might improve the day of some people ^^

  • zqwzzleEnglish
    48·
    2 months ago

    Hello, would you like to hear a TCP joke?

    Edit: since no one is biting here’s the full joke

    “Hi, I’d like to hear a TCP joke.”
    “Hello, would you like to hear a TCP joke?”
    “Yes, I’d like to hear a TCP joke.”
    “Ok, I’ll tell you a TCP joke.”
    “Ok, I will hear a TCP joke.”
    “Are you ready to hear a TCP joke?”
    “Yes, I am ready to hear a TCP joke.”
    “Ok, I am about to send the TCP joke. It will last 10 seconds, it has two characters, it does not have a setting, it ends with a punchline.”
    “Ok, I am ready to get your TCP joke that will last 10 seconds, has two characters, does not have an explicit setting, and ends with a punchline.”
    “I’m sorry, your connection has timed out. Hello, would you like to hear a TCP joke?”

  • steventhedev@lemmy.world
    29·
    2 months ago

    To be fair, because of window size management it only takes 1% packet loss to cause a catastrophic drop in speed.

    Packet loss in TCP is only ever handled as a signal of extreme network congestion. It was never intended to go over a lossy link like wifi.

    • marcos@lemmy.world
      14·
      2 months ago

      Doesn’t wifi have its own retrial protocol? It’s been a long time since I’ve read the standard, but I think it’s almost lossless from the POV of TCP.

      • frezik@midwest.social
        17·
        2 months ago

        I believe so, yes. Every 802.11 frame is effectively ACK’d. Makes a mockery of OSI layering, but so does everything else.

      • steventhedev@lemmy.world
        6·
        2 months ago

        None built in from what I recall. That was from back in 2011, so it’s possible things changed since.

        Reading through, it looks like retries do exist, but remember that duplicate packets are treated as a window reset, so it’s possible that transmission succeeded but the ack was lost.

        I remember the project demos from the course though - one team implemented some form of fast retry on two laptops and had one guy walk out and away. With regular wifi he didn’t even make it to the end of the hall before the video dropped out. With their custom stack he made it out of the building before it went.

        I’ll need to dig through to find the name of what they did.

    • legion02@lemmy.world
      2·
      2 months ago

      On the other side of the spectrum packet loss is a key feature of some of the layers below tcp, like path-mtu discovery.

  • MrLLM@ani.socialEnglish
    24·
    2 months ago

    Found this in the depths of my storage. Not sure where its from but might improve the day of some people ^^

    I also remember someone posting that article

  • MelodiousFunk@slrpnk.net
    15·
    2 months ago

    Network monitoring engineers: explains for the umpteenth time that a node reporting down isn’t just a single dropped packet

    • Entropywins@lemmy.world
      4·
      2 months ago

      Geez…we all have learning experiences but I feel node down and packet dropped should be a clear distinction in the mind of anyone in IT…but people will surprise you