netfilter: xt_NFLOG: nflog-range does not truncate packets
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 <jdollard@akamai.com> Reviewed-by: Josh Hunt <johunt@akamai.com> Signed-off-by: Vishwanath Pai <vpai@akamai.com> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
This commit is contained in:
committed by
Pablo Neira Ayuso
parent
e1dbbc5907
commit
7643507fe8
@@ -6,9 +6,13 @@
|
||||
#define XT_NFLOG_DEFAULT_GROUP 0x1
|
||||
#define XT_NFLOG_DEFAULT_THRESHOLD 0
|
||||
|
||||
#define XT_NFLOG_MASK 0x0
|
||||
#define XT_NFLOG_MASK 0x1
|
||||
|
||||
/* This flag indicates that 'len' field in xt_nflog_info is set*/
|
||||
#define XT_NFLOG_F_COPY_LEN 0x1
|
||||
|
||||
struct xt_nflog_info {
|
||||
/* 'len' will be used iff you set XT_NFLOG_F_COPY_LEN in flags */
|
||||
__u32 len;
|
||||
__u16 group;
|
||||
__u16 threshold;
|
||||
|
||||
Reference in New Issue
Block a user