> This morning tcpdumping pflog to my console stop working. What am I > doing wrong, and how can I diagnose problems with it. > This is the command I've been using for monitoring pflog0: > # tcpdump -i pflog0 -e -v
try adding the '-n'. you are doing name resolution on every ip address and your dns server might have changed. i'd also strongly suggest avoiding the '-v' option. it has a history of being remotely exploitable. the usual incantation is: # tcpdump -nettti pflog0 .mike