| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
| |
to tcp.h, since don't use the system headers now anyway it was just
making up for our own tcp.h.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
checksum, fetch it by casting the pointer to "const u_int8_t *" rather
than "const char *" - casting it to "const char *" causes it to be
sign-extended, perhaps causing 16 1 bits to be added in at the top and,
at least on big-endian platforms (where "htons()" does nothing, meaning
it won't trim off the extra 16 bits) with signed "char"s (e.g., SPARC),
causing the checksum to be computed incorrectly and causing it to
incorrectly be reported as bad.
|
|
|
|
| |
from: jinmei@kame.net
|
|
|
|
|
|
|
|
| |
ip6.h is almost normal RFC2292 header.
icmp6.h has couple of extensions (not covered by RFC2292),
like MLD, ICMPv6 nodeinfo, and router renumber.
XXX how to synchronize with future kame changes?
|
|
|
|
|
|
| |
come with exact size. while at it, correct signedness of ip/udp header field.
nuke most of the use of bitfield.
TODO: bitfield in namser.h
|
|
|
|
|
| |
u_int x:4, y:4; will occupy sizeof(int) on some platforms, while it occupy
1 byte on some platforms. use macro to decode th_off.
|
| |
|
|
|
|
| |
"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".
|
|
|
|
|
|
|
|
|
| |
by dissectors, and have dissectors include them rather than
<netinet/udp.h>, <netinet/udp_var.h>, or <netinet/tcp.h>, if they
actually need that stuff.
Remove all unnecessary includes of <netinet/udp*.h> or <netinet/tcp*.h>
files.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
text, as per RFC 1122:
4.2.2.12 RST Segment: RFC-793 Section 3.4
A TCP SHOULD allow a received RST segment to include data.
DISCUSSION
It has been suggested that a RST segment could contain
ASCII text that encoded and explained the cause of the
RST. No standard has yet been established for such
data.
as some TCP implementations (e.g., HP-UX 11.0) do that.
Clean up the code that prints the payload of non-RST segments.
|
| |
|
| |
|
|
|
|
| |
From Francisco Matias Cuenca-Acuna <mcuenca@george.rutgers.edu>
|
| |
|
|
|
|
|
|
| |
use u_long for it.
use u_int{16,32}_t.
ECN support improvement (from net/openbsd).
|
|
|
|
|
| |
- 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.
|
|
|
|
|
|
|
| |
the ports.
- Print the TCP port information if the TCP header is truncated after the
ports.
- Print the sequence number if -vv even if you wouldn't normally.
|
|
|
|
| |
packets
|
| |
|
| |
|
|
|
|
|
|
|
| |
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?
|
| |
|
|
|