netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emiliano Romero <emilianoromero@gmail.com>
To: netfilter-devel@vger.kernel.org
Subject: Re: Nat+Iptables+Tcp Keepalive Problem
Date: Thu, 04 Jun 2009 12:53:55 -0300	[thread overview]
Message-ID: <4A27EE13.5000303@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0906041656220.16139@blackhole.kfki.hu>

Jozsef Kadlecsik escribió:
> The TCP keepalived packet in the output above is invalid: it's sequence 
> number is wrong.
> 
> Best regards,
> Jozsef

Thanks for your reply Jozsef. After your reply I look at RFC 1122, It say:
"Some TCP implementations, however, have included a keep-alive 
mechanism.  To confirm that an idle connection is still active, these 
implementations send a probe segment designed to elicit a response from 
the peer TCP.  Such a segment generally contains SEG.SEQ = SND.NXT-1"
..."so that this SEG.SEQ will be outside the window.  Therefore, the 
probe causes the receiver to return an acknowledgment segment"

When I try with a linux box sending TCP KA, I see that this sets the ACK 
flag on TCP KeepAlive and that works correctly. I think that my remote 
equipments (GPRS Modems) are making TCP KA is the wrong way. Or maybe 
the GPRS Service Provider are touching my packets.

Thanks Again.

Regards
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-06-04 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 13:18 Nat+Iptables+Tcp Keepalive Problem Emiliano Romero
2009-06-04 14:59 ` Jozsef Kadlecsik
2009-06-04 15:53   ` Emiliano Romero [this message]
2009-06-04 16:35     ` Jozsef Kadlecsik

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=4A27EE13.5000303@gmail.com \
    --to=emilianoromero@gmail.com \
    --cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).