From: Harald Welte <laforge@netfilter.org>
To: David Miller <davem@redhat.com>
Cc: Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Update: [PATCH 2.6] iptables MIRROR target fixes
Date: Fri, 25 Jul 2003 22:52:42 +0200 [thread overview]
Message-ID: <20030725205242.GH3244@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20030719142648.GS32475@sunbeam.de.gnumonks.org>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
Hi again, Dave!
On Sat, Jul 19, 2003 at 04:26:48PM +0200, Harald Welte wrote:
> This is the first of my 2.6 merge of the recent bugfixes (all tested
> against 2.6.0-test1). You might need to apply them incrementally
> (didn't test it in a different order).
Unfortunately I introduced a typo during the merge (which in turn
introduced a new bug).
Please incrementially apply the following patch, thanks.
--- linux-2.6.0-test1-nftest5/net/ipv4/netfilter/ipt_MIRROR.c 2003-07-19 16:13:56.000000000 +0200
+++ linux-2.6.0-test1-nftest6/net/ipv4/netfilter/ipt_MIRROR.c 2003-07-19 17:35:23.000000000 +0200
@@ -173,7 +173,7 @@
/* Don't let conntrack code see this packet:
* it will think we are starting a new
* connection! --RR */
- ip_direct_send(*pskb);
+ ip_direct_send(nskb);
return NF_DROP;
}
[now really off for OLS].
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2003-07-25 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030719142648.GS32475@sunbeam.de.gnumonks.org>
2003-07-25 20:52 ` Harald Welte [this message]
2003-07-25 22:22 ` David S. Miller
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=20030725205242.GH3244@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®