Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Erik Slagter <erik@slagter.name>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Trying to do some very simple ingress limiting, no success
Date: Sun, 09 Apr 2006 13:09:34 +0000	[thread overview]
Message-ID: <1144588174.5694.27.camel@localhost.localdomain> (raw)
In-Reply-To: <1144579998.5694.18.camel@localhost.localdomain>


[-- Attachment #1.1: Type: text/plain, Size: 2230 bytes --]

On Sun, 2006-04-09 at 14:00 +0100, Andy Furniss wrote:
> Erik Slagter wrote:
> > Hi,
> > 
> > I am trying to do some simple ingress limiting based on fwmark. I know
> > the ability and sense to do INGRESS limiting is ehm... limited ;-) but
> > still I want to try it.
> > 
> > I tried several things.
> > 
> > === 1 ===
> > 
> > tcq ingress handle ffff: 
> > tcf parent ffff: protocol ip prio 1 handle 1 fw police rate 12mbit burst 10k drop
> > tcf parent ffff: protocol ip prio 1 handle 2 fw police rate 10mbit burst 10k drop
> > tcf parent ffff: protocol ip prio 1 handle 3 fw police rate 1mbit  burst 10k drop
> > 
> > This installs OK, but the filters are never called. The netfilter stats
> > show the marks are set though. To make sure it's not just the tc stats
> > output that's borked, I changed the bw limits to a rediculous low value,
> > and indeed, no effect at all.
> > 
> There are two policers now the old one will work as you want but you 
> need to change your kernel config. Unselect packet action and you should 
> be able to choose a different policer.

Found it and deselected it. Now making new kernel...

The "old" policer is marked as "obsolete", so I guess it will go away.

What am I supposed to replace it with, then?

> Or you could try using tc filters instead of netfilter - I don't know if 
> it will be possible for what you want as I can't see the rules that mark.

It's probably possible, but I already have quite a large set of
netfilter rules. I don't want to make the whole thing even more
complicated by also adding lots of tc stuff, I'd rather have the
tc/iproute things as simple as possible.
 
> This has never worked if you want a queue on ingress you need to use IMQ 
> (in the case that you need netfilter PREROUTING marks) or IFB (kernel >= 
> 2.6.16) but this will hook before netfilter - so no marks.

For IMQ I need to patch the kernel (feasible) and the netfilter tools
(not feasible :-() I just learned.

And you're just telling me I cannot use IFB. Bummer. Anyway, if there is
any simple (!) way to implement what I am searching for, I am happy.

I will try your "old policer version" suggestion asap.

Thanks for your help.

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2771 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-04-09 13:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-09 10:53 [LARTC] Trying to do some very simple ingress limiting, no success Erik Slagter
2006-04-09 13:00 ` Andy Furniss
2006-04-09 13:09 ` Erik Slagter [this message]
2006-04-09 13:42 ` Andy Furniss
2006-04-10 12:36 ` Erik Slagter
2006-04-10 12:38 ` Erik Slagter

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=1144588174.5694.27.camel@localhost.localdomain \
    --to=erik@slagter.name \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox