All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Help please with tc and iptables mark
Date: Mon, 04 Apr 2005 13:31:52 +0000	[thread overview]
Message-ID: <425141C8.8070506@dsl.pipex.com> (raw)
In-Reply-To: <200504041206.35593.adrian.turcu@gmvinteractive.com>

Adrian Turcu wrote:
> Hello list members,
> 
> Finaly I'm here after a week of trying to subscribe to this list... pfew...
> 
> Anyway... I have a rather strange problem with tc. I am trying to police the 
> ingress traffic into my network using the iptables MARK feature (in mangle 
> table, PREROUTING) but it seems that tc filters ignore this marks and they 
> don't work at all for me. Let me explain a bit more in detail:

There is alot of work going on with tc at the moment - There are/will be 
lots more matches and the ability to run iptables commands from filters.

> 
> I have a server behind my linux-firewall box (firewall is with 2.6.10 kernel 
> custom build,

I think with 2.6.10 you can still get the behaviour you want if you 
don't select packet action in Qos and/or fair queuing of config - you 
get to select a different policer then.

CONFIG_NET_CLS_POLICE is the one you want if the other doesn't disappear 
de select it aswell.

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

  reply	other threads:[~2005-04-04 13:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 11:06 [LARTC] Help please with tc and iptables mark Adrian Turcu
2005-04-04 13:31 ` Andy Furniss [this message]
2005-04-04 13:49 ` Adrian Turcu
2005-04-04 14:31 ` james jones
2005-04-04 14:54 ` Adrian Turcu
2005-04-04 16:24 ` Adrian Turcu
2005-04-04 16:41 ` Adrian Turcu
2005-04-04 23:52 ` Alexander Samad
2005-04-08  0:26 ` 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=425141C8.8070506@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.