![]() |
|
|||
|
Here is the nmap command I'm using to try to change counters other than match when I type pfctl -s info
Quote:
Last edited by audio; 16th July 2008 at 08:18 PM. |
|
|||
|
Add some log modifiers to your pf ruleset. Then you can use tcpdump -eni pflog0 to verify which rule matched a packet.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
|
I can do that, but for example if I do a tcpdump -eni pflog0 not reason match" then I don't get any results. There are a lot of other reasons in the PF manual such as bad-offset, fragment, short, normalize, memory, etc., and I'd like to be able to trigger those and see them in the logs, or in the pf info stats.
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| uncovering network info? | evilunixuser | Other OS | 2 | 2nd June 2009 04:35 PM |
| Using a LiveCD to gather info | phreud | FreeBSD Installation and Upgrading | 9 | 14th November 2008 11:43 PM |
| port info | sniper007 | FreeBSD General | 6 | 14th November 2008 10:46 AM |
| PF and label counters | espenfjo | FreeBSD General | 2 | 2nd July 2008 03:17 PM |
| README (Forum Rules and Info) | Carpetsmoker | Forum Announcements | 0 | 30th April 2008 04:22 PM |