From ea72be86078d1b8bac48c79b831e0caca4255870 Mon Sep 17 00:00:00 2001
From: Guy Harris <guy@alum.mit.edu>
Date: Thu, 8 Aug 2013 04:29:08 +0000
Subject: Speak of the "-d encap:" value as a linktype, rather than a DLT; if a
 name is specified, it currently must be a DLT_ name rather than a LINKTYPE_
 name, as we use libpcap to do the mapping and it currently has no API to map
 LINKTYPE_ names to values, but if a number is specified, it could either be a
 LINKTYPE_ name or a DLT_ name if the two are different, and we want to
 encourage the use of LINKTYPE_ values.

Note that in comments.

svn path=/trunk/; revision=51204
---
 doc/rawshark.pod | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'doc')

diff --git a/doc/rawshark.pod b/doc/rawshark.pod
index 0514d41efb..3cdc0ac962 100644
--- a/doc/rawshark.pod
+++ b/doc/rawshark.pod
@@ -6,7 +6,7 @@ rawshark - Dump and analyze raw pcap data
 =head1 SYNOPSIS
 
 B<rawshark>
-S<[ B<-d> E<lt>encap:dltE<gt>|E<lt>proto:protonameE<gt> ]>
+S<[ B<-d> E<lt>encap:linktypeE<gt>|E<lt>proto:protonameE<gt> ]>
 S<[ B<-F> E<lt>field to displayE<gt> ]>
 S<[ B<-h> ]>
 S<[ B<-l> ]>
@@ -111,7 +111,8 @@ A complete list of DLTs can be found at
 L<http://www.tcpdump.org/linktypes.html>.
 
 B<encap>:I<number> Packet data should be dissected using the
-libpcap/WinPcap DLT I<number>, e.g. B<encap:105> for raw IEEE 802.11. 
+libpcap/WinPcap LINKTYPE_ I<number>, e.g. B<encap:105> for raw IEEE
+802.11 or B<encap:101> for raw IP.
 
 B<proto>:I<protocol> Packet data should be passed to the specified Wireshark
 protocol dissector, e.g. B<proto:http> for HTTP data.
-- 
cgit v1.2.3