From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: [Cake] OpenWRT, DSCP & 6in4 tunneling - a hint!
Date: Thu, 10 Dec 2015 14:30:19 +0000 [thread overview]
Message-ID: <56698C7B.9000309@darbyshire-bryant.me.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
Those following my recent journey on trying to get dcsp info from inner
ipv6 headers to the outer ipv4 tunnel headers and as a result get cake
to classify traffic correctly, may be interested in the following solution:
add "option tos 'inherit'" to the 'wan6' interface definition in
/etc/config/network
I can't find any documentation covering this on the openwrt site which
lead to quite an investigation starting from 'sit.c' in the kernel,
iproute2, busybox, openwrt's netifd and finally the '6in4.sh' that it calls.
The odd thing is that I swear this used to work by default!
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
next reply other threads:[~2015-12-10 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 14:30 Kevin Darbyshire-Bryant [this message]
2015-12-10 15:12 ` Dave Taht
2015-12-10 16:40 ` 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=56698C7B.9000309@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