From: "ewan" <ewan@fragworld.co.uk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Deleting filters from a hashtable
Date: Sat, 25 Oct 2003 16:59:11 +0000 [thread overview]
Message-ID: <marc-lartc-106710114530395@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106704435528380@msgid-missing>
sorry paul, meant to answer in list.....
an alternate approach to this problem might be to keep your rules in a
database such as mysql and have a simple script file which builds and runs
the filter script.
this would allow you to add extra id and comment fields in the database
which can be used by your program to decide which rules should be applied at
any given time.
such a setup makes the task of identifing, deleting and adding rules much
easier as you can use complex programs and sql statements on the database.
You no longer have to worry about how to pick out a certian rule from a
textfile or installed ruleset as your build script simple replaces all rules
with a set selected from the DB
----- Original Message -----
From: "Paul J. Caritj" <pcaritj@riovia.net>
To: <lartc@mailman.ds9a.nl>
Sent: Thursday, October 23, 2003 4:59 PM
Subject: [LARTC] Deleting filters from a hashtable
> Hi,
> I'm trying to delete filters from a hashtable programatically, but am
> being foiled by one small problem:
>
> I can delete the rule with no difficulty given the full handle like so:
> tc filter del dev eth2 pref 5 handle 2:fe:800 u32
>
> First, my understanding is that, in this case:
> 2 => table
> fe => column
> 800 =>row (or vice versa)
> Is this correct?
>
> Given that, I suppose I need to know how to delete an entry without
> knowing which row it was inserted into. Alternatively, can I explicitly
> set the row into which I am inserting? Here is what I'm doing now:
>
> tc filter add dev eth2 parent 1:0 protocol ip prio 1 u32 ht 2:fe: match
> ip dst 192.168.255.254/32 flowid 1:fe; (Where, notably, "fffe" is the
> last two octets of the IP, and fe is the last.)
>
> Any help would be *much* appreciated. My brain is starting to melt ;)
>
> -Paul
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-10-25 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 23:59 [LARTC] Deleting filters from a hashtable Paul J. Caritj
2003-10-25 16:59 ` ewan [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-106710114530395@msgid-missing \
--to=ewan@fragworld.co.uk \
--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.