From: Nemeth Denes <nemeth.denes@iit.bme.hu>
To: vishesh <linuxtovishesh@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: sequence numbers in conntrack
Date: Sun, 10 Jan 2010 11:06:16 +0100 [thread overview]
Message-ID: <4B49A698.6080005@iit.bme.hu> (raw)
In-Reply-To: <1263096654.2614.1.camel@vishesh-laptop>
Hi
Sorry it was a typo it should be the following:
(host H is behind the NAT ....)
Thanks
vishesh wrote:
> On Sat, 2010-01-09 at 22:12 +0100, Nemeth Denes wrote:
>
>> Hello,
>>
>> Could someone help me to explain what does the conntack module do
>> in TCP connection negotiation in the following three cases: (host N is
>> behind the NAT and host P is on the other side of the NAT)
>>
>> A:
>> P sends a SYN to H and H replies with an SYN-ACK with an invalid
>> sequence number (If this passes normally through is it possible to
>> filter it out?)
>>
>> B:
>> P sends a SYN to H and H replies with non SYN-ACK (3-way-handshake)
>> or SYN (TCP simultaneous open) package
>>
>> C: If the "--random" option is given to the postrouting chain, what happens
>> if the clients use up all the ports?
>>
>> Many thanks,
>> Denes Nemeth
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe netfilter" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> Dear denes
> Do you mean N host where host H is mentioned ?
> thnks
>
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-01-10 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 21:12 sequence numbers in conntrack Nemeth Denes
2010-01-10 4:10 ` vishesh
2010-01-10 10:06 ` Nemeth Denes [this message]
2010-01-10 11:03 ` Nemeth Denes
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=4B49A698.6080005@iit.bme.hu \
--to=nemeth.denes@iit.bme.hu \
--cc=linuxtovishesh@gmail.com \
--cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.