From: David Miller <davem@davemloft.net>
To: shmulik@nsof.io
Cc: netdev@vger.kernel.org, shmulik.ladkani@gmail.com
Subject: Re: [PATCH net-next] ip6_tunnel: Allow rcv/xmit even if remote address is a local address
Date: Wed, 25 Oct 2017 10:34:25 +0900 (KST) [thread overview]
Message-ID: <20171025.103425.239621897812285829.davem@davemloft.net> (raw)
In-Reply-To: <20171020212515.4678-1-shmulik@nsof.io>
From: Shmulik Ladkani <shmulik@nsof.io>
Date: Sat, 21 Oct 2017 00:25:15 +0300
> From: Shmulik Ladkani <shmulik.ladkani@gmail.com>
>
> Currently, ip6_tnl_xmit_ctl drops tunneled packets if the remote
> address (outer v6 destination) is one of host's locally configured
> addresses.
> Same applies to ip6_tnl_rcv_ctl: it drops packets if the remote address
> (outer v6 source) is a local address.
>
> This prevents using ipxip6 (and ip6_gre) tunnels whose local/remote
> endpoints are on same host; OTOH v4 tunnels (ipip or gre) allow such
> configurations.
>
> An example where this proves useful is a system where entities are
> identified by their unique v6 addresses, and use tunnels to encapsulate
> traffic between them. The limitation prevents placing several entities
> on same host.
>
> Introduce IP6_TNL_F_ALLOW_LOCAL_REMOTE which allows to bypass this
> restriction.
>
> Signed-off-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>
Given this wasn't allowed for so long, making it configurable makes
sense.
Applied, thanks.
prev parent reply other threads:[~2017-10-25 1:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 21:25 [PATCH net-next] ip6_tunnel: Allow rcv/xmit even if remote address is a local address Shmulik Ladkani
2017-10-25 1:34 ` David Miller [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=20171025.103425.239621897812285829.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shmulik.ladkani@gmail.com \
--cc=shmulik@nsof.io \
/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).