Date: Sat, 21 Jun 2008 07:30:30 +1000 (EST) From: Peter Jeremy <peterjeremy@optushome.com.au> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/124825: tcpdump(8) does not support pfsync(4) data Message-ID: <200806202130.m5KLUUjR093930@server.vk2pj.dyndns.org> Resent-Message-ID: <200806211220.m5LCK4Zp046110@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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@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:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200806202130.m5KLUUjR093930>