From: Jason Boxman <jasonb@edseek.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Prioritizing forwarded traffic over locally generated traffic
Date: Fri, 24 Sep 2004 17:07:42 +0000 [thread overview]
Message-ID: <200409241307.42215.jasonb@edseek.com> (raw)
In-Reply-To: <20040923220934.TUOJ19539.mta07-svc.ntlworld.com@slartibartfast>
On Friday 24 September 2004 12:55, Neil Greatorex wrote:
> Many thanks to both of you for your replies.
>
> I have managed to get the setup working how I intended now - by using HTB
> classes/qdiscs. I had tried this approach before as one of many, however
> what I had failed to do was create the two classes I am filtering the
> traffic into as subclasses of a parent HTB class that was limited to the
> rate of the connection. Now it works as I intended!
>
> I'm now going to tackle the harder problem of doing it for downloading -
> I'm off to play with IMQ :-)
Indeed. Some people experience success setting up another egress qdisc on the
router's internet NIC and shaping with that. Since you have lots of ingress
to the router itself destined for the router, this may not work. I haven't
messed with IMQ yet, but it ought to work too. It's just extra work if you
don't need to shape incoming traffic for the router itself as well as the
network.
> Again, many thanks for your suggestions/advice!
Enjoy!
_______________________________________________
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-09-24 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 22:09 [LARTC] Prioritizing forwarded traffic over locally generated traffic Neil Greatorex
2004-09-23 22:34 ` Jason Boxman
2004-09-24 5:35 ` [LARTC] Prioritizing forwarded traffic over locally generated kraquen
2004-09-24 16:55 ` [LARTC] Prioritizing forwarded traffic over locally generated traffic Neil Greatorex
2004-09-24 17:07 ` Jason Boxman [this message]
2004-10-07 3:50 ` Alexander Samad
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=200409241307.42215.jasonb@edseek.com \
--to=jasonb@edseek.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.