On 4/17/18 11:05 PM, Hangbin Liu 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 whatev
On Wed, Apr 18, 2018 at 08:50:16AM -0700, Stephen Hemminger wrote:
> 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.
Got it, Thanks.
Regards
Hangbin
On Wed, 18 Apr 2018 13:10:49 +0800
Hangbin Liu 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
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 L
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
prot
