24 Jun, 2016

1 commit

  • li->u.ulog.copy_len is currently ignored by the kernel, we should truncate
    the packet to either li->u.ulog.copy_len (if set) or copy_range before
    sending it to userspace. 0 is a valid input for copy_len, so add a new
    flag to indicate whether this was option was specified by the user or not.

    Add two flags to indicate whether nflog-size/copy_len was set or not.
    XT_NFLOG_F_COPY_LEN is for XT_NFLOG and NFLOG_F_COPY_LEN for nfnetlink_log

    On the userspace side, this was initially represented by the option
    nflog-range, this will be replaced by --nflog-size now. --nflog-range would
    still exist but does not do anything.

    Reported-by: Joe Dollard
    Reviewed-by: Josh Hunt
    Signed-off-by: Vishwanath Pai
    Signed-off-by: Pablo Neira Ayuso

    Vishwanath Pai
     

19 Sep, 2015

1 commit


15 May, 2013

1 commit

  • Since (69b34fb netfilter: xt_LOG: add net namespace support
    for xt_LOG), we hit this:

    [ 4224.708977] BUG: unable to handle kernel NULL pointer dereference at 0000000000000388
    [ 4224.709074] IP: [] ipt_log_packet+0x29/0x270

    when callling log functions from conntrack both in and out
    are NULL i.e. the net pointer is invalid.

    Adding struct net *net in call to nf_logfn() will secure that
    there always is a vaild net ptr.

    Reported as netfilter's bugzilla bug 818:
    https://bugzilla.netfilter.org/show_bug.cgi?id=818

    Reported-by: Ronald
    Signed-off-by: Hans Schillstrom
    Signed-off-by: Pablo Neira Ayuso

    Hans Schillstrom
     

12 May, 2010

1 commit


25 Mar, 2010

2 commits


04 Nov, 2008

1 commit


08 Oct, 2008

4 commits


29 Jan, 2008

3 commits


16 Oct, 2007

1 commit


11 Jul, 2007

3 commits


03 Dec, 2006

1 commit

  • Add new NFLOG target to allow use of nfnetlink_log for both IPv4 and IPv6.
    Currently we have two (unsupported by userspace) hacks in the LOG and ULOG
    targets to optionally call to the nflog API. They lack a few features,
    namely the IPv4 and IPv6 LOG targets can not specify a number of arguments
    related to nfnetlink_log, while the ULOG target is only available for IPv4.
    Remove those hacks and add a clean way to use nfnetlink_log.

    Signed-off-by: Patrick McHardy

    Patrick McHardy