All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Limiting bandwidth to entire LAN
Date: Fri, 05 Mar 2004 00:07:45 +0000	[thread overview]
Message-ID: <4047C4D1.3060801@snapgear.com> (raw)
In-Reply-To: <000b01c401f8$aafbc380$ce302bc8@traza>

Hi Gastón,

> tc filter add dev eth0 parent 1:0 protocol ip prio 100 u32 match ip src
> 1.2.3.0/24 classid 1:30

> tc filter add dev eth1 parent 1:0 protocol ip prio 100 u32 match ip dst
> 1.2.3.0/24 classid 1:30
I'm pretty sure you want 'flowid 1:30' instead of classid on the filters.

To my knowledge, the classid is declaring the filter to have that class, instead of 
directing the matching to the class with that id.

Although, taking a quick look through the doco, I can't see anywhere where
it explicitly says what the flowid does, maybe it's just assumed because all the 
examples are like that.

regards

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer  email:     damion@snapgear.com
SnapGear - A CyberGuard Company ---    ph:         +61 7 3435 2809
  | Custom Embedded Solutions          fax:         +61 7 3891 3630
  | and Security Appliances            web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  ---  Free Embedded Linux Distro at   http://www.snapgear.org  ---

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2004-03-05  0:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04 14:55 [LARTC] Limiting bandwidth to entire LAN Gastón
2004-03-05  0:07 ` Damion de Soto [this message]
2004-03-06 12:15 ` Stef Coene
2004-03-06 12:15 ` Stef Coene
2004-03-07 23:06 ` gaston
2004-03-07 23:17 ` gaston

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=4047C4D1.3060801@snapgear.com \
    --to=damion@snapgear.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.