[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180501.190455.1836576340094446679.davem@davemloft.net>
Date: Tue, 01 May 2018 19:04:55 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: jakub.kicinski@...ronome.com
Cc: netdev@...r.kernel.org, oss-drivers@...ronome.com,
john.hurley@...ronome.com
Subject: Re: [PATCH net] nfp: flower: set tunnel ttl value to net default
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
Date: Tue, 1 May 2018 15:49:49 -0700
> From: John Hurley <john.hurley@...ronome.com>
>
> Firmware requires that the ttl value for an encapsulating ipv4 tunnel
> header be included as an action field. Prior to the support of Geneve
> tunnel encap (when ttl set was removed completely), ttl value was
> extracted from the tunnel key. However, tests have shown that this can
> still produce a ttl of 0.
>
> Fix the issue by setting the namespace default value for each new tunnel.
> Follow up patch for net-next will do a full route lookup.
>
> Fixes: 3ca3059dc3a9 ("nfp: flower: compile Geneve encap actions")
> Fixes: b27d6a95a70d ("nfp: compile flower vxlan tunnel set actions")
> Signed-off-by: John Hurley <john.hurley@...ronome.com>
> Reviewed-by: Jakub Kicinski <jakub.kicinski@...ronome.com>
Applied and queued up for -stable.
Powered by blists - more mailing lists