From: Kajetan Staszkiewicz <kajtek@biezanow.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] TC in Wireless Environment
Date: Tue, 27 Dec 2005 23:55:01 +0000 [thread overview]
Message-ID: <200512280055.01307.kajtek@biezanow.net> (raw)
In-Reply-To: <008701c60b32$4e4b5cf0$6a01a8c0@AZIM>
Dnia wtorek, 27 grudnia 2005 23:10, Azim Samjani napisa³(a):
> Hi,
>
> Has anyone used TC in a wireless environment, which is dynamic. I
> understand that the parameters for queuing are static and cannot be changed
> unless the queuing discipline is deleted and reloaded with different
> parameters.
>
> If anyone can share any experience, that would be helpful.
Hello!
I'm not sure if I fully understand Your problem but tc is able to change
specified class without destroying all classes and disciplines on network
interface.
I use perl and php webpanel for setting up speed limits for my clients.
Loading all tc rules for all interfaces (and imqs) after every single change
is very slow, but I am able to change the one I need after changing settings
of one client with `tc class change`, after which I put all the stuff that
normally goes with `tc class add`.
--
| pozdrawiam / greetings | powered by Trustix, Gentoo and FreeBSD |
| Kajetan Staszkiewicz | JID: vegeta@chrome.pl |
| Vegeta | IMQ devnames: http://tuxpowered.net |
`------------------------^----------------------------------------'
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-12-27 23:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-27 22:10 [LARTC] TC in Wireless Environment Azim Samjani
2005-12-27 23:55 ` Kajetan Staszkiewicz [this message]
2005-12-28 16:10 ` Azim Samjani
2005-12-29 6:41 ` gypsy
2006-01-02 17:01 ` Kajetan Staszkiewicz
2006-01-03 15:43 ` Azim Samjani
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=200512280055.01307.kajtek@biezanow.net \
--to=kajtek@biezanow.net \
--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.