Re: TCP LAST-ACK state broken in 2.4.17-pre2 [NEW DATA]

kuznet
2001-12-18T18:41:45Z

Hello!

> from the SYN exchange (about 200 ms). So, something is wrong?

Well, the guess was right and this is pleasant.

The only minor :-) question remained is to guess how rto could happen
to be at this value. I will think. Well, if you have some guesses,
please, tell me. Is this intel btw? I just see that other side
sends bogus misaligned tcp options... not a problem, but it can
be reason of funnyies with some probability.

Alexey