<![CDATA[PfBlocker log format]]>Hi All,

I have pfBlocker 1.0.2 on pfSense 2.1.5 (haven't made the 2.2 upgrade yet). I also recently started exporting my logs to a server running ELSA. However I've noticed that the blocked packet logs are rather useless (see screenshot). They state a rule number that was blocked, but no text. So I still have to go to my pf page to check what happened.

SO, does anyone know if the new version of pfBlocker adds more useful logs with text strings? And if not, would it be possible to somehow make the logging format customizeable? A hack on my end or a feature request?
Untitled.png
Untitled.png_thumb

]]>https://forum.netgate.com/topic/82220/pfblocker-log-formatRSS for NodeWed, 15 Apr 2026 01:13:34 GMTWed, 01 Apr 2015 21:49:45 GMT60<![CDATA[Reply to PfBlocker log format on Fri, 03 Apr 2015 16:29:08 GMT]]>Thank you BBcan! I'll look into that this weekend. I appreciate the helpful answer :)

]]>https://forum.netgate.com/post/533619https://forum.netgate.com/post/533619Fri, 03 Apr 2015 16:29:08 GMT<![CDATA[Reply to PfBlocker log format on Thu, 02 Apr 2015 18:45:12 GMT]]>Yes unfortunately, pfSense Syslogs do not contain the "Description" field in its output. I know that user "fearnothing" has written a parser (pfsense 2.2) for ELSA. Its available here:

https://groups.google.com/forum/#!topic/security-onion/P4oALAvH-Ek

]]>https://forum.netgate.com/post/533389https://forum.netgate.com/post/533389Thu, 02 Apr 2015 18:45:12 GMT<![CDATA[Reply to PfBlocker log format on Wed, 01 Apr 2015 22:01:14 GMT]]>pfBlocker does not log anything. It creates firewall rules. Logging and its format is core pf. And no, there is no decription text in pfSense 2.2.x either. If you want description, stop using raw logs.

]]>https://forum.netgate.com/post/533141https://forum.netgate.com/post/533141Wed, 01 Apr 2015 22:01:14 GMT