Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: shmulik@metanetworks.com
Cc: ast@kernel.org, netdev@vger.kernel.org, shmulik.ladkani@gmail.com
Subject: Re: [PATCH net-next] ip6_tunnel: collect_md xmit: Use ip_tunnel_key's provided src address
Date: Tue, 07 Aug 2018 12:37:19 -0700 (PDT)	[thread overview]
Message-ID: <20180807.123719.1020396637013549448.davem@davemloft.net> (raw)
In-Reply-To: <20180806120059.24992-1-shmulik.ladkani@gmail.com>

From: Shmulik Ladkani <shmulik@metanetworks.com>
Date: Mon,  6 Aug 2018 15:00:59 +0300

> When using an ip6tnl device in collect_md mode, the xmit methods ignore
> the ipv6.src field present in skb_tunnel_info's key, both for route
> calculation purposes (flowi6 construction) and for assigning the
> packet's final ipv6h->saddr.
> 
> This makes it impossible specifying a desired ipv6 local address in the
> encapsulating header (for example, when using tc action tunnel_key).
> 
> This is also not aligned with behavior of ipip (ipv4) in collect_md
> mode, where the key->u.ipv4.src gets used.
> 
> Fix, by assigning fl6.saddr with given key->u.ipv6.src.
> In case ipv6.src is not specified, ip6_tnl_xmit uses existing saddr
> selection code.

Applied, thanks.

> Signed-off-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>
> Reviewed-by: Eyal Birger <eyal.birger@gmail.com>
> Fixes: 8d79266bc48c ("ip6_tunnel: add collect_md mode to IPv6 tunnels")

Please place the Fixes: tag first in the set of tags in the future,
thank you.

      reply	other threads:[~2018-08-07 21:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-06 12:00 [PATCH net-next] ip6_tunnel: collect_md xmit: Use ip_tunnel_key's provided src address Shmulik Ladkani
2018-08-07 19:37 ` 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=20180807.123719.1020396637013549448.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ast@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shmulik.ladkani@gmail.com \
    --cc=shmulik@metanetworks.com \
    /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