Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Adam Towarnyckyj" <adamt@commspeed.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] TC Hashing Filters
Date: Tue, 06 Jul 2004 20:16:38 +0000	[thread overview]
Message-ID: <02f801c46396$24a27f90$903113d8@uranus> (raw)
In-Reply-To: <005c01c2c1b1$e006a820$0200a8c0@monster>

Ok, I tried this:

tc qdisc add dev eth1 root handle 1: cbq bandwidth 200Mbit avpkt 1000

tc class add dev eth1 parent 1: classid 1:2 cbq bandwidth 200Mbit rate
200MBit allot 1514 weight 2Mbit prio 8 maxburst 20 avpkt 1000

tc filter add dev eth1 parent 1: handle 2: protocol ip u32 divisor 256

tc filter add dev eth1 protocol ip parent 1: u32 match ip src
216.19.49.140/32 hashkey mask 0x000000ff at 12 link 2:

tc class add dev eth1 parent 1:2 classid 1:3 cbq bandwidth 200Mbit rate
128Kbit allot 1514 prio 5 maxburst 20 avpkt 1000 bounded

tc filter add dev eth1 protocol ip parent 1: u32 ht 2:8c: match ip src
216.19.49.140 flowid 1:3

As well as changing the last class parent to 1:  Neither of these
worked.
As for the app, could I take a look at it? I'm sure it could be easily
modified to use CBQ and if not, I could modify the box the use HTB. I
really don't mind either way. I was having a problem patching for HTB
and that's why I'm not currently using it. My boss and I wrote a perl
script to pull information from a MySql database (rate and customer IP)
and plug it in to TC and that's what I was planning on doing this time
around only with a few modifications for the hashing tables. I won't
start on that though until I can get this up and running. Anyways,
thanks for the help. 

Adam Towarnyckyj
 

-----Original Message-----
From: zoop@lone.ath.cx [mailto:zoop@lone.ath.cx] 
Sent: Tuesday, July 06, 2004 12:15 PM
To: Adam Towarnyckyj; lartc@mailman.ds9a.nl
Subject: RE: [LARTC] TC Hashing Filters

....

Here the filter parents should be root not 1:2.  I think in the howto it
says that
all filters should be attached to root.  I'll get my box up that I have
doing this
to give you a working example.

>tc filter add dev eth1 parent 1:2 handle 2: protocol ip u32 divisor 256
>
>tc filter add dev eth1 protocol ip parent 1: u32 match ip src
>216.19.49.0/24 hashkey mask 0x000000ff at 12 link 2:
>
>tc class add dev eth1 parent 1:2 classid 1:3 htb rate 64Kbit ceil
64Kbit
>burst 0Kbit
>
>tc filter add dev eth1 protocol ip parent 1:2 u32 ht 2:8c: match ip src
>216.19.49.140 flowid 1:3
>
>I even tried changing the src to dst and this still does not work.
>Gideon, if you are out there somewhere, I'd appreciate it if you could
>tell me if this actually worked for you. This is the most frustrating
>project I have ever had to deal with because it makes so much sense and
>in theory it looks like it should be working just fine. Anyways, thanks
>for everyone's help. If anyone has any other ideas, I welcome them.
>
>Adam Towarnyckyj

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

  parent reply	other threads:[~2004-07-06 20:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22  1:02 [LARTC] TC Hashing Filters mjoachimiak
2003-01-23  0:08 ` mjoachimiak
2004-07-02 22:54 ` Adam Towarnyckyj
2004-07-03  0:12 ` zoop
2004-07-06 17:02 ` Adam Towarnyckyj
2004-07-06 18:08 ` Adam Towarnyckyj
2004-07-06 19:14 ` zoop
2004-07-06 19:16 ` zoop
2004-07-06 19:36 ` Walt Wyndroski
2004-07-06 20:16 ` Adam Towarnyckyj [this message]
2004-07-06 21:15 ` Adam Towarnyckyj
2004-07-06 21:25 ` Ed Wildgoose
2004-07-12 20:48 ` Adam Towarnyckyj
2004-07-13  1:23 ` gypsy
2004-07-13 17:45 ` Adam Towarnyckyj
2004-07-14  5:57 ` Catalin BOIE
2004-07-14 13:48 ` gypsy
2004-07-14 18:06 ` Adam Towarnyckyj
2004-07-14 18:25 ` Jason Boxman
2004-07-15  2:13 ` gypsy
2004-07-15 12:36 ` Glen Mabey
2004-07-15 17:40 ` Adam Towarnyckyj
2004-07-16  3:36 ` gypsy
2004-07-22 22:07 ` Adam Towarnyckyj

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='02f801c46396$24a27f90$903113d8@uranus' \
    --to=adamt@commspeed.net \
    --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