From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Can anyone fix this?
Date: Wed, 19 May 2004 11:50:45 +0000 [thread overview]
Message-ID: <40AB4A15.3020308@dsl.pipex.com> (raw)
In-Reply-To: <200405191427.53256.ml-lartc@drspirograph.com>
Chris Jensen wrote:
> Hi,
> I appologise for the bad ettiquite of this, but I have tried looking for some
> HTB examples that would help me, and am having trouble understanding how the
> tc filters should work, but I can't figure out why this isn't working.
> I've written this script, based upon the ultimate traffic shaper at LARTC, to
> try and shape for me and my 3 housemates.
> The idea being to give each user approx 1 quarter of the bandwidth, and then
> subdivide that into 3 priorities.
>
> None of the traffic seems to get clasiffied though.
You can't use u32 to filter egress on src if you are NATing - you need
to mark in POSTROUTING mangle and filter on fw.
Have a look at the kptd on www.docum.org .
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-05-19 11:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 4:27 [LARTC] Can anyone fix this? Chris Jensen
2004-05-19 11:50 ` Andy Furniss [this message]
2004-05-19 12:26 ` Chris Jensen
2004-05-19 14:17 ` Andreas Klauer
2004-05-23 12:08 ` Dmitry Golubev
2004-05-23 16:37 ` Patrick McHardy
2004-05-24 10:53 ` Dmitry Golubev
2004-05-24 16:23 ` Chris Jensen
2004-05-24 17:35 ` Stef Coene
2004-05-24 17:53 ` Andreas Klauer
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=40AB4A15.3020308@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.