search for: logemu

...4 at opayq.com> --- I upgraded to ulogd 2.0.4 & kernel 3.17.2 but these did not make a difference, here's how the output looks now; Sat Nov 1 17:07:03 2014 <5> ulogd.c:843 building new pluginstance stack: 'log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU' Sat Nov 1 17:07:03 2014 <5> ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol 2 Sat Nov 1 17:07:03 2014 <5> ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol 10 Sat Nov 1 17:07:03 2014 <5> ulogd_inppkt_NFLOG.c:503 forci...

...horewall NFLOG(1,0,1), which if I'm understanding this correct, the first 1 gives me group 1 which I believe is what you said I need. And now with this setting I'm seeing logging... :) In ulog.conf I'm using; stack=log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU But I noticed I was still getting these messages; ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol 2 ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol 7 ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol 10 And I no...

...ing support - add 'rmem' configuration key to set the netlink socket rmem buffsize - don't use kernel header files for IP/TCP header definitions - various cosmetic cleanup to compile with -Wall - fix usage of libmysqlclient: call mysql_init() before mysql_real_connect() - don't have LOGEMU read the system time, ulogd_LOCAL.so does this already Please direct any questions / bug reports to the ulogd@lists.gnumonks.org mailinglist. Thanks for all your patience with my not-so-frequend release cycle. --=20 - Harald Welte <laforge@gnumonks.org> http://www.gnumonks.or...

...|WORKSFORME ------- Comment #3 from eric at inl.fr 2009-12-14 20:31 ------- With latest git tree, I did not manage to reproduce the problem. For the record, I've used the following stack: stack=log1:NFLOG,base1:BASE,mark1:MARK,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU stack=ct1:NFCT,mark1:MARK,op1:OPRINT -- Configure bugmail: http://bugzilla.netfilter.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

...14 15:39:20 2011 <5> ulogd.c:372 registering plugin `PRINTPKT' Mon Mar 14 15:39:20 2011 <5> ulogd.c:372 registering plugin `HWHDR' Mon Mar 14 15:39:20 2011 <5> ulogd.c:372 registering plugin `PRINTFLOW' Mon Mar 14 15:39:20 2011 <5> ulogd.c:372 registering plugin `LOGEMU' Mon Mar 14 15:39:20 2011 <5> ulogd.c:372 registering plugin `SYSLOG' Mon Mar 14 15:39:20 2011 <5> ulogd.c:372 registering plugin `XML' Mon Mar 14 15:39:20 2011 <5> ulogd.c:372 registering plugin `BASE' Mon Mar 14 15:39:20 2011 <8> ulogd.c:1189 not even a sin...

https://bugzilla.netfilter.org/show_bug.cgi?id=977 --- Comment #29 from Netbug <b1b30ee4 at opayq.com> --- Hi Eric, So it's ok to use; stack=log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU With #bind=1 commented out? I thought if you're going to use log2 then bind=1 had to be uncommented? -- You are receiving this mail because: You are watching all bug changes. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.netfilter.org/piper...

...cStart=/usr/sbin/ulogd --daemon --uid ulog --pidfile /run/ulog/ulogd.pid (code=exited, status=0/SUCCESS) Main PID: 24096 (code=exited, status=1/FAILURE) Mar 01 10:36:18 kevus ulogd[24096]: building new pluginstance stack: 'log1:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU' Mar 01 10:36:18 kevus ulogd[24096]: forcing unbind of existing log handler for protocol 2 Mar 01 10:36:18 kevus ulogd[24096]: forcing unbind of existing log handler for protocol 10 Mar 01 10:36:18 kevus ulogd[24096]: forcing unbind of existing log handler for protocol 7 Mar 01 10:36:18 kevus u...

...nd ulogd (under > Fedora 12 x86_64). A few days ago, I raised bug 651 re. ulogd 1.23. Since then, > I decided to try ulogd 2.0.0beta3 (as apparently I could then try using the > --nflog options in ebtables instead of the --ulog options.) This is proving a > lot more encouraging: the syslogemu plugin is working fine. However, when I try > to save the packets using the pcap plugin, I get lots of log messages like the > following: > > Wed May 12 15:33:25 2010 <7> ulogd_output_PCAP.c:170 Error during write: > Success > Wed May 12 15:33:25 2010 <5> ulogd.c:499...

...2 / DBI / table name Jan Andres (1): pcap: fix packet length handling Jan Engelhardt (20): build: move global automake options into configure.ac build: remove statements without obvious effect build: remove -fPIC flag build: remove unused $(all_includes) output/LOGEMU: resolve build warning build: default to not building static libraries build: propagate global CFLAGS build: no need for error message in PKG_CHECK_MODULES filter/HWHDR: remove redundant sizeof(char) build: avoid use of LIBS variable build: use appropriate locati...

http://bugzilla.netfilter.org/show_bug.cgi?id=793 Summary: ulogd -d does not close all fds Product: ulogd Version: SVN (please provide timestamp) Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ulogd AssignedTo: netfilter-buglog at lists.netfilter.org