There is no such feature yet but I know the problem. I usually do it the following way:
Create a rule&pipe that is limitting the traffic to some value that is lower than the expected
bandwidthusage of that traffic. Then make all other traffic stop or try under low traffic condition
and see if the traffic that should match this rule is actually limited. If so your ruledefinition is
correct. You now can change the assignment to another queue/pipe that reflects the real usage. It's
not a good solution but should at least show if your rule definition is correct.
> -----Original Message-----
> From: Bob Young [mailto:bob at lavamail dot net]
> Sent: Tuesday, August 29, 2006 3:12 PM
> To: m0n0wall at lists dot m0n0 dot ch
> Subject: [m0n0wall] Is there logging for M0n0wall Traffic
> Shaper rules ?
> Does anyone know if there is logging for individual Traffic
> Shaper rules?
> I know M0n0wall has firewall logging. But Traffic Shaper
> logging would be
> great if M0n0wall has it.
> It's easy to just assume a particular Traffic Shaper rule is
> working, just
> because we put it in as a Traffic Shaper rule. When in
> reality maybe the
> packets are passing our intended rule and going on to our
> lower priority
> "catch-all" rule.
> If none of our Traffic Shaper rules are a match, then the
> data still passes
> out the pipe to the destination interface, using the full BW
> that the pipe
> is set for, with no queuing at all.
> So in reality we may only "think" a Traffic Shaper rule we typed in is
> working, when in reality it is being bypassed completely.
> Thank you for any info on how to log the Traffic Shaper rules.
> Bob Young