|Main index||Section 8||Options|
pflogd closes and then re-opens the log file when it receives SIGHUP, permitting newsyslog(8) to rotate logfiles automatically. SIGALRM causes pflogd to flush the current logfile buffers to the disk, thus making the most recent logs available. The buffers are also flushed every delay seconds.
If the log file contains data after a restart or a SIGHUP, new logs are appended to the existing file. If the existing log file was created with a different snaplen, pflogd temporarily uses the old snaplen to keep the log file consistent.
pflogd tries to preserve the integrity of the log file against I/O errors. Furthermore, integrity of an existing log file is verified before appending. If there is an invalid log file or an I/O error, the log file is moved out of the way and a new one is created. If a new file cannot be created, logging is suspended until a SIGHUP or a SIGALRM is received.
pflogd will also log the pcap statistics for the pflog(4) interface to syslog when a SIGUSR1 is received.
The options are as follows:
|Debugging mode. pflogd does not disassociate from the controlling terminal.|
|Time in seconds to delay between automatic flushes of the file. This may be specified with a value between 5 and 3600 seconds. If not specified, the default is 60 seconds.|
|Log output filename. Default is /var/log/pflog.|
|Specifies the pflog(4) interface to use. By default, pflogd will use pflog0.|
|Writes a file containing the process ID of the program to /var/run. The file name has the form <pidfile >.pid. The default is pflogd.|
|Analyze at most the first snaplen bytes of data from each packet rather than the default of 116. The default of 116 is adequate for IP, ICMP, TCP, and UDP headers but may truncate protocol information for other protocols. Other file parsers may desire a higher snaplen.|
|Check the integrity of an existing log file, and return.|
|Selects which packets will be dumped, using the regular language of tcpdump(1).|
|Process ID of the currently running pflogd.|
|/var/log/pflog||Default log file.|
# pflogd -s 1600 -f suspicious.log port 80 and host evilhost
Log from another pflog(4) interface, excluding specific packets:
# pflogd -i pflog3 -f network3.log "not (tcp and port 23)"
Display binary logs:
# tcpdump -n -e -ttt -r /var/log/pflog
Display the logs in real time (this does not interfere with the operation of pflogd):
# tcpdump -n -e -ttt -i pflog0
Tcpdump has been extended to be able to filter on the pfloghdr structure defined in <net/if_pflog.h>. Tcpdump can restrict the output to packets logged on a specified interface, a rule number, a reason, a direction, an IP family or an action.
|ip||Address family equals IPv4.|
|ip6||Address family equals IPv6.|
|ifname kue0||Interface name equals "kue0".|
|on kue0||Interface name equals "kue0".|
|ruleset authpf||Ruleset name equals "authpf".|
|rulenum 10||Rule number equals 10.|
|reason match||Reason equals match. Also accepts "bad-offset", "fragment", "bad-timestamp", "short", "normalize", "memory", "congestion", "ip-option", "proto-cksum", "state-mismatch", "state-insert", "state-limit", "src-limit", and "synproxy".|
|action pass||Action equals pass. Also accepts "block".|
|inbound||The direction was inbound.|
|outbound||The direction was outbound.|
Display the logs in real time of inbound packets that were blocked on the wi0 interface:
# tcpdump -n -e -ttt -i pflog0 inbound and action block and on wi0
|PFLOGD (8)||October 22 2008|
|Main index||Section 8||Options|
|“||Our grievance is not just against Unix itself, but against the cult of Unix zealots who defend and nurture it. They take the heat, disease, and pestilence as givens, and, as ancient shamans did, display their wounds, some self-inflicted, as proof of their power and wizardry. We aim, through bluntness and humor, to show them that they pray to a tin god, and that science, not religion, is the path to useful and friendly technology.||”|
|— The Unix Haters' handbook|