All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems with tc filter (getting packets into a CBQ)
Date: Sat, 18 May 2002 15:59:50 +0000	[thread overview]
Message-ID: <marc-lartc-102173762815237@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102166263506798@msgid-missing>

> Still no packets being filtered into my CBQ, but the packets are clearly
> being marked.

I found the error.  You mark the packets when they enter your box with 
iptables on device eth0.  But you add the qdisc and the classes to the same 
device.  But this qdisc and class can only control OUTgoing traffic and you 
want to control incoming traffic.  If this is a firewall with two NIC's, you 
can attach the qdisc and class to the second NIC.  Incoming NTP traffic get's 
marked and get's shaped when it leaves the box on the second NIC.  
If you really want to shape incoming traffic, you will have to use the 
ingress qdisc or the IMQ device.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2002-05-18 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17 19:09 [LARTC] Problems with tc filter (getting packets into a CBQ) Edwin Chiu
2002-05-18  0:08 ` Stef Coene
2002-05-18  0:29 ` Edwin Chiu
2002-05-18  9:17 ` Stef Coene
2002-05-18 15:46 ` Edwin Chiu
2002-05-18 15:59 ` Stef Coene [this message]

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=marc-lartc-102173762815237@msgid-missing \
    --to=stef.coene@docum.org \
    --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.