From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Please document this
Date: Fri, 23 Jul 2004 14:06:45 +0000 [thread overview]
Message-ID: <41011B75.238F1C4F@iswest.com> (raw)
Stephen,
This REALLY needs to be fixed in the code; tc should reject as a syntax
error any "add filter" command that does not include a "prio"
parameter. It also needs to be documented.
== From LARTC mailing list => Dear list,
> After much code crunching and beating my head against the wall
> (literally), I discovered the faulty code. Thanks mostly to gypsy who
> played a huge role in helping me discover the problem. My tc filter line
> had an error in it which completely baffles me because it worked up
> until 2045 lines were entered.
>
> Old command:
> tc filter add dev $dev protocol ip parent 12: u32 ht 2:$table1: ht
> 3:$table2: match ip dst $ip/32 flowid 12:$classid
>
> New command:
> tc filter add dev $dev protocol ip parent 12: prio 5 u32 ht 2:$table1:
> ht 3:$table2: match ip dst $ip/32 flowid 12:$classid
>
> Who would have thought that a prio would cause that much trouble?
Thanks,
gypsy
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2004-07-23 14:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41011B75.238F1C4F@iswest.com \
--to=gypsy@iswest.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.