From: Eric Leblond <eric@inl.fr>
To: Pierre Chifflier <chifflier@edenwall.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [ULOGD2] UNIXSOCK plugin (v5b)
Date: Sat, 23 Oct 2010 11:54:29 +0200 [thread overview]
Message-ID: <1287827669.4463.0.camel@ice-age> (raw)
In-Reply-To: <1287575092-454-1-git-send-email-chifflier@edenwall.com>
[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]
Hi,
Le mercredi 20 octobre 2010 à 13:44 +0200, Pierre Chifflier a écrit :
> Hi,
>
> First of all, sorry for the long time with no updates on this patch.
> This is a resend of the patches for the UNIXSOCK input plugin for ulogd2.
>
> Please let me know if there are any issues.
Patches pushed to the git tree.
BR,
>
> PS: hope you enjoyed the oowall presentation :)
>
>
>
> Changes for v5:
> - align all structures on 64 bits instead of 32
> This has been tested on a sparc64 (thanks to Jan)
> - update pcap2ulog to handle different pcap formats
>
> Changes for v4:
> - use structures instead of reading integers directly
> - all structures and fields are now aligned (4 bytes)
> - update pcap2ulog script to use aligned data as well
>
> Changes for v3:
> - if the bufsize value (from conf) is 0, try to guess the buffer size
> using getsockopt(SOL_SOCKET, SO_RCVBUF ..)
> - set default path to /var/run/ulogd/ulogd2.sock with mode 0600
> - add new configuration options perms, owner and group to be able
> to set these parameters on the created socket
> - change the input algorithm to make it more robust against junk data (which
> can happen if the client is desynchronized)
> - fixed a few bugs
>
> Description:
>
> [1] add new input plugin UNISOCK, using a unix socket. This allows userspace
> applications to send packets to ulogd, for example to send packets offline.
> It uses a key-length-value protocol to handle optional fields or extensions.
>
> [2] is a Perl script to load a PCAP file and send it to ulogd using the
> UNIXSOCK plugin.
>
> Pierre
--
Eric Leblond <eric@inl.fr>
INL: http://www.inl.fr/
NuFW: http://www.nufw.org/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2010-10-26 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 11:44 [ULOGD2] UNIXSOCK plugin (v5b) Pierre Chifflier
2010-10-20 11:44 ` [PATCH 1/2] Add new input plugin UNIXSOCK Pierre Chifflier
2010-10-20 11:44 ` [PATCH 2/2] Add helper script pcap2ulog Pierre Chifflier
2010-10-23 9:54 ` Eric Leblond [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=1287827669.4463.0.camel@ice-age \
--to=eric@inl.fr \
--cc=chifflier@edenwall.com \
--cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).