Bug 659678

Summary: [PATCH] update ulogd to version 2 for NFLOG support.
Product: [Fedora] Fedora Reporter: Stephen Beahm <stephenbeahm>
Component: ulogdAssignee: Martin Preisler <mpreisle>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: rawhideCC: upstream-release-monitoring
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-06 15:49:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
update ulogd to version 2 none

Description Stephen Beahm 2010-12-03 12:50:06 UTC
Created attachment 464566 [details]
update ulogd to version 2

ulogd verson 2 is needed for NFLOG suppport.

The ip6tables ULOG target has been obsoleted in favor of NFLOG. iptables is soon to follow.

I already submitted an selinux-policy patch for ulogd to Dan Walsh; He applied and released it.

Comment 1 Fedora Admin XMLRPC Client 2011-11-09 14:14:30 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Martin Preisler 2011-11-23 12:00:30 UTC
Hi Stephen,
many thanks for your patch!

I have applied and rebased it in the git package repo of ulogd. I have built just for rawhide for now. I will continue testing and aim to integrate ulogd 2.0.0-beta4 into f17.

One thing that bothers me is that ulogd doesn't work out of the box (one of the stack lines have to be uncommented in /etc/ulogd.conf) and user isn't notified of this.

koji build task: http://koji.fedoraproject.org/koji/taskinfo?taskID=3534529

Comment 3 Martin Preisler 2012-02-16 09:25:20 UTC
ulogd 2.0.0beta4 is available in branched f17 and rawhide.

Comment 4 Martin Preisler 2012-03-23 12:00:20 UTC
*** Bug 693696 has been marked as a duplicate of this bug. ***