Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
* [Cerowrt-devel] TCP TFO client behaviour
@ 2012-12-11 16:48 Ketan Kulkarni
  2012-12-11 16:59 ` [Cerowrt-devel] [Bloat] " Eric Dumazet
  2012-12-12 10:45 ` Eggert, Lars
  0 siblings, 2 replies; 8+ messages in thread
From: Ketan Kulkarni @ 2012-12-11 16:48 UTC (permalink / raw)
  To: bloat, cerowrt-devel

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

Hi,
I am testing tcp tfo behavior with httping client and polipo server.

One observation from my TFO testing  -If for a connection server sends a
cookie to client, client always does TFO for subsequent connections. This
is ok.

If for some reason, server stops supporting TFO (either because server got
restarted without TFO support (in my case) or because path changed and the
nw node is dropping packet with unknown syn option or stripping the
option), client does not clear up its cookie cache. It always sends data in
syn and server never acks the syn-data and client retransmits.

As per kernel code -if syn-data is not acked it is retransmitted
immediately - with the assumption first syn was dropped (but the assumption
server stopped supporting TFO might not have been considered)

My opinion is to flush the cookie for this server and re-attempt the cookie
"negotiation" on subsequent connection.

Your thoughts?

Thanks,
Ketan

[-- Attachment #2: Type: text/html, Size: 997 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2012-12-12 10:45 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-12-11 16:48 [Cerowrt-devel] TCP TFO client behaviour Ketan Kulkarni
2012-12-11 16:59 ` [Cerowrt-devel] [Bloat] " Eric Dumazet
2012-12-11 17:52   ` Dave Taht
2012-12-11 18:41     ` Rick Jones
2012-12-11 20:00       ` Dave Taht
2012-12-11 20:52         ` Rick Jones
2012-12-12  9:01     ` Ketan Kulkarni
2012-12-12 10:45 ` Eggert, Lars

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox