Speak of a "link-layer header type" rather than a "link-layer type"; a

given link-layer type, e.g. 802.11, might have multiple header types
(802.11, 802.11 plus various radio headers, Ethernet), and multiple
link-layer types might have the same header type (802.11 interfaces
might supply Ethernet headers, and Linux loopback interfaces supply
Ethernet headers as well).

Point to tcpdump.org's page of link-layer header types, rather than to
the net/bpf.h header that 1) might not exist on your system and 2) might
not be up-to-date if it does exist.

svn path=/trunk/; revision=39529
This commit is contained in:
Guy Harris 2011-10-23 22:49:11 +00:00
parent ed79560623
commit 051d46467f
1 changed files with 6 additions and 5 deletions

View File

@ -108,11 +108,12 @@ hex. This corresponds to the C<-A> option for I<od>.
=item -l
Specify the link-layer type of this packet. Default is Ethernet
(1). See I<net/bpf.h> for the complete list of possible
encapsulations. Note that this option should be used if your dump is a
complete hex dump of an encapsulated packet and you wish to specify
the exact type of encapsulation. Example: I<-l 7> for ARCNet packets.
Specify the link-layer header type of this packet. Default is Ethernet
(1). See L<http://www.tcpdump.org/linktypes.html> for the complete list
of possible encapsulations. Note that this option should be used if
your dump is a complete hex dump of an encapsulated packet and you wish
to specify the exact type of encapsulation. Example: I<-l 7> for ARCNet
packets.
=item -e E<lt>l3pidE<gt>