From: Corey Hickey <bugfood-ml@fatooh.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Does IPV6 support HTB?
Date: Wed, 24 Mar 2004 17:01:49 +0000 [thread overview]
Message-ID: <4061BEFD.40202@fatooh.org> (raw)
In-Reply-To: <GJEFLCKHDGDKIACOCAACGEHBCAAA.atlas@control.kangwon.ac.kr>
신혜민 wrote:
> I have been studying traffic control in linux these days.
>
> I became to know there are several qeueuing displines such as tbf, cbq,
>
> htp, etc. But, there isn't the comment whether they support IPv6 traffic.
>
> I got this question because there is no comment about how to connect qdisc
>
> classes with IPv6 flow using "tc filter" command, and I think the "tc
>
> filter" command examples shown in several documents are for only IPv4.
>
I haven't personally verified this, but I'm pretty sure that even if the
tc filters don't natively support ipv6 matches, you can still use
iptables/ip6tables to mark packets as you choose, and then filter for
that mark. Something like:
# It's often easier to make new chains for this
# because there's an implicit RETURN after a MARK
# so we can't just let packets fall off the end of the chain
# or else they may end up matching later rules.
ip6tables -t mangle -N fast
ip6tables -t mangle -A fast -j MARK --set-mark 0x01
ip6tables -t mangle -A fast -j ACCEPT
# just an example
ip6tables -t mangle -A FORWARD -p tcp -s 10.0.0.2 -j fast
# You can set up your htb (or whatever) framework
# and add this filter for it to reference.
tc filter add dev eth0 parent 1: protocol ip prio 1 handle 0x01 fw \
flowid 1:10
....and so forth.
-Corey
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-03-24 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 12:40 [LARTC] Does IPV6 support HTB? 신혜민
2004-03-24 17:01 ` Corey Hickey [this message]
2004-03-24 18:24 ` Alan Ford
2004-03-26 14:34 ` Alan Ford
2004-04-15 11:23 ` Alan Ford
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=4061BEFD.40202@fatooh.org \
--to=bugfood-ml@fatooh.org \
--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.