I tried reading this, but every paragraph gave me the impression that I was looking at some cruel mixture of SCIgen and a Markov Generator.
Maybe it's just the the bad grammar, and obscenely absent punctuation. Oh-well, no matter... wasn't what I was looking for anyway.
This however, was quite interesting.
Caution: Unrelated stuff follows...
Six Stages of Debugging
- That can't happen.
- That doesn't happen on my machine.
- That shouldn't happen.
- Why does that happen?
- Oh, I see.
- How did that ever work?
The above appeared a brief moment before the following conversation took place, but I felt it was so amazing that it should be presented in the fashion of an ordered list.
Co-worker says:
10:56:24.716278 10.10.10.70.0 > 20.20.20.140.80: S [tcp sum ok] \
3601732956:3601732956(0) win 8192 (DF) (ttl 124, id 18507, len 48)
10:56:24.717652 10.10.10.70.1 > 20.20.20.140.80: S [tcp sum ok] \
1773456162:1773456162(0) win 8192 (DF) (ttl 124, id 18508, len 48)
You say:
buh?
Co-worker says:
Guess what that is?
You say:
That's one messed up looking pair of packets.
I'm guessing (read: Guess) they're windowsy related
but source port of 0, and 1 leads me to think the problem's coming from the router itself
Co-worker says:
Another customer's $1K/month internet service foiled by their own $20 dlink router, which
appears to, on reboot, start NAT sessions from port 0,1,2,3,4,...
You say:
Pfffff
