From b958492b885e6666ef04ce17c827340fba4871e2 Mon Sep 17 00:00:00 2001 From: Sascha Wildner Date: Fri, 5 Aug 2005 15:35:53 +0000 Subject: [PATCH] Fix man page reference: tcpdump(8) -> tcpdump(1). --- share/man/man4/pflog.4 | 8 ++++---- share/man/man4/pfsync.4 | 8 ++++---- usr.sbin/pfctl/pf.os.5 | 12 ++++++------ usr.sbin/pflogd/pflogd.8 | 14 +++++++------- 4 files changed, 21 insertions(+), 21 deletions(-) diff --git a/share/man/man4/pflog.4 b/share/man/man4/pflog.4 index dd337a81b2..7be4d6535a 100644 --- a/share/man/man4/pflog.4 +++ b/share/man/man4/pflog.4 @@ -1,5 +1,5 @@ .\" $OpenBSD: pflog.4,v 1.7 2004/03/21 19:47:59 miod Exp $ -.\" $DragonFly: src/share/man/man4/pflog.4,v 1.1 2005/03/24 01:15:59 corecode Exp $ +.\" $DragonFly: src/share/man/man4/pflog.4,v 1.2 2005/08/05 15:35:52 swildner Exp $ .\" .\" Copyright (c) 2001 Tobias Weingartner .\" All rights reserved. @@ -40,7 +40,7 @@ the packet filter, .Xr pf 4 . Logged packets can easily be monitored in real time by invoking -.Xr tcpdump 8 +.Xr tcpdump 1 on the .Nm interface, or stored to disk using @@ -74,13 +74,13 @@ struct pfloghdr { # tcpdump -n -e -ttt -i pflog0 .Ed .Sh SEE ALSO +.Xr tcpdump 1 , .Xr inet 4 , .Xr inet6 4 , .Xr netintro 4 , .Xr pf 4 , .Xr ifconfig 8 , -.Xr pflogd 8 , -.Xr tcpdump 8 +.Xr pflogd 8 .Sh HISTORY The .Nm diff --git a/share/man/man4/pfsync.4 b/share/man/man4/pfsync.4 index 9d642511f2..7dbf6ca04a 100644 --- a/share/man/man4/pfsync.4 +++ b/share/man/man4/pfsync.4 @@ -1,5 +1,5 @@ .\" $OpenBSD: pfsync.4,v 1.14 2004/03/21 19:47:59 miod Exp $ -.\" $DragonFly: src/share/man/man4/pfsync.4,v 1.1 2005/03/24 01:15:59 corecode Exp $ +.\" $DragonFly: src/share/man/man4/pfsync.4,v 1.2 2005/08/05 15:35:52 swildner Exp $ .\" .\" Copyright (c) 2002 Michael Shalayeff .\" All rights reserved. @@ -39,7 +39,7 @@ interface is a pseudo-device which exposes certain changes to the state table used by .Xr pf 4 . State changes can be viewed by invoking -.Xr tcpdump 8 +.Xr tcpdump 1 on the .Nm interface. @@ -130,6 +130,7 @@ only the necessary information. # tcpdump -s1500 -evtni pfsync0 .Ed .Sh SEE ALSO +.Xr tcpdump 1, .Xr bpf 4 , .Xr inet 4 , .Xr inet6 4 , @@ -137,8 +138,7 @@ only the necessary information. .Xr pf 4 , .Xr pf.conf 5 , .Xr protocols 5 , -.Xr ifconfig 8 , -.Xr tcpdump 8 +.Xr ifconfig 8 .Sh HISTORY The .Nm diff --git a/usr.sbin/pfctl/pf.os.5 b/usr.sbin/pfctl/pf.os.5 index 2ad796ae9e..720cd87bc2 100644 --- a/usr.sbin/pfctl/pf.os.5 +++ b/usr.sbin/pfctl/pf.os.5 @@ -1,5 +1,5 @@ .\" $OpenBSD: pf.os.5,v 1.4 2003/08/28 09:41:23 jmc Exp $ -.\" $DragonFly: src/usr.sbin/pfctl/pf.os.5,v 1.2 2005/05/07 02:11:25 swildner Exp $ +.\" $DragonFly: src/usr.sbin/pfctl/pf.os.5,v 1.3 2005/08/05 15:35:52 swildner Exp $ .\" .\" Copyright (c) 2003 Mike Frantzen .\" @@ -24,7 +24,7 @@ The .Xr pf 4 firewall and the -.Xr tcpdump 8 +.Xr tcpdump 1 program can both fingerprint the operating system of hosts that originate an IPv4 TCP connection. The file consists of newline-separated records, one per fingerprint, @@ -201,7 +201,7 @@ An absolutely braindead embedded operating system fingerprint could be: .Ed .Pp The -.Xr tcpdump 8 +.Xr tcpdump 1 output of .Bd -literal # tcpdump -s128 -c1 -nv 'tcp[13] == 2' @@ -215,7 +215,7 @@ almost translates into the following fingerprint 57344:64:1:44:M1460: exampleOS:1.0::exampleOS 1.0 .Ed .Pp -.Xr tcpdump 8 +.Xr tcpdump 1 does not explicitly give the packet length. But it can usually be derived by adding the size of the IPv4 header to the size of the TCP header to the size of the TCP options. @@ -237,7 +237,7 @@ three bytes. .Pp In the above example, the packet size comes out to 44 bytes. .Sh SEE ALSO +.Xr tcpdump 1 , .Xr pf 4 , .Xr pf.conf 5 , -.Xr pfctl 8 , -.Xr tcpdump 8 +.Xr pfctl 8 diff --git a/usr.sbin/pflogd/pflogd.8 b/usr.sbin/pflogd/pflogd.8 index b802c3574f..96af59eff6 100644 --- a/usr.sbin/pflogd/pflogd.8 +++ b/usr.sbin/pflogd/pflogd.8 @@ -1,5 +1,5 @@ .\" $OpenBSD: pflogd.8,v 1.24 2004/01/16 10:45:49 jmc Exp $ -.\" $DragonFly: src/usr.sbin/pflogd/pflogd.8,v 1.1 2004/09/21 21:25:28 joerg Exp $ +.\" $DragonFly: src/usr.sbin/pflogd/pflogd.8,v 1.2 2005/08/05 15:35:53 swildner Exp $ .\" .\" Copyright (c) 2001 Can Erkin Acar. All rights reserved. .\" @@ -47,14 +47,14 @@ to the packet logging interface and writes the packets to a logfile (normally .Pa /var/log/pflog ) in -.Xr tcpdump 8 +.Xr tcpdump 1 binary format. These logs can be reviewed later using the .Fl r option of -.Xr tcpdump 8 , +.Xr tcpdump 1 , hopefully offline in case there are bugs in the packet parsing code of -.Xr tcpdump 8 . +.Xr tcpdump 1 . .Pp .Nm closes and then re-opens the log file when it receives @@ -113,7 +113,7 @@ Other file parsers may desire a higher snaplen. Check the integrity of an existing log file, and return. .It Ar expression Selects which packets will be dumped, using the regular language of -.Xr tcpdump 8 . +.Xr tcpdump 1 . .El .Sh FILES .Bl -tag -width /var/run/pflogd.pid -compact @@ -178,12 +178,12 @@ the wi0 interface: # tcpdump -n -e -ttt -i pflog0 inbound and action block and on wi0 .Ed .Sh SEE ALSO +.Xr tcpdump 1 , .Xr pcap 3 , .Xr pf 4 , .Xr pflog 4 , .Xr pf.conf 5 , -.Xr newsyslog 8 , -.Xr tcpdump 8 +.Xr newsyslog 8 .Sh HISTORY The .Nm -- 2.28.0