From: Patrick McHardy <kaber@trash.net>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
ak@suse.de, herbert@gondor.apana.org.au
Subject: Re: ip_finish_output2: No header cache and no neighbour! in 2.6.15-git7
Date: Sun, 22 Jan 2006 15:07:01 +0100 [thread overview]
Message-ID: <43D39185.4070808@trash.net> (raw)
In-Reply-To: <20060119.235114.41595062.davem@davemloft.net>
David S. Miller wrote:
> From: Andi Kleen <ak@suse.de>
> Date: Fri, 20 Jan 2006 08:15:39 +0100
>
>>Sorry for the delay in testing. Looks good so far. I'm running with SNAT
>>and the patch and the messages haven't appeared. Will keep it running
>>for longer, but previously they would have started already, so it's probably
>>ok now.
>
>
> Thanks for testing Andi.
>
> Patrick, please send me the final version of the fix you want me to
> put in when you get a chance.
I need to rethink this, my patch breaks SNAT to non-local IPs because
the NAT code will throw the packet away if ip_route_me_harder fails.
parent reply other threads:[~2006-01-22 14:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20060119.235114.41595062.davem@davemloft.net>]
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=43D39185.4070808@trash.net \
--to=kaber@trash.net \
--cc=ak@suse.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).