From: Anil Gunturu <anil@mistletoetech.com>
To: netfilter@lists.netfilter.org
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: Re: tcp conn tracking
Date: Mon, 15 Jan 2007 08:57:20 -0800 (PST) [thread overview]
Message-ID: <25296252.199981168880240692.JavaMail.root@smtp1.mistletoetech.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701150843190.9059@blackhole.kfki.hu>
Thank you for the response.
So, ftp connection tracking doesn't work always. Just curious about what is the rationale for such a solution? Is it assumed that if the packet with PORT command is fragmented someone is deliberatly attacking the system?
Cheers,
-Anil
----- Original Message -----
From: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
To: Anil Gunturu <anil@mistletoetech.com>
Cc: netfilter@lists.netfilter.org
Sent: Sunday, January 14, 2007 11:47:23 PM GMT-0800 US/Pacific
Subject: Re: tcp conn tracking
On Sun, 14 Jan 2007, Anil Gunturu wrote:
> Does the tcp connection tracking reorder and reassemble the tcp data. I
> am particularly interested in how ip_conntrack_ftp works, if the tcp
> data for port commnad comes in two different out-of-order segments.
The connection tracking in netfilter defragments fragmented packets but
does not reorder out of order packets. Moreover FTP connection tracking
won't work on PORT/etc commands which arrive in multiple (not fragmented)
packets, even if those are in order.
Best regards,
Jozsef
-
E-mail : kadlec@blackhole.kfki.hu, kadlec@sunserv.kfki.hu
PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address : KFKI Research Institute for Particle and Nuclear Physics
H-1525 Budapest 114, POB. 49, Hungary
next prev parent reply other threads:[~2007-01-15 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 5:14 tcp conn tracking Anil Gunturu
2007-01-15 7:47 ` Jozsef Kadlecsik
2007-01-15 16:57 ` Anil Gunturu [this message]
2007-01-15 16:59 ` Jan Engelhardt
2007-01-15 17:24 ` Anil Gunturu
2007-01-15 18:42 ` Jozsef Kadlecsik
2007-01-15 18:49 ` Grant Taylor
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=25296252.199981168880240692.JavaMail.root@smtp1.mistletoetech.com \
--to=anil@mistletoetech.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter@lists.netfilter.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