Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+ipvs\-next\]\s+ipvs\:\s+Maintain\s+all\s+DSCP\s+and\s+ECN\s+bits\s+for\s+ipv6\s+tun\s+forwarding\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: [PATCH ipvs-next] ipvs: Maintain all DSCP and ECN bits for ipv6 tun forwarding (score: 1)
Author: Simon Horman <horms@xxxxxxxxxxxx>
Date: Thu, 17 Jul 2014 12:55:25 +0900
Thanks, I have queued this up for v3.16 in the ipvs tree. -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo
/html/lvs-devel/2014-07/msg00013.html (11,198 bytes)

2. [PATCH ipvs-next] ipvs: Maintain all DSCP and ECN bits for ipv6 tun forwarding (score: 1)
Author: <agartrell@xxxxxx>
Date: Wed, 16 Jul 2014 15:57:34 -0700
Previously, only the four high bits of the tclass were maintained in the ipv6 case. This matches the behavior of ipv4, though whether or not we should reflect ECN bits may be up for debate. Signed-of
/html/lvs-devel/2014-07/msg00012.html (10,222 bytes)

3. Re: [PATCH ipvs-next] ipvs: Maintain all DSCP and ECN bits for ipv6 tun forwarding (score: 1)
Author: Simon Horman <horms@xxxxxxxxxxxx>
Date: Wed, 16 Jul 2014 09:41:49 +0900
Hi Alex, Somehow this patch did not reach my inbox. Could you repost it with Julian's ack and me CCed? -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message
/html/lvs-devel/2014-07/msg00005.html (11,975 bytes)

4. Re: [PATCH ipvs-next] ipvs: Maintain all DSCP and ECN bits for ipv6 tun forwarding (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Wed, 16 Jul 2014 00:36:38 +0300 (EEST)
Hello, Agreed, RFC 3168 9.1 has some recommendations and more changes may be needed, eg. by using INET_ECN_encapsulate as in other tunnels: ip6_flow_hdr(iph, INET_ECN_encapsulate(inner_dsfield, inner
/html/lvs-devel/2014-07/msg00002.html (10,377 bytes)


This search system is powered by Namazu