From: Patrick McHardy <kaber@trash.net>
To: Phil Oester <kernel@linuxace.com>
Cc: Harald Welte <laforge@netfilter.org>,
netfilter-devel@lists.netfilter.org,
Henrik Nordstrom <hno@marasystems.com>
Subject: Re: SO_ORIGINAL_DST does not work in nat/OUTPUT anymore
Date: Mon, 11 Jul 2005 01:54:18 +0200 [thread overview]
Message-ID: <42D1B52A.10200@trash.net> (raw)
In-Reply-To: <20050710222006.GA11812@linuxace.com>
Phil Oester wrote:
> I humbly re-resubmit my original patch.
It doesn't apply to the current tree. I'm going to fix it up manually,
but please base future patches on linus's latest tree.
> The problem occurs (most frequently)
> in the case of raw sockets, which my patch addresses.
Unfortunately this is only true in your case. There was a report without
any packet sockets involved just two weeks ago and I have multiple
reports at work without any packet sockets. In these cases qdiscs aren't
the problem either, so it seems there are still spots that need fixing
after reverting the patch.
Anyway, your patch is the best we can do right now, thanks.
next prev parent reply other threads:[~2005-07-10 23:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-10 14:18 SO_ORIGINAL_DST does not work in nat/OUTPUT anymore Jens Hoelldampf
2005-07-10 15:32 ` Harald Welte
2005-07-10 16:18 ` Patrick McHardy
2005-07-10 16:27 ` Henrik Nordstrom
2005-07-10 17:53 ` Patrick McHardy
2005-07-10 20:24 ` Harald Welte
2005-07-10 20:46 ` Patrick McHardy
2005-07-11 11:06 ` Jan Engelhardt
2005-07-11 11:19 ` Patrick McHardy
2005-07-11 11:58 ` Harald Welte
2005-07-10 22:20 ` Phil Oester
2005-07-10 23:54 ` Patrick McHardy [this message]
2005-07-11 9:44 ` Roberto Nibali
2005-07-11 11:16 ` Patrick McHardy
2005-07-11 11:41 ` Roberto Nibali
2005-07-11 11:47 ` Patrick McHardy
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=42D1B52A.10200@trash.net \
--to=kaber@trash.net \
--cc=hno@marasystems.com \
--cc=kernel@linuxace.com \
--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.