From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Alin Nastac <alin.nastac@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] ipv6: Preserve link scope traffic original oif
Date: Fri, 3 Mar 2017 12:39:18 +0100 [thread overview]
Message-ID: <20170303113918.GA13435@salvia> (raw)
In-Reply-To: <1488376043-31976-1-git-send-email-alin.nastac@gmail.com>
On Wed, Mar 01, 2017 at 02:47:23PM +0100, Alin Nastac wrote:
> Link-local and multicast packets must keep their original oif after
> ip6_route_me_harder is called.
Out of curiosity, how does the setup you use look like to trigger this
problem?
next prev parent reply other threads:[~2017-03-03 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 13:47 [PATCH] ipv6: Preserve link scope traffic original oif Alin Nastac
2017-03-03 11:39 ` Pablo Neira Ayuso [this message]
2017-03-03 11:56 ` Alin Năstac
2017-03-03 12:12 ` Pablo Neira Ayuso
2017-03-03 13:22 ` Alin Năstac
-- strict thread matches above, loose matches on Subject: below --
2017-03-01 13:00 Alin Nastac
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=20170303113918.GA13435@salvia \
--to=pablo@netfilter.org \
--cc=alin.nastac@gmail.com \
--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 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).