lkml.org 
[lkml]   [2020]   [Aug]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [net-next v4] seg6: using DSCP of inner IPv4 packets
From
Date


On 25/08/2020 03:11, David Miller wrote:
> From: Ahmed Abdelsalam <ahabdels@gmail.com>
> Date: Mon, 24 Aug 2020 08:51:24 +0000
>
>> This patch allows copying the DSCP from inner IPv4 header to the
>> outer IPv6 header, when doing SRv6 Encapsulation.
>>
>> This allows forwarding packet across the SRv6 fabric based on their
>> original traffic class.
>>
>> Signed-off-by: Ahmed Abdelsalam <ahabdels@gmail.com>
>
> "Allows" sounds like the behavior is optional, but that is not what
> is happening here. You are making this DSCP inheritance behavior
> unconditional.
>
> I've stated that the current behavior matches what other ipv6
> tunneling devices do, and therefore we should keep it that way.
>
> Furthermore, this behavior has been in place for several releases
> so you cannot change it by default. People may be depending upon
> how things work right now.
>

Ok. I added a new sysctl (seg6_inherit_inner_ipv4_dscp) to
enable/disable the new behavior.

The sysctl will be checked in case of IPv4 traffic.
In the IPv6 case, there is no change as the code is already copying the
DSCP from the inner IPv6 packet.

I'm sending a new patch.


> Also:
>
>> @@ -130,6 +129,7 @@ int seg6_do_srh_encap(struct sk_buff *skb, struct ipv6_sr_hdr *osrh, int proto)
>> struct ipv6_sr_hdr *isrh;
>> int hdrlen, tot_len, err;
>> __be32 flowlabel;
>> + u8 tos = 0, hop_limit;
>
> Need to preserve reverse christmas tree here.
>
Fixed in the new patch.

\
 
 \ /
  Last update: 2020-08-25 14:04    [W:0.032 / U:25.436 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site