#307871* (?/48) ⚐Flag
<o11c> The problem with TCP jokes is that if you don't get them, I'll be up all night trying to make sure you do.
-!- Frost is away: Gone fishing.
<o11c> The problem with TCP jokes is that if you don't get them, I'll be up all night trying to make sure you do.
-!- Frost is away: Gone fishing.
<o11c> The problem with TCP jokes is that if you don't get them, I'll be up all night trying to make sure you do.
-!- Frost is away: Gone fishing.
<o11c> The problem with TCP jokes is that if you don't get them, I'll be up all night trying to make sure you do.
-!- Frost is away: Gone fishing.
<o11c> The problem with TCP jokes is that if you don't get them, I'll be up all night trying to make sure you do.
-!- Frost is away: Gone fishing.
<o11c> The problem with TCP jokes is that if you don't get them, I'll be up all night trying to make sure you do.
-!- Frost is away: Gone fishing.
<o11c> ... or maybe I'll just time out.
-!- Frost is away: Gone fishing.
<Frost> LMAO
<Frost> Time To Live exceeded there? :D
<o11c> I thought TTL is for a single packet?
-!- Frost is away: Gone fishing.
<Frost> well, yeah, it is per packet. :)
<o11c> anyway, I was wondering if I should consider your /away message like a TCP reset or something else
<Frost> LOL
<o11c> but then I decided it didn't matter, because of those spoofed TCP RSTs I was getting
<Frost> oh wow. I forgot about that.
<Frost> Did it really work to just drop the RSTs?
<o11c> I think soComment: Over /msg, of course (no multicast). I'd include timestamps but I didn't actually read the RFC to see what they should be.
|