From: Eric Leblond <regit@inl.fr>
To: christopher.f.ulherr@exgate.tek.com
Cc: netfilter@lists.netfilter.org
Subject: Re: logging of successful tcp connections
Date: Fri, 22 Apr 2005 17:14:14 +0200 [thread overview]
Message-ID: <1114182854.7835.1.camel@localhost.localdomain> (raw)
In-Reply-To: <F97948CF897D7B46802A18845A8B9BFD471A31@us-rich-m01.global.tektronix.net>
Le jeudi 21 avril 2005 à 09:38 -0700,
christopher.f.ulherr@exgate.tek.com a écrit :
> I would like to know if there is a way I can log only successful tcp
> connections. I'm only interested in successful (established)
> connections, and not just syn "connection attempts". I guess what I need
> is a way to log a single packet if it caused a state transition from NEW
> to ESTABLISHED. It would also be helpful to log the packet that
> terminated the connection (state change from established).
Have a look at :
http://regit.free.fr/nufw/content.php?article.11
We used this in the NuFW project(http://www.nufw.org) to track the state
of connections.
> In this
> manner, we could easily tell what connections were made, and their
> duration (and not rely on the userland application to log this info).
>
> I've looked into using the state matching, but couldn't achieve this
> specific functionality with that.
>
>
> Is there some trivial way to accomplish this I am overlooking?
>
>
> Thanks,
> Chris
>
next prev parent reply other threads:[~2005-04-22 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 16:38 logging of successful tcp connections christopher.f.ulherr
2005-04-22 15:14 ` Eric Leblond [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-21 17:28 christopher.f.ulherr
2005-04-21 19:58 ` Taylor, Grant
2005-04-21 22:28 christopher.f.ulherr
2005-04-21 23:55 ` Taylor Grant
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=1114182854.7835.1.camel@localhost.localdomain \
--to=regit@inl.fr \
--cc=christopher.f.ulherr@exgate.tek.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