Re: MTU filter revisited...

Hi Eugene,

Im not sure I understand what you mean with "Will adding a third term help me in terms of round trip improvement?", can you elaborate further?

I dont think there is a way to know how much time it takes for a filter to process a packet but I can tell it is very very fast, at a point that I dont think you will notice the difference. I could think on a test like this:

PC_A------------SRX----------PC_B

You can try 10000 pings from PC_A to PC_B and check the statistics:

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=71ms TTL=55
Reply from 8.8.8.8: bytes=32 time=67ms TTL=55
Reply from 8.8.8.8: bytes=32 time=67ms TTL=55
Reply from 8.8.8.8: bytes=32 time=61ms TTL=55

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 61ms, Maximum = 71ms, Average = 66ms

Then you can apply the filter, try the test again and check the statistics. You can also add more terms and test if you see a considerable difference in the times.

Regarding the fact that you used a range on the matching criteria, I dont think it will make any difference if you use a single value but if thats an option, I will go with the fixed value instead of the range.

I hope I was able to help you a bit.