From: "Daniel F. Chief Security Engineer -" <danielf@supportteam.net>
To: Peteris Krumins <newsgroups@lf.lv>, netfilter@lists.netfilter.org
Subject: Re: IP Fragmentation
Date: Mon, 31 Mar 2003 12:41:37 -0600 [thread overview]
Message-ID: <200303311241.37811.danielf@supportteam.net> (raw)
In-Reply-To: <127503161447.20030331000615@lf.lv>
Depends on your network and weather or not you care to be rfc compliant.
I see real fragmented traffic all the time. I choose not to block it. Because
it would break stuff that our customers need to use. So i just keep an eye on
fragmentation and watch fro abuse of it. We host 125,000 web sites, and use
iptables on our Firewalls (8).
On Sunday 30 March 2003 15:06, Peteris Krumins wrote:
> Hi,
>
> How often does IP Fragmentation occur?
> Is it safe to restrict any fragmented packets to 'come' into my
> network?
>
>
> P.Krumins
--
Daniel Fairchild - Chief Security Engineer | danielf@supportteam.net
prev parent reply other threads:[~2003-03-31 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-30 21:06 IP Fragmentation Peteris Krumins
2003-03-31 18:41 ` Daniel F. Chief Security Engineer - [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=200303311241.37811.danielf@supportteam.net \
--to=danielf@supportteam.net \
--cc=netfilter@lists.netfilter.org \
--cc=newsgroups@lf.lv \
/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