From: "Mark E. Donaldson" <markee@bandwidthco.com>
To: Josh.Berry@compucom.com, netfilter@lists.netfilter.org
Subject: RE: IPTables State Tracking
Date: Fri, 29 Aug 2003 20:41:10 -0700 [thread overview]
Message-ID: <DKEDJAAMDCDBHFKPBEMPCEPBCHAA.markee@bandwidthco.com> (raw)
In-Reply-To: <0C7C6E1720E8D74FB52EBEF93649730A0116BF07@2k099exm01.compucom.local>
Yes . . . the following is excerpted from the IPTables Tutorial:
"All of the connection tracking is done by special framework within the
kernel called conntrack. Most of the time, we need and want more specific
connection tracking than the default conntrack engine can maintain. Because
of this, there are also more specific parts of conntrack that handles the
TCP, UDP or ICMP protocols among others. These modules grabs specific,
unique, information from the packets, so that they may keep track of each
stream of data. The information that conntrack gathers is then used to tell
conntrack in which state the stream is currently in. For example, UDP
streams are, generally, uniquely identified by their destination IP address,
source IP address, destination port and source port."
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org]On Behalf Of
Josh.Berry@compucom.com
Sent: Friday, August 29, 2003 7:39 AM
To: netfilter@lists.netfilter.org
Subject: IPTables State Tracking
Does IPTables track virtual state of ICMP and UDP packets? I know that
UDP and ICMP are not stateful connections, but does IPTables perform
pseudo-stateful tracking of these connections such as some other
firewalls that basically timeout UDP/ICMP connections after a specific
time?
Thanks,
Josh Berry
Information Security Group
972-856-5402
prev parent reply other threads:[~2003-08-30 3:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 14:38 IPTables State Tracking Josh.Berry
2003-08-30 0:11 ` James Mullens
2003-08-30 0:33 ` Chris Brenton
2003-08-30 3:41 ` Mark E. Donaldson [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=DKEDJAAMDCDBHFKPBEMPCEPBCHAA.markee@bandwidthco.com \
--to=markee@bandwidthco.com \
--cc=Josh.Berry@compucom.com \
--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