All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lev Stipakov <lstipakov@gmail.com>
To: linux-audit@redhat.com
Subject: Re: Auditing network traffic
Date: Thu, 21 Jan 2016 11:49:13 +0200	[thread overview]
Message-ID: <56A0A999.9090401@gmail.com> (raw)
In-Reply-To: <3655233.WIOkSfVQiu@x2>

Hi Steve,

Thank you for your comments! It seems that AUDIT target is better option 
than hooking syscalls and managing fds. I don't have to look inside 
traffic, just src/dest and bytes count is enough for me.

What would be the performance implications of that approach comparison 
to, say, libpcap option? Mostly I am concerned about logging part - 
seems that every packet produces NETFILTER_PKT record. I could not find 
any way to disable that, except probably disabling logging all together 
but that will break ausearch.

-Lev

  parent reply	other threads:[~2016-01-21  9:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 14:26 Auditing network traffic Lev Stipakov
2016-01-20 15:18 ` Steve Grubb
2016-01-20 15:29   ` Steve Grubb
2016-01-20 18:05     ` F Rafi
2016-01-20 18:30       ` Steve Grubb
2016-01-21  9:49     ` Lev Stipakov [this message]
2016-01-21 16:50       ` Steve Grubb
2016-01-21 20:49         ` Lev Stipakov
2016-01-21 22:09           ` Steve Grubb
2016-01-20 21:40 ` Paul Moore
2016-01-21  5:19 ` Peter Moody

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=56A0A999.9090401@gmail.com \
    --to=lstipakov@gmail.com \
    --cc=linux-audit@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.