public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Charles Bearden <Charles.F.Bearden@uth.tmc.edu>
Cc: netdev@vger.kernel.org
Subject: Re: TCP keepalives ignored by kernel when the contain timestamps
Date: Fri, 10 Jun 2011 18:54:30 +0200	[thread overview]
Message-ID: <1307724870.4044.20.camel@edumazet-laptop> (raw)
In-Reply-To: <4DF248C5.9050004@uth.tmc.edu>

Le vendredi 10 juin 2011 à 11:39 -0500, Charles Bearden a écrit :
> On 06/10/2011 11:17 AM, Eric Dumazet wrote:
> > Le vendredi 10 juin 2011 à 11:07 -0500, Charles Bearden a écrit :
> >
> >> You are correct: the checksums in the keepalives are broken, though they are
> >> correct in the other segments from the Win2008 server. I have updated the pastes
> >> linked to above with 'tcpdump -v' output. I apologize for missing that problem
> >> the first time around.
> >
> > Hmm, maybe its OK : If checksums are offloaded to NIC, tcpdump 'lies'
> > telling checksum is not OK, since tcpdump get a copy of the packet
> > before being handled by the NIC.
> >
> > You should take a tcpdump on the receiving machine (the machine that
> > apparently doesnt react to the keepalive probes)
> 
> I should have made this clear before: these dumps were captured on the machine 
> that is ignoring the keepalives ("Ubuntu.host" in the dumps) from the other host 
> ("Win200[38].host" in the dumps). If I understand tcp checksum offloading 
> correctly, it wouldn't play a role here.
> 

OK, thanks.

I am curious, could you check the payload byte included in the keepalive
probes has the value of last sent byte on the session ?

(linux send keepalive probes with no data, so implementing this
'feature' would need to keep track of this value in tcp socket)




  reply	other threads:[~2011-06-10 16:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 15:26 TCP keepalives ignored by kernel when the contain timestamps Charles Bearden
2011-06-10 13:56 ` Eric Dumazet
2011-06-10 15:10   ` Charles Bearden
2011-06-10 16:07     ` Charles Bearden
2011-06-10 16:17       ` Eric Dumazet
2011-06-10 16:39         ` Charles Bearden
2011-06-10 16:54           ` Eric Dumazet [this message]
2011-06-10 18:00             ` Charles Bearden
2011-06-10 18:04               ` Eric Dumazet
2011-06-10 18:13                 ` Charles Bearden
2011-06-10 18:41                   ` Eric Dumazet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1307724870.4044.20.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=Charles.F.Bearden@uth.tmc.edu \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox