From: Ramin Dousti <ramin@cannon.eng.us.uu.net>
To: Curtis Call <curtiscall@usa.net>
Cc: Ramin Dousti <ramin@cannon.eng.us.uu.net>,
Marcel de Boer <marceldb@luon.net>,
netfilter@lists.netfilter.org
Subject: Re: [Re: [FTP large file problem]]
Date: Fri, 18 Jul 2003 10:52:28 -0400 [thread overview]
Message-ID: <20030718145228.GC880@cannon.eng.us.uu.net> (raw)
In-Reply-To: <993HgRoIe8480S06.1058538844@cmsweb06.cms.usa.net>
Thanks but there I could find:
-----
If you are doing connection tracking or NAT, then all fragments will get merged back together before they reach the packet filtering code, so you need never worry about fragments.
-----
And I guess by default everybody is using "connection tracking" with netfilter.
Ramin
On Fri, Jul 18, 2003 at 08:34:04AM -0600, Curtis Call wrote:
> See:
>
> http://www.netfilter.org/documentation/HOWTO//packet-filtering-HOWTO-7.html#ss7.3
>
> Scroll down to 'Specifying fragments'. Looks like whether it is reassembled
> prior to the filter depends on a few different factors...
>
> Anyway, I was having problems with a local firewall filter stalling my large
> IMAP downloads. Permitting fragments did the trick...
prev parent reply other threads:[~2003-07-18 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 14:34 [Re: [FTP large file problem]] Curtis Call
2003-07-18 14:52 ` Ramin Dousti [this message]
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=20030718145228.GC880@cannon.eng.us.uu.net \
--to=ramin@cannon.eng.us.uu.net \
--cc=curtiscall@usa.net \
--cc=marceldb@luon.net \
--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