summaryrefslogtreecommitdiff
path: root/net/netfilter/xt_TPROXY.c
diff options
context:
space:
mode:
authorPablo Neira Ayuso <pablo@netfilter.org>2015-03-02 01:10:28 +0100
committerPablo Neira Ayuso <pablo@netfilter.org>2015-03-19 11:14:48 +0100
commit4017a7ee693d1cae6735c0dac21594a7c6416c4c (patch)
tree1ff0e2930ba407497e9ed56839de227c9f3c5b33 /net/netfilter/xt_TPROXY.c
parentd6b6cb1d3e6f78d55c2d4043d77d0d8def3f3b99 (diff)
netfilter: restore rule tracing via nfnetlink_log
Since fab4085 ("netfilter: log: nf_log_packet() as real unified interface"), the loginfo structure that is passed to nf_log_packet() is used to explicitly indicate the logger type you want to use. This is a problem for people tracing rules through nfnetlink_log since packets are always routed to the NF_LOG_TYPE logger after the aforementioned patch. We can fix this by removing the trace loginfo structures, but that still changes the log level from 4 to 5 for tracing messages and there may be someone relying on this outthere. So let's just introduce a new nf_log_trace() function that restores the former behaviour. Reported-by: Markus Kötter <koetter@rrzn.uni-hannover.de> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'net/netfilter/xt_TPROXY.c')
0 files changed, 0 insertions, 0 deletions