From: "Folke Aeon" <aeon_folke@hotmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Structuring my shaping (fwd)
Date: Sun, 20 Oct 2002 02:37:04 +0000 [thread overview]
Message-ID: <marc-lartc-103508150722728@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103489653022215@msgid-missing>
hi,
i am not sure whether my point
will do your help or not. if you
have problems with deleting your
filters , then maybe the following
will do some help. if you don't
have a problem with that, then
just ignore this message :)
i delete my filters in a way
which just change the "add" to
"del" and nothing else different.
say, i add a filter :
tc filter add dev eth0 parent 1:0 prio 1 handle 0x30 tcindex classid 1:171
then, later i want to delete it,
i just type:
tc filter del dev eth0 parent 1:0 prio 1 handle 0x30 tcindex classid 1:171
hoping this will do some help.
by the way, this methord does can
delete the filter, but i am NOT
sure whether this will have some
negative influence on the other
classes.
regards
folke.
>From: Hayden Myers <hayden@spinbox.com>
>To: lartc@mailman.ds9a.nl
>Subject: [LARTC] Structuring my shaping (fwd)
>Date: Sat, 19 Oct 2002 15:59:47 -0400 (EDT)
>
>I still don't understand how I can have multiple classes with a different
>filter for each class and then change one of the filters without blowing
>away the rest and having to have different priorities. I'm shaping
>traffic between users so all filters should have the same priority.
>Anybody else have problems changing/deleting filters? I see some messages
>on the net but none have responses. I saw something about u32h but his
>examples give me RTNETLINK: invalid argument messages. This is beginning
>to irritate me highly.
>
>Hayden Myers
>Support Manager
>Skyline Network Technologies
>hayden@spinbox.com
>(410)583-1337 option 2
>
>
>---------- Forwarded message ----------
>Date: Thu, 17 Oct 2002 19:14:34 -0400 (EDT)
>From: Hayden Myers <hayden@compaq.skyline.net>
>To: lartc@mailman.ds9a.nl
>Subject: Structuring my shaping
>
>The shaping for my project needs to limit individual users while giving
>each user equal priority. My thoughts are to create a root prio qdisc and
>then place a qdisc underneath that for each user. Inside each of those
>qdiscs will be the classes to subdivide traffic based on port. Is this
>the best way to accomplish what I want?
>
>Hayden Myers
>Support Manager
>Skyline Network Technologies
>hayden@spinbox.com
>(410)583-1337 option 2
>
>
>
>
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_________________________________________________________________
Get a speedy connection with MSN Broadband. Join now!
http://resourcecenter.msn.com/access/plans/freeactivation.asp
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-10-20 2:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 23:14 [LARTC] Structuring my shaping Hayden Myers
2002-10-18 6:38 ` Stef Coene
2002-10-19 19:59 ` [LARTC] Structuring my shaping (fwd) Hayden Myers
2002-10-19 23:41 ` Stef Coene
2002-10-20 2:37 ` Folke Aeon [this message]
2002-10-20 4:20 ` Werner Almesberger
2002-10-21 3:45 ` Alexey Talikov
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-103508150722728@msgid-missing \
--to=aeon_folke@hotmail.com \
--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.