From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] dscp & tunneling
Date: Thu, 10 Dec 2015 11:18:16 +0000 [thread overview]
Message-ID: <56695F78.5020802@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <5664173D.40808@darbyshire-bryant.me.uk>
[-- Attachment #1: Type: text/plain, Size: 1594 bytes --]
On 06/12/15 11:08, Kevin Darbyshire-Bryant wrote:
> So there I was pondering the problem of getting the IPv6 DSCP coding
> onto the outer IPv4 packets of my '6in4' tunnel (kindly provided for
> free by Hurricane Electric) when I stumbled across this in a man page:
>
>
> ip tunnel { add | change | del | show | prl } [ NAME ]
> [ mode MODE ] [ remote ADDR ] [ local ADDR ]
> [ [i|o]seq ] [ [i|o]key KEY ] [ [i|o]csum ] ]
> [ encaplimit ELIM ] [ ttl TTL ]
> [ tos TOS ] [ flowlabel FLOWLABEL ]
> [ prl-default ADDR ] [ prl-nodefault ADDR ] [ prl-delete
> ADDR ]
> [ [no]pmtudisc ] [ dev PHYS_DEV ] [ dscp inherit ]
>
> dscp inherit - just what I need! Unfortunately it turns out it's for
> 'things being tunnelled over ipv6' and not 'ipv6 being tunnelled over
> ipv4'. Aaaarrghhh! So close.
Of course I'm a complete muppet! This would be a fairly pointless
exercise as cake has already classified the tunnel as it's a single flow
(from my router to the tunnel server) and no amount of dscp bit fiddling
from inner to outer headers is going to make different parts of the
tunnel flow move to different cake tins. Oh I am stupid. Sigh.
I'm going to persist with my dscp 'dye' option (wash cleans, dye
'colours' the packets with certain dscp codes per tin - wash/dye -
geddit? I'll fetch my coat)
>
>
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
next prev parent reply other threads:[~2015-12-10 11:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 11:08 Kevin Darbyshire-Bryant
2015-12-10 11:18 ` Kevin Darbyshire-Bryant [this message]
2015-12-10 11:45 ` Dave Taht
2015-12-10 12:09 ` Kevin Darbyshire-Bryant
2015-12-10 12:22 ` Dave Taht
2015-12-10 12:35 ` Kevin Darbyshire-Bryant
2015-12-10 12:43 ` Kevin Darbyshire-Bryant
2015-12-10 12:49 ` Dave Taht
2015-12-10 12:59 ` Kevin Darbyshire-Bryant
2015-12-12 1:14 ` Jonathan Morton
2015-12-12 9:14 ` Kevin Darbyshire-Bryant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56695F78.5020802@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox