bin/124825: tcpdump(8) does not support pfsync(4) data

Peter Jeremy peterjeremy at optushome.com.au
Sat Jun 21 12:20:04 UTC 2008


>Number:         124825
>Category:       bin
>Synopsis:       tcpdump(8) does not support pfsync(4) data
>Confidential:   no
>Severity:       non-critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jun 21 12:20:03 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Peter Jeremy
>Release:        FreeBSD 7.0-STABLE i386
>Organization:
n/a
>Environment:
System: FreeBSD server.vk2pj.dyndns.org 7.0-STABLE FreeBSD 7.0-STABLE #18: Sun May 18 15:02:39 EST 2008 root at server.vk2pj.dyndns.org:/var/obj/k7/usr/src/sys/server i386

>Description:
	In its current form on FreeBSD, pf(4) has no mechanism to report
	state changes to the user.  This significantly increases the
	difficulty in debugging pf(4) issues.

>How-To-Repeat:
	Documented deficiency in FreeBSD (see pfsync(4) manpage)

>Fix:
	Port tcpdump's print-pfsync.c, as well as any other required
	infrastructure (eg libpcap patches) from OpenBSD.


>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list