From: Viktor Kemmet <Viktor.Kemmet@t-online.de>
To: lartc@vger.kernel.org
Subject: [LARTC] TC and Diffserv on IPv6
Date: Mon, 25 Feb 2002 22:23:43 +0000 [thread overview]
Message-ID: <marc-lartc-101467582319979@msgid-missing> (raw)
Hi all,
does somebody have experience with IPv6 traffic control?
I have tried different tools - but, none of them seemed to work the way
it works with IPv4. Our project, Multi-Media-Conferencing, builds upon
IPv6 and is intended to use Diffserv for supporting differentiated
services requirements.
Is that feasible? At the moment we're facing the following problems:
1.) Settings made using tc don't have an effect on IPv6-traffic. (Is it
due to tc or to the kernel?)
2.) ip6tables does not support the TOS target or equivalent traffic
class setting.
3.) mgen6 does not support traffic class marking.
4.) ping6 returns the message: "Flowinfo is not supported."
Thanks
viktor
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next reply other threads:[~2002-02-25 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 22:23 Viktor Kemmet [this message]
2002-02-25 23:54 ` [LARTC] TC and Diffserv on IPv6 bert hubert
2002-02-26 11:07 ` Viktor.Kemmet
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-101467582319979@msgid-missing \
--to=viktor.kemmet@t-online.de \
--cc=lartc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.