| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
The rest of the low-level print-*.c handlers need the infodelay
wrapping too.
|
| |
|
|
|
|
|
|
|
|
|
| |
Martin Husemann <martin@netbsd.org>.
Clean up PPPoE dissector - get rid of unused variable, and have it just
use its first argument as a pointer to the PPPoE packet (which may also
make it work if, for example, you have PPPoE packets wrapped inside VLAN
headers).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
live captures with a "cooked" (SOCK_DGRAM) rather than a "raw"
(SOCK_RAW) PF_PACKET socket; it includes a bunch of the fields from the
"struct sockaddr_ll" you get in a "recvfrom()", including the Ethernet
protocol field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.)
|
|
|
|
| |
(Tested with libpcap-0.4 as comes with FreeBSD 3.4)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
application won't build with any other version of libpcap, which means
that a lot of applications won't use them. In addition,
"pcap_linktype()" needs to return DLT_ values, so that platforms that
build libpcap as a shared library won't break binary compatibility if
they update to this version of libpcap.
Instead, we map from DLT_ values to LINKTYPE_ values when writing
savefiles, and map from LINKTYPE_ values to DLT_ values when reading
savefiles, so that savefiles don't have platform-dependent DLT_ values
in the header as the link type, they have platform-independent LINKTYPE_
values.
This means we don't need to make DLT_ATM_RFC1483, DLT_RAW, etc. have
platform-independent values starting at 100 - only the values in the
savefile header need to be like that.
|
|
|
|
| |
"n_long", and "n_time", defined in that file, with other types.
|
|
|
|
|
|
|
|
|
|
|
| |
have dissectors include them rather than <netinet/ip.h> or
<netinet/ip_var.h>, if they actually need that stuff.
Put the declarations of the ICMP stuff directly into "print-icmp.c".
Remove all unnecessary includes of <netinet/ip*.h> files.
Copy the byte-order stuff from "nameser.h" into "tcp.h".
|
|
|
|
|
|
|
| |
RFC 1662, or Cisco point-to-point with HDLC framing, as per seciont
4.3.1 of RFC 1547; there's always an address and control octet at the
beginning of these packets, but they're not necessarily 0xff 0x03),
which we map to PCAP_ENCAP_PPP_HDLC.
|
|
|
|
|
| |
also use those DLT_ codes that older libpcaps may have used directly
rather than mapped to PCAP_ENCAP_ codes, if they're defined.
|
|
|
|
|
| |
NetBSD ones; use it for DLT_IEEE802, which in many OSes is used for
token ring.
|
| |
|
|
|
|
| |
(cleanup): make static
|
|
|
|
|
| |
also check return value from getopt() against -1 and not EOF
From Francisco Matias Cuenca-Acuna <mcuenca@george.rutgers.edu>
|
| |
|
| |
|
|
|
|
| |
patch from "Gilbert Ramirez Jr." <gram@xiexie.org>
|
| |
|
|
|
|
|
| |
there seem to be couple of unsafe use of strcat and strcpy - we should
bring in strl{cat,cpy}.
|
| |
|
| |
|
|
|
|
|
| |
if you can actually run a program linked against it. The
-enable-libsmi is gone as it should not be needed anymore.
|
|
|
|
|
| |
- add -X option for ascii printing.
- telnet command sequences (ff xx xx) will be dumped with -vvv -X.
|
|
|
|
|
|
|
|
|
|
|
| |
API.
* print-bgp.c: improve options printing. ugly code exists for
unaligned option parsing (need some fix).
* const poisoning in SMB decoder.
* make dump format back to original. someone may want to add an
option to do ascii printing, but keep the default behavior as is
for scripts used in many places.
* -Wall -Werror clean checks.
|
|
|
|
|
|
|
|
| |
Here is a new version of the libsmi patch for tcpdump. It provides
some bug fixes and some enhancements such as access checking and
better range checking. The patch also fixed a few bugs in the
print_snmp.c module of tcpdump itself (unrelated to the usage of
libsmi).
|
| |
|
| |
|
|
|
|
|
|
|
| |
- endian checks (use WORDS_BIGENDIAN)
- fallback def for IPPROTO_{AH,ESP}
- sa_len issues
- do not use bittypes.h, respect AC_LBL_CHECK_TYPES
|
|
|
|
|
|
|
| |
Hope I did not break anything. Portability on IPv4-only node needs checking,
I'll do this very soon. (sorry for rather jumbo commit)
XXx what is _FAVOR_BSD?
|
|
|
|
| |
AH/ESP printing.
|
| |
|
|
|