Hello Marius, On Sun, Mar 20, 2005 at 03:28:24PM +0200, [EMAIL PROTECTED] wrote:
> *I need to differentiate the two bands for each host.* (62+ hosts > beeing forwarded trought the gateway). The Metropolitan segment is [ ... ] > So, any1 has some comments on this, how should i "treat" this disease? > *does pmacctd parse the tag definition file recursively*? the only thing > that i did and it works but i dont't know when it comes to memory management > how it will look > > 1= incoming, 2 = outgoing; composed tags with ip > id=2216 filter='dst host XXX.XXX.XXX.216 and src net YYY.YYY.148.0/24' > id=2216 filter='dst host XXX.XXX.XXX.216 and src net YYY.YYY.149.0/24' > id=2216 filter='dst host XXX.XXX.XXX.216 and src net YYY.YYY.136.0/24' > id=2216 filter='dst host XXX.XXX.XXX.216 and src net YYY.YYY.121.0/24' > .... > id=1216 filter='src host XXX.XXX.XXX.216 and dst net YYY.YYY.148.0/24' > id=1216 filter='src host XXX.XXX.XXX.216 and dst net YYY.YYY.149.0/24' Two comments on the setup. 1) If you need to differentiate the two segments, you may consider tagging just one (say, the Metropolitan one), leaving the other untagged. This way all Metropolitan traffic would be tagged as 'x' and the remainder, Internet Traffic, as '0'. 2) a) If you don't need to further differentiate incoming/outcoming traffic on the Metro segment (because, for example, you need just to differentiate the Metro/Internet traffic), you may consider removing the src/dst clauses from the filter; b) If on your (local) side, *all* hosts have to be handled the same way, you may also consider removing the 'host XXX.XXX.XXX.216' part. This way, some lines (one for each Metro class) like the following one should be enough to tag all (in and out) Metro traffic for each local host: "id=216 filter='net YYY.YYY.148.0/24'" Cheers, Paolo
