All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Harald Welte <laforge@netfilter.org>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: [PATCH]: clear nf_debug for ipsec tunnel packets
Date: Mon, 25 Aug 2003 00:35:31 +0200	[thread overview]
Message-ID: <3F493DB3.9060607@trash.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 260 bytes --]

Hi Harald,

this patch for 2.6 clears nf_debug in ip_local_deliver_finish so the
"hook ... already set" message in nf_hook_slow won't get triggered for
decapsulated ipsec-tunnel packets when passing them through the network
stack again.

Best regards,
Patrick

[-- Attachment #2: pom-2.6-tunnel-debug.diff --]
[-- Type: text/plain, Size: 1317 bytes --]

diff -urN a/patch-o-matic_2.5/pending/27-ipsec_tunnel-nf_debug.diff b/patch-o-matic_2.5/pending/27-ipsec_tunnel-nf_debug.diff
--- a/patch-o-matic_2.5/pending/27-ipsec_tunnel-nf_debug.diff	1970-01-01 01:00:00.000000000 +0100
+++ b/patch-o-matic_2.5/pending/27-ipsec_tunnel-nf_debug.diff	2003-08-24 23:17:43.000000000 +0200
@@ -0,0 +1,11 @@
+===== net/ipv4/ip_input.c 1.17 vs edited =====
+--- 1.17/net/ipv4/ip_input.c	Mon Jun 16 17:11:36 2003
++++ edited/net/ipv4/ip_input.c	Sun Aug 24 23:11:36 2003
+@@ -201,6 +201,7 @@
+ 
+ #ifdef CONFIG_NETFILTER_DEBUG
+ 	nf_debug_ip_local_deliver(skb);
++	skb->nf_debug = 0;
+ #endif /*CONFIG_NETFILTER_DEBUG*/
+ 
+ 	__skb_pull(skb, ihl);
diff -urN a/patch-o-matic_2.5/pending/27-ipsec_tunnel-nf_debug.diff.help b/patch-o-matic_2.5/pending/27-ipsec_tunnel-nf_debug.diff.help
--- a/patch-o-matic_2.5/pending/27-ipsec_tunnel-nf_debug.diff.help	1970-01-01 01:00:00.000000000 +0100
+++ b/patch-o-matic_2.5/pending/27-ipsec_tunnel-nf_debug.diff.help	2003-08-24 23:34:23.000000000 +0200
@@ -0,0 +1,7 @@
+Author: Patrick McHardy <kaber@trash.net>
+Status: Working
+
+This patch clears nf_debug in ip_local_deliver_finish so the
+"hook ... already set" message in nf_hook_slow won't get triggered for
+decapsulated ipsec-tunnel packets when passing them through the network
+stack again.

                 reply	other threads:[~2003-08-24 22:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F493DB3.9060607@trash.net \
    --to=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.