On Wed, 18 Apr 2018 13:10:49 +0800
Hangbin Liu <liuhang...@gmail.com> wrote:
> Hi Stephen,
>
> The patch's subject contains fix. But the kernel feature is applied on
> net-next.
> So I'm not sure if iproute2 net-next is suitable. If you are OK with the
> patch,
> please feel free to apply it on the branch which you think is suitable.
>
> Thanks
> Hangbin
>
> On 18 April 2018 at 13:05, Hangbin Liu <liuhang...@gmail.com> wrote:
> > Like kernel net-next commit 72f6d71e491e6 ("vxlan: add ttl inherit
> > support"),
> > vxlan ttl inherit should means inherit the inner protocol's ttl value.
> >
> > But currently when we add vxlan with "ttl inherit", we only set ttl 0,
> > which is actually use whatever default value instead of inherit the inner
> > protocol's ttl value.
> >
> > To make a difference with ttl inherit and ttl == 0, we add an attribute
> > IFLA_VXLAN_TTL_INHERIT when "ttl inherit" specified. And use "ttl auto"
> > to means "use whatever default value", the same behavior with ttl == 0.
> >
> > Reported-by: Jianlin Shi <ji...@redhat.com>
> > Suggested-by: Jiri Benc <jb...@redhat.com>
> > Signed-off-by: Hangbin Liu <liuhang...@gmail.com>
When davem merges the feature into net-next, dsa will merge this into
iproute2-next.
We hold off merging into iproute2 because often the kernel review feedback
causes
API changes.
