duplicate packets might be generated more than once. not sure about the State options....
sai On 3/3/07, Brookenmire <[EMAIL PROTECTED]> wrote:
Thanks Sai, but the it raises a couple of questions: Why am I seeing multiple blocks from the same IP and port if it is the last packet ? Also, if I set the State option for the rule to "None" I still see the same thing ? Mar 3 06:38:57 192.168.1.199 pf: 2. 562031 rule 189/0(match): block in on ng0: xxx.xxx.xxx.xxx.1809 > 192.168.2.10.49205: F 0:0(0) ack 1 win 33362 Mar 3 06:39:03 192.168.1.199 pf: 5. 126777 rule 189/0(match): block in on ng0: xxx.xxx.xxx.xxx.1809 > 192.168.2.10.49205: F 0:0(0) ack 1 win 33362 Mar 3 06:39:13 192.168.1.199 pf: 10. 466370 rule 189/0(match): block in on ng0: xxx.xxx.xxx.xxx.1809 > 192.168.2.10.49205: F 0:0(0) ack 1 win 33362 Mar 3 06:39:34 192.168.1.199 pf: 20. 817280 rule 189/0(match): block in on ng0: xxx.xxx.xxx.xxx.1809 > 192.168.2.10.49205: F 0:0(0) ack 1 win 33362 Mar 3 06:40:15 192.168.1.199 pf: 41. 546847 rule 189/0(match): block in on ng0: xxx.xxx.xxx.xxx.1809 > 192.168.2.10.49205: F 0:0(0) ack 1 win 33362 Mar 3 07:04:30 192.168.1.199 pf: 21. 176218 rule 189/0(match): block in on ng0: xxx.xxx.xxx.xxx.2692 > 192.168.2.10.49205: F 1998254475:1998254475(0) ack 3549271994 win 33362
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
