Hi!<br><br>I'm trying to work out whether or not I should use flow-tag to group different customer subnets. I have encountered the following questions from reading the man page:<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
Multiple actions may match and set tags on the same flow. Note that<br>listing many actions will cause tags to be applied in O(actions) time.<br>The actions try to run in O(1) time. For example if 10 prefixes are<br>listed in a single action it will take about the same CPU as if 100
<br>prefixes are used. Listing 100 actions will require 100 times the<br>CPU as 1 action.</blockquote><div><br>Does this mean that using flow-tag to tag all you subnets won't give you any performance boost compared to
e.g. just filtering your flows per subnet and generating a report of this?<br><br>Also this example worries me:<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
match 128.146/16 set-destination 0x010001</blockquote><div><br>Does it mean that the destination address will be overwritten?<br><br>Thanks for reading!<br><br>All the best,<br>Benjamin<br></div><br></div>