Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

2016-10-11 11:57 GMT+08:00 Chris Caputo : > I have tested the above patch with 4.8.1, with and without nflog-size > defined in an iptables configuration, and it works well. > > The ulogd-2.0.5 segfaults no longer happen when nflog-size is not present > in a target. > > I recommend

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

2016-10-11 11:57 GMT+08:00 Chris Caputo : > I have tested the above patch with 4.8.1, with and without nflog-size > defined in an iptables configuration, and it works well. > > The ulogd-2.0.5 segfaults no longer happen when nflog-size is not present > in a target. > > I recommend this fix.

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

On Tue, 11 Oct 2016, Liping Zhang wrote: > Yes, thanks for clarifying this. There's a bug in kernel, can you try > this patch: > > diff --git a/net/netfilter/xt_NFLOG.c b/net/netfilter/xt_NFLOG.c > index 018eed7..8c069b4 100644 > --- a/net/netfilter/xt_NFLOG.c > +++ b/net/netfilter/xt_NFLOG.c >

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

On Tue, 11 Oct 2016, Liping Zhang wrote: > Yes, thanks for clarifying this. There's a bug in kernel, can you try > this patch: > > diff --git a/net/netfilter/xt_NFLOG.c b/net/netfilter/xt_NFLOG.c > index 018eed7..8c069b4 100644 > --- a/net/netfilter/xt_NFLOG.c > +++ b/net/netfilter/xt_NFLOG.c >

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

2016-10-11 2:33 GMT+08:00 Chris Caputo : >> >> What numbers did you specify after --nflog-size option? >> --nflog-size 0 or ...? If you want log the whole packet to >> the ulogd, please do not specify this nflog-size option. > > Not specifying nflog-size does not appear to log the

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

2016-10-11 2:33 GMT+08:00 Chris Caputo : >> >> What numbers did you specify after --nflog-size option? >> --nflog-size 0 or ...? If you want log the whole packet to >> the ulogd, please do not specify this nflog-size option. > > Not specifying nflog-size does not appear to log the whole packet...

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

On Mon, 10 Oct 2016, Liping Zhang wrote: > 2016-10-10 15:02 GMT+08:00 Chris Caputo : > > Program received signal SIGSEGV, Segmentation fault. > > 0x765fd18a in _interp_iphdr (pi=0x617f50, len=0) at > > ulogd_raw2packet_BASE.c:720 > > > > 715 static int

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

On Mon, 10 Oct 2016, Liping Zhang wrote: > 2016-10-10 15:02 GMT+08:00 Chris Caputo : > > Program received signal SIGSEGV, Segmentation fault. > > 0x765fd18a in _interp_iphdr (pi=0x617f50, len=0) at > > ulogd_raw2packet_BASE.c:720 > > > > 715 static int _interp_iphdr(struct

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

Hi Chris, 2016-10-10 15:02 GMT+08:00 Chris Caputo : > On Tue, 4 Oct 2016, Justin Piszcz wrote: >> kernel 4.8 with ulogd-2.0.5- IPs are no longer logged: >> >> Oct 4 17:51:30 atom INPUT_BLOCK IN=eth1 OUT= >> MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00 LEN=0 TOS=00 PREC=0x00 >>

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

Hi Chris, 2016-10-10 15:02 GMT+08:00 Chris Caputo : > On Tue, 4 Oct 2016, Justin Piszcz wrote: >> kernel 4.8 with ulogd-2.0.5- IPs are no longer logged: >> >> Oct 4 17:51:30 atom INPUT_BLOCK IN=eth1 OUT= >> MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00 LEN=0 TOS=00 PREC=0x00 >> TTL=0 ID=0

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

On Tue, 4 Oct 2016, Justin Piszcz wrote: > kernel 4.8 with ulogd-2.0.5- IPs are no longer logged: > > Oct 4 17:51:30 atom INPUT_BLOCK IN=eth1 OUT= > MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00 LEN=0 TOS=00 PREC=0x00 > TTL=0 ID=0 PROTO=0 MARK=0 > Oct 4 17:51:31 atom INPUT_BLOCK IN=eth1 OUT= >

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

On Tue, 4 Oct 2016, Justin Piszcz wrote: > kernel 4.8 with ulogd-2.0.5- IPs are no longer logged: > > Oct 4 17:51:30 atom INPUT_BLOCK IN=eth1 OUT= > MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00 LEN=0 TOS=00 PREC=0x00 > TTL=0 ID=0 PROTO=0 MARK=0 > Oct 4 17:51:31 atom INPUT_BLOCK IN=eth1 OUT= >

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

On Tue, Oct 4, 2016 at 8:58 PM, Liping Zhang wrote: > Hi Justin, > > 2016-10-05 6:02 GMT+08:00 Justin Piszcz : >> Hello, >> [ .. ] > > Which one are you using? iptables or nftables? # iptables -V iptables v1.6.0 > > Could you please paste the

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

On Tue, Oct 4, 2016 at 8:58 PM, Liping Zhang wrote: > Hi Justin, > > 2016-10-05 6:02 GMT+08:00 Justin Piszcz : >> Hello, >> [ .. ] > > Which one are you using? iptables or nftables? # iptables -V iptables v1.6.0 > > Could you please paste the related iptables/nftables rules here? Rules:

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

Hi Justin, 2016-10-05 6:02 GMT+08:00 Justin Piszcz : > Hello, > > kernel 4.8 with ulogd-2.0.5- IPs are no longer logged: > > Oct 4 17:51:30 atom INPUT_BLOCK IN=eth1 OUT= > MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00 LEN=0 TOS=00 PREC=0x00 > TTL=0 ID=0 PROTO=0 MARK=0 >

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

Hi Justin, 2016-10-05 6:02 GMT+08:00 Justin Piszcz : > Hello, > > kernel 4.8 with ulogd-2.0.5- IPs are no longer logged: > > Oct 4 17:51:30 atom INPUT_BLOCK IN=eth1 OUT= > MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00 LEN=0 TOS=00 PREC=0x00 > TTL=0 ID=0 PROTO=0 MARK=0 > Oct 4 17:51:31 atom

kernel v4.8: iptables logs are truncated with the 4.8 kernel?

Hello, kernel 4.8 with ulogd-2.0.5- IPs are no longer logged: Oct 4 17:51:30 atom INPUT_BLOCK IN=eth1 OUT= MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00 LEN=0 TOS=00 PREC=0x00 TTL=0 ID=0 PROTO=0 MARK=0 Oct 4 17:51:31 atom INPUT_BLOCK IN=eth1 OUT= MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00

kernel v4.8: iptables logs are truncated with the 4.8 kernel?

Hello, kernel 4.8 with ulogd-2.0.5- IPs are no longer logged: Oct 4 17:51:30 atom INPUT_BLOCK IN=eth1 OUT= MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00 LEN=0 TOS=00 PREC=0x00 TTL=0 ID=0 PROTO=0 MARK=0 Oct 4 17:51:31 atom INPUT_BLOCK IN=eth1 OUT= MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00