From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Dries De Winter <dries.dewinter@gmail.com>,
David Miller <davem@davemloft.net>,
kaber@trash.net, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] net: ICMPv6 packets transmitted on wrong interface if nfmark is mangled
Date: Tue, 4 Dec 2012 00:52:16 +0100 [thread overview]
Message-ID: <20121203235216.GA11723@1984> (raw)
In-Reply-To: <alpine.LNX.2.01.1212040037240.2816@nerf07.vanv.qr>
On Tue, Dec 04, 2012 at 12:38:25AM +0100, Jan Engelhardt wrote:
>
> On Monday 2012-12-03 22:31, Dries De Winter wrote:
> >
> >Not fixing this means that skb->mark is unavailable for use on ICMPv6
> >packets because it will inevitably put those packets on the wrong
> >interface. [...]
> >
> >I use skb->mark for QoS, not for routing so I don't expect
> >the outgoing interface to be affected by my markers.
>
> Why would it do that, if one has no routes joined to a fwmark NNN
> routing rule?
iptables_mangle assumes that ip_route_me_harder needs to be called if
the mark has changed.
prev parent reply other threads:[~2012-12-03 23:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <22884633.2468.1354092935228.JavaMail.driesdw@sahwcmp0020>
2012-11-28 9:09 ` [PATCH] net: ICMPv6 packets transmitted on wrong interface if nfmark is mangled Dries De Winter
2012-11-28 23:30 ` David Miller
2012-11-30 12:29 ` Dries De Winter
2012-11-30 17:22 ` David Miller
2012-12-03 12:46 ` Dries De Winter
2012-12-03 19:11 ` David Miller
2012-12-03 21:31 ` Dries De Winter
2012-12-03 22:06 ` David Miller
2012-12-05 13:41 ` Dries De Winter
2012-12-05 17:57 ` David Miller
2012-12-06 9:11 ` Dries De Winter
2012-12-03 23:38 ` Jan Engelhardt
2012-12-03 23:52 ` Pablo Neira Ayuso [this message]
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=20121203235216.GA11723@1984 \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=dries.dewinter@gmail.com \
--cc=jengelh@inai.de \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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.