From: "Adam Towarnyckyj" <adamt@commspeed.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] TC Hashing Filters
Date: Thu, 15 Jul 2004 17:40:04 +0000 [thread overview]
Message-ID: <075301c46a92$c357fef0$903113d8@uranus> (raw)
In-Reply-To: <005c01c2c1b1$e006a820$0200a8c0@monster>
gypsy wrote:
> Your script can be modified to display the line with the substitutions
> and to exit when executing causes an error. What I envision is that
> you'll watch 2000+ lines of good stuff scroll by and that the final
line
> will be your Bad Boy. And the last few lines are what we all are
> holding our breath to see <grin>.
I have done as you suggested (actually, if you noticed in the Action
subroutine, all the error reporting from before was still there I just
commented it out) and this is what I've come up with. This is the last
known good command and then the command that errors, as well as the
error message, and the counter I added back in.
Performing: /sbin/tc filter add dev eth1 protocol ip parent 1: u32 ht
2:54: match ip dst 216.19.20.84 flowid 1:FFFB
2045
Performing: /sbin/tc filter add dev eth1 protocol ip parent 1: u32 ht
2:2E: match ip dst 216.19.46.46 flowid 1:FFFB
WHOOPS: RTNETLINK answers: File exists
The error exists on the 2046th command. Any tc filter command I try to
add from here on out gives me the same error even if I try it manually
instead of using the script. I examined the previous commands that
worked fine and there are plenty that dump into the 2:2E: table.
> I think the line above should count down from 65535, not up.
As you can see, I did this as you suggested. I like it better because it
keeps things very separate so there's no confusion. Thanks for the
suggestion.
> Sorry, that's all I have time for now.
Any time you can spare is incredibly helpful. Thank you.
Adam Towarnyckyj
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-07-15 17:40 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
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 [this message]
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='075301c46a92$c357fef0$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 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.