Each tag action with a type of "source-prefix" or "destination-prefix"
uses a longest match algorithm. For example if you have.
tag-action FOO
type source-prefix
match 10.0.0.0/8 set-src 0xFF
match 10.10.0.0/16 set-src 0xEE
A flow with a source IP address of "10.10.1.1" would get the
destination tag 0xEE.
An Identical match will result in an invalid tag file. Flow-tag will
exit with an error message. "flow-tag: tag.cfg line xx: Only one set
per source/destination per match."
You can only modify the source or destination tag in an action. To
modify both set up two actions then call them both in the definition.
ie
tag-action ACTION1
type source-prefix
match 10.0.0.0/8 set-src 0xFF
match 10.10.0.0/16 set-src 0xEE
tag-action ACTION2
type destination-prefix
match 10.0.0.0/8 set-dst 0xFF
match 10.10.0.0/16 set-dst 0xEE
tag-definition BAR
term
action ACTION1
action ACTION2
On May 7, 2005, at 8:15 AM, Gennady Abramov wrote:
Hello,
I have some questions about how flow-tag will select tag from
"tag-action"
section, if there is an overlapping of prefixes in this tag-action.
Is more detailed prefix is always prefferable?
Which tag will get flow, if there is two statements in one tag-action,
with identical "match", but with different tags in "set" ?
Based on previouce question, could I to modify source AND dst tag in
one
tag-action, using one match criteria, for example, to apply src and dst
tags to all flows from exporter 1.2.3.4?
--
Gennady Abramov, CCNA, CCNP; Demos-Internet NOC
[EMAIL PROTECTED] , AGV77-RIPE
_______________________________________________
Flow-tools mailing list
[EMAIL PROTECTED]
http://mailman.splintered.net/mailman/listinfo/flow-tools
_______________________________________________
Flow-tools mailing list
[EMAIL PROTECTED]
http://mailman.splintered.net/mailman/listinfo/flow-tools
