Linux Netfilter discussions
 help / color / mirror / Atom feed
From: James Mullens <mullensja@ornl.gov>
To: Josh.Berry@compucom.com, netfilter@lists.netfilter.org
Subject: RE: IPTables State Tracking
Date: Fri, 29 Aug 2003 20:11:13 -0400	[thread overview]
Message-ID: <00d601c36e8b$394be310$7309db80@ornl.gov> (raw)
In-Reply-To: <0C7C6E1720E8D74FB52EBEF93649730A0116BF07@2k099exm01.compucom.local>


I believe that a UDP packet that passes through the filters opens a 30
second window for replies.  If a reply comes this is considered to be a
conversation and the window is extended to 180 seconds.  I think the
window is extended as long as the conversation continues.  

For ICMP I believe only types echo, timestamp, info request, and address
can open a 30 second window for a single reply.  The window is closed
when a reply is received.  

This is from netfilter Red Hat 8, kernel 2.4.18.  

Someone who has actually worked on the code may know better.

jim mullens

-----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 10:39
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





  reply	other threads:[~2003-08-30  0:11 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 [this message]
2003-08-30  0:33 ` Chris Brenton
2003-08-30  3:41 ` Mark E. Donaldson

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='00d601c36e8b$394be310$7309db80@ornl.gov' \
    --to=mullensja@ornl.gov \
    --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