1999-10-08 07:47:09 +08:00
|
|
|
/*
|
|
|
|
* Copyright (c) 1991, 1993, 1994, 1995, 1996, 1997
|
|
|
|
* The Regents of the University of California. All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that: (1) source code distributions
|
|
|
|
* retain the above copyright notice and this paragraph in its entirety, (2)
|
|
|
|
* distributions including binary code include the above copyright notice and
|
|
|
|
* this paragraph in its entirety in the documentation or other materials
|
|
|
|
* provided with the distribution, and (3) all advertising materials mentioning
|
|
|
|
* features or use of this software display the following acknowledgement:
|
|
|
|
* ``This product includes software developed by the University of California,
|
|
|
|
* Lawrence Berkeley Laboratory and its contributors.'' Neither the name of
|
|
|
|
* the University nor the names of its contributors may be used to endorse
|
|
|
|
* or promote products derived from this software without specific prior
|
|
|
|
* written permission.
|
|
|
|
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
|
|
|
|
* WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
|
|
|
|
* MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef lint
|
|
|
|
static const char rcsid[] =
|
2002-12-19 17:39:10 +08:00
|
|
|
"@(#) $Header: /tcpdump/master/tcpdump/print-null.c,v 1.47 2002-12-19 09:39:13 guy Exp $ (LBL)";
|
1999-11-21 17:36:43 +08:00
|
|
|
#endif
|
|
|
|
|
|
|
|
#ifdef HAVE_CONFIG_H
|
|
|
|
#include "config.h"
|
1999-10-08 07:47:09 +08:00
|
|
|
#endif
|
|
|
|
|
2002-08-01 16:52:55 +08:00
|
|
|
#include <tcpdump-stdinc.h>
|
1999-10-08 07:47:09 +08:00
|
|
|
|
|
|
|
#include <pcap.h>
|
|
|
|
#include <stdio.h>
|
|
|
|
#include <string.h>
|
|
|
|
|
|
|
|
#include "interface.h"
|
|
|
|
#include "addrtoname.h"
|
|
|
|
|
2000-09-23 16:54:24 +08:00
|
|
|
#include "ip.h"
|
2000-10-07 13:53:09 +08:00
|
|
|
#ifdef INET6
|
|
|
|
#include "ip6.h"
|
|
|
|
#endif
|
2000-09-23 16:54:24 +08:00
|
|
|
|
1999-10-08 07:47:09 +08:00
|
|
|
#ifndef AF_NS
|
|
|
|
#define AF_NS 6 /* XEROX NS protocols */
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/*
|
Handle DLT_NULL correctly - the AF_ value is in host byte order, which
may not be *our* byte order if we're reading a capture file from another
machine; we currently handle that by checking whether it looks like an
integer < 65536 or not and, if it's not, byte-swap it.
This also lets us handle OpenBSD DLT_LOOP as well - it's like DLT_NULL
except that the AF_ value is in *network* byte order.
(Old-style Linux loopback captures were also DLT_NULL, but the header
had an Ethernet type in it; there have also been captures where the
header was a PPP header. For now, we just continue to assume that all
DLT_NULL packets are IP, and check the IP version field to decide
whether it's IPv4, IPv6, or something else.
We may want to consider adopting Ethereal's heuristics, which would at
least mean we wouldn't be reporting bogus packet types for old-style
Linux loopback captures and those weird PPP - ISDN4BSD? - captures,
although the version of libpcap that goes with this version of tcpdump
doesn't produce bogus DLT_NULL captures for Linux loopback devices.)
2000-12-17 06:00:50 +08:00
|
|
|
* The DLT_NULL packet header is 4 bytes long. It contains a host-byte-order
|
|
|
|
* 32-bit integer that specifies the family, e.g. AF_INET.
|
|
|
|
*
|
|
|
|
* Note here that "host" refers to the host on which the packets were
|
|
|
|
* captured; that isn't necessarily *this* host.
|
|
|
|
*
|
|
|
|
* The OpenBSD DLT_LOOP packet header is the same, except that the integer
|
|
|
|
* is in network byte order.
|
1999-10-08 07:47:09 +08:00
|
|
|
*/
|
|
|
|
#define NULL_HDRLEN 4
|
|
|
|
|
|
|
|
static void
|
Handle DLT_NULL correctly - the AF_ value is in host byte order, which
may not be *our* byte order if we're reading a capture file from another
machine; we currently handle that by checking whether it looks like an
integer < 65536 or not and, if it's not, byte-swap it.
This also lets us handle OpenBSD DLT_LOOP as well - it's like DLT_NULL
except that the AF_ value is in *network* byte order.
(Old-style Linux loopback captures were also DLT_NULL, but the header
had an Ethernet type in it; there have also been captures where the
header was a PPP header. For now, we just continue to assume that all
DLT_NULL packets are IP, and check the IP version field to decide
whether it's IPv4, IPv6, or something else.
We may want to consider adopting Ethereal's heuristics, which would at
least mean we wouldn't be reporting bogus packet types for old-style
Linux loopback captures and those weird PPP - ISDN4BSD? - captures,
although the version of libpcap that goes with this version of tcpdump
doesn't produce bogus DLT_NULL captures for Linux loopback devices.)
2000-12-17 06:00:50 +08:00
|
|
|
null_print(u_int family, u_int length)
|
1999-10-08 07:47:09 +08:00
|
|
|
{
|
2000-12-04 14:47:17 +08:00
|
|
|
if (nflag)
|
Handle DLT_NULL correctly - the AF_ value is in host byte order, which
may not be *our* byte order if we're reading a capture file from another
machine; we currently handle that by checking whether it looks like an
integer < 65536 or not and, if it's not, byte-swap it.
This also lets us handle OpenBSD DLT_LOOP as well - it's like DLT_NULL
except that the AF_ value is in *network* byte order.
(Old-style Linux loopback captures were also DLT_NULL, but the header
had an Ethernet type in it; there have also been captures where the
header was a PPP header. For now, we just continue to assume that all
DLT_NULL packets are IP, and check the IP version field to decide
whether it's IPv4, IPv6, or something else.
We may want to consider adopting Ethereal's heuristics, which would at
least mean we wouldn't be reporting bogus packet types for old-style
Linux loopback captures and those weird PPP - ISDN4BSD? - captures,
although the version of libpcap that goes with this version of tcpdump
doesn't produce bogus DLT_NULL captures for Linux loopback devices.)
2000-12-17 06:00:50 +08:00
|
|
|
printf("AF %u ", family);
|
2000-12-04 14:47:17 +08:00
|
|
|
else {
|
|
|
|
switch (family) {
|
1999-10-08 07:47:09 +08:00
|
|
|
|
2000-12-04 14:47:17 +08:00
|
|
|
case AF_INET:
|
|
|
|
printf("ip ");
|
|
|
|
break;
|
1999-10-08 07:47:09 +08:00
|
|
|
|
1999-10-30 13:11:06 +08:00
|
|
|
#ifdef INET6
|
2000-12-04 14:47:17 +08:00
|
|
|
case AF_INET6:
|
|
|
|
printf("ip6 ");
|
|
|
|
break;
|
1999-10-30 13:11:06 +08:00
|
|
|
#endif
|
|
|
|
|
2000-12-04 14:47:17 +08:00
|
|
|
case AF_NS:
|
|
|
|
printf("ns ");
|
|
|
|
break;
|
1999-10-08 07:47:09 +08:00
|
|
|
|
2000-12-04 14:47:17 +08:00
|
|
|
default:
|
Handle DLT_NULL correctly - the AF_ value is in host byte order, which
may not be *our* byte order if we're reading a capture file from another
machine; we currently handle that by checking whether it looks like an
integer < 65536 or not and, if it's not, byte-swap it.
This also lets us handle OpenBSD DLT_LOOP as well - it's like DLT_NULL
except that the AF_ value is in *network* byte order.
(Old-style Linux loopback captures were also DLT_NULL, but the header
had an Ethernet type in it; there have also been captures where the
header was a PPP header. For now, we just continue to assume that all
DLT_NULL packets are IP, and check the IP version field to decide
whether it's IPv4, IPv6, or something else.
We may want to consider adopting Ethereal's heuristics, which would at
least mean we wouldn't be reporting bogus packet types for old-style
Linux loopback captures and those weird PPP - ISDN4BSD? - captures,
although the version of libpcap that goes with this version of tcpdump
doesn't produce bogus DLT_NULL captures for Linux loopback devices.)
2000-12-17 06:00:50 +08:00
|
|
|
printf("AF %u ", family);
|
2000-12-04 14:47:17 +08:00
|
|
|
break;
|
|
|
|
}
|
1999-10-08 07:47:09 +08:00
|
|
|
}
|
2000-12-04 14:47:17 +08:00
|
|
|
printf("%d: ", length);
|
1999-10-08 07:47:09 +08:00
|
|
|
}
|
|
|
|
|
Handle DLT_NULL correctly - the AF_ value is in host byte order, which
may not be *our* byte order if we're reading a capture file from another
machine; we currently handle that by checking whether it looks like an
integer < 65536 or not and, if it's not, byte-swap it.
This also lets us handle OpenBSD DLT_LOOP as well - it's like DLT_NULL
except that the AF_ value is in *network* byte order.
(Old-style Linux loopback captures were also DLT_NULL, but the header
had an Ethernet type in it; there have also been captures where the
header was a PPP header. For now, we just continue to assume that all
DLT_NULL packets are IP, and check the IP version field to decide
whether it's IPv4, IPv6, or something else.
We may want to consider adopting Ethereal's heuristics, which would at
least mean we wouldn't be reporting bogus packet types for old-style
Linux loopback captures and those weird PPP - ISDN4BSD? - captures,
although the version of libpcap that goes with this version of tcpdump
doesn't produce bogus DLT_NULL captures for Linux loopback devices.)
2000-12-17 06:00:50 +08:00
|
|
|
/*
|
|
|
|
* Byte-swap a 32-bit number.
|
|
|
|
* ("htonl()" or "ntohl()" won't work - we want to byte-swap even on
|
|
|
|
* big-endian platforms.)
|
|
|
|
*/
|
|
|
|
#define SWAPLONG(y) \
|
|
|
|
((((y)&0xff)<<24) | (((y)&0xff00)<<8) | (((y)&0xff0000)>>8) | (((y)>>24)&0xff))
|
|
|
|
|
2002-12-19 17:39:10 +08:00
|
|
|
u_int
|
|
|
|
null_if_print(const struct pcap_pkthdr *h, const u_char *p)
|
1999-10-08 07:47:09 +08:00
|
|
|
{
|
|
|
|
u_int length = h->len;
|
|
|
|
const struct ip *ip;
|
Handle DLT_NULL correctly - the AF_ value is in host byte order, which
may not be *our* byte order if we're reading a capture file from another
machine; we currently handle that by checking whether it looks like an
integer < 65536 or not and, if it's not, byte-swap it.
This also lets us handle OpenBSD DLT_LOOP as well - it's like DLT_NULL
except that the AF_ value is in *network* byte order.
(Old-style Linux loopback captures were also DLT_NULL, but the header
had an Ethernet type in it; there have also been captures where the
header was a PPP header. For now, we just continue to assume that all
DLT_NULL packets are IP, and check the IP version field to decide
whether it's IPv4, IPv6, or something else.
We may want to consider adopting Ethereal's heuristics, which would at
least mean we wouldn't be reporting bogus packet types for old-style
Linux loopback captures and those weird PPP - ISDN4BSD? - captures,
although the version of libpcap that goes with this version of tcpdump
doesn't produce bogus DLT_NULL captures for Linux loopback devices.)
2000-12-17 06:00:50 +08:00
|
|
|
u_int family;
|
1999-10-08 07:47:09 +08:00
|
|
|
|
Handle DLT_NULL correctly - the AF_ value is in host byte order, which
may not be *our* byte order if we're reading a capture file from another
machine; we currently handle that by checking whether it looks like an
integer < 65536 or not and, if it's not, byte-swap it.
This also lets us handle OpenBSD DLT_LOOP as well - it's like DLT_NULL
except that the AF_ value is in *network* byte order.
(Old-style Linux loopback captures were also DLT_NULL, but the header
had an Ethernet type in it; there have also been captures where the
header was a PPP header. For now, we just continue to assume that all
DLT_NULL packets are IP, and check the IP version field to decide
whether it's IPv4, IPv6, or something else.
We may want to consider adopting Ethereal's heuristics, which would at
least mean we wouldn't be reporting bogus packet types for old-style
Linux loopback captures and those weird PPP - ISDN4BSD? - captures,
although the version of libpcap that goes with this version of tcpdump
doesn't produce bogus DLT_NULL captures for Linux loopback devices.)
2000-12-17 06:00:50 +08:00
|
|
|
memcpy((char *)&family, (char *)p, sizeof(family));
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This isn't necessarily in our host byte order; if this is
|
|
|
|
* a DLT_LOOP capture, it's in network byte order, and if
|
|
|
|
* this is a DLT_NULL capture from a machine with the opposite
|
|
|
|
* byte-order, it's in the opposite byte order from ours.
|
|
|
|
*
|
|
|
|
* If the upper 16 bits aren't all zero, assume it's byte-swapped.
|
|
|
|
*/
|
|
|
|
if ((family & 0xFFFF0000) != 0)
|
|
|
|
family = SWAPLONG(family);
|
|
|
|
|
1999-10-08 07:47:09 +08:00
|
|
|
length -= NULL_HDRLEN;
|
|
|
|
|
|
|
|
ip = (struct ip *)(p + NULL_HDRLEN);
|
|
|
|
|
|
|
|
if (eflag)
|
Handle DLT_NULL correctly - the AF_ value is in host byte order, which
may not be *our* byte order if we're reading a capture file from another
machine; we currently handle that by checking whether it looks like an
integer < 65536 or not and, if it's not, byte-swap it.
This also lets us handle OpenBSD DLT_LOOP as well - it's like DLT_NULL
except that the AF_ value is in *network* byte order.
(Old-style Linux loopback captures were also DLT_NULL, but the header
had an Ethernet type in it; there have also been captures where the
header was a PPP header. For now, we just continue to assume that all
DLT_NULL packets are IP, and check the IP version field to decide
whether it's IPv4, IPv6, or something else.
We may want to consider adopting Ethereal's heuristics, which would at
least mean we wouldn't be reporting bogus packet types for old-style
Linux loopback captures and those weird PPP - ISDN4BSD? - captures,
although the version of libpcap that goes with this version of tcpdump
doesn't produce bogus DLT_NULL captures for Linux loopback devices.)
2000-12-17 06:00:50 +08:00
|
|
|
null_print(family, length);
|
1999-10-08 07:47:09 +08:00
|
|
|
|
2000-10-03 10:54:54 +08:00
|
|
|
switch (IP_V(ip)) {
|
1999-12-22 14:27:19 +08:00
|
|
|
case 4:
|
|
|
|
ip_print((const u_char *)ip, length);
|
1999-11-21 11:48:05 +08:00
|
|
|
break;
|
|
|
|
#ifdef INET6
|
|
|
|
case 6:
|
1999-12-22 14:27:19 +08:00
|
|
|
ip6_print((const u_char *)ip, length);
|
1999-11-21 11:48:05 +08:00
|
|
|
break;
|
|
|
|
#endif /* INET6 */
|
1999-12-22 14:27:19 +08:00
|
|
|
default:
|
2000-10-03 10:54:54 +08:00
|
|
|
printf("ip v%d", IP_V(ip));
|
1999-11-21 11:48:05 +08:00
|
|
|
break;
|
|
|
|
}
|
1999-10-08 07:47:09 +08:00
|
|
|
|
2002-12-19 17:39:10 +08:00
|
|
|
return (NULL_HDRLEN);
|
1999-10-08 07:47:09 +08:00
|
|
|
}
|
|
|
|
|