From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up)
Date: Sun, 25 Apr 2004 07:06:17 +0000 [thread overview]
Message-ID: <408B6369.5010200@dsl.pipex.com> (raw)
In-Reply-To: <46799.82.82.95.252.1082769835.squirrel@mail.surakware.net>
Jason Boxman wrote:
> Egress is easy. Ingress seems to be a topic that is discussed often on LARTC,
> and I believe your options are to either use an ingress policer or the IMQ
> target. The former you can do directly with tcng, the latter I believe you
> cannot.
I know nothing about TCNG so can't help there.
You can shape ingress without using IMQ as long as you have just one LAN
interface and don't care about traffic headed for the shaping PC. You
just shape on the LAN interface.
Andy.
_______________________________________________
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-04-25 7:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-24 1:23 [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) on a router trapni
2004-04-24 5:27 ` Jason Boxman
2004-04-25 7:06 ` Andy Furniss [this message]
2004-04-25 17:43 ` Christian Parpart
2004-04-26 8:01 ` [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) Andy Furniss
2004-04-28 8:42 ` [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) on a router Christian Parpart
2004-05-02 23:44 ` Andreas Klauer
2004-05-05 8:34 ` [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) Andy Furniss
2004-05-05 10:39 ` [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) on a router Andreas Klauer
2004-05-05 12:33 ` [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) Andy Furniss
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=408B6369.5010200@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.