summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Backout CHANGES update - wrong branchtcpdump_3_9tcpdump-3.9ken2008-10-151-16/+1
|
* Update for 4.0.0 final releaseken2008-10-151-1/+16
|
* bugfix: do proper padding calculation for LSPINGhannes2008-01-281-3/+10
|
* in tcpdump a length field has the semantics of a 'total length field'tcpdump_3_9rel8tcpdump-3.9.8hannes2007-09-211-2/+2
| | | | | | i.e. including the header - the IP6 payload length field differs from that ... highlight the difference by printing 'payload length' rather than 'length'
* From Victor Oppleman: add support for RFC 1393 traceroute.guy2007-09-143-2/+5
|
* From Christian Sievers: add support for TFTP option acknowledgementsguy2007-09-146-10/+102
| | | | | | | | | | (RFC 2347), and add an opening quotation mark to the error message string. Don't use the system's <arpa/tftp.h>, use our own. Update the README to reflect the current practice for submitting patches, and fix a spelling error.
* From pfhunt on SourceForge:guy2007-09-142-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When a packet contains an IPv6 options header followed by an unknown IPv6 protocol payload, tcpdump displays the proto ID for the known option header, not for the unknown payload. For example, this is the output for an IPv6 packet containing a destination options header, followed by a payload of (unknown) protocol 138: # tcpdump -s 128 -i eth1 tcpdump: WARNING: addresses not searched tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 128 bytes 11:44:40.862572 I IP6 2007::10:5:2:163 > 2007::10:5:2:164: DSTOPT ip-proto-60 16 The ip-proto-60 refers to the destination option header (DSTOPT), rather than displaying the unknown option 138, which I think would be more informative. The attached patch fixes this problem. With the patch applied, the output for the packet is: # tcpdump -s 128 -i eth1 tcpdump: WARNING: addresses not searched tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 128 bytes 11:48:26.160462 I IP6 2007::10:5:2:163 > 2007::10:5:2:164: DSTOPT ip-proto-138 16
* Propagateguy2007-09-141-3/+3
| | | | | | | | | | revision 1.118 date: 2006-05-11 19:14:55 -0700; author: guy; state: Exp; lines: +2 -2 "ether.h" defines more than we need, and, on some platforms, redefines ether_header (which is one of the things we don't need). Just define ETHER_ADDR_LEN to 6 if it's not defined - it can't be anything but 6. to the x.9 branch, to fix build problems on Solaris.
* Fixed a compilation problem: getnameinfo() was not linked.gianluca2007-09-131-0/+1
|
* From Chris Larson: don't cut off the last byte of the chunk payload.guy2007-09-132-2/+4
|
* Removed print-pflog.c from the sources.gianluca2007-09-132-5/+0
|
* Completely remove that unused "structure".guy2007-09-131-6/+1
|
* Commented out a 0-length structure that is not used.gianluca2007-09-131-1/+3
|
* Don't declare variables in the middle of a block of code; in C89, that'sguy2007-09-131-3/+3
| | | | not valid.
* Added an #ifndef WIN32 to exclude an #include directive under VC6.gianluca2007-09-131-1/+6
|
* IKEv2 is in HEAD only, not 3.9 branchken2007-09-131-2/+1
|
* Update with todays patchesken2007-09-121-1/+3
|
* From Max Laier: check whether the system has <net/pfvar.h> and:guy2007-09-1210-5431/+5286
| | | | | | | | | | | if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
* Prep for 3.9.8 releaseken2007-09-102-3/+16
|
* From Francois-Xavier Le Bail: decode DCHP option 249 (Microsoft'sguy2007-08-212-2/+5
| | | | | Classless Static Route option) the same way as option 121 (RFC 3442's Classless Static Route option).
* From Francois-Xavier Le Bail: suport for the DHCP Classless Static Routeguy2007-07-242-74/+162
| | | | | | | | | | | | | | | | | | | | | | | | | | | | option (RFC 3442). Just modify the "len" variable as we parse an option - no need for a separate variable representing the amount of data left (I suspect that's why the wrong variable appears to have been used in the "trailing data length" message; I'd expect that message to indicate how much *extra* data there was in the option, not how much *total* data there was in the option). Add checks for too-short options in some cases where they were missing. In the check for the Client FQDN option, skip past what data there is in the option if it's too short, so it doesn't show up as extra data in the option. For the Agent Circuit option, for each suboption: check to make sure the suboption length doesn't go past what's left in the option; don't reject options with an option type or length of 0 (neither are forbidden by RFC 3046, and, in fact, RFC 3046 says "a sub-option length may be zero"); use fn_printn() to print the Agent Circuit ID suboption, rather than doing the equivalent ourselves with a safeputchar() loop.
* releasetar target fixed up.tcpdump_3_9rel7tcpdump-3.9.7mcr2007-07-241-13/+4
|
* updated changelog for 3.9.7.mcr2007-07-241-1/+16
|
* Handle the padding that Atheros adapters helpfully introduce between theguy2007-07-221-8/+21
| | | | 802.2 header and the body.
* Handle 802.11 frames with QoS data.guy2007-07-221-18/+24
|
* Don't attempt to dissect the payload of a no-data frame.guy2007-07-222-10/+30
|
* In print_data(), check each byte to make sure we haven't gone past theguy2007-07-151-1/+7
| | | | end of the captured packet data.
* Fix message printed for bad andX offset to correctly describe theguy2007-07-141-2/+2
| | | | badness.
* Fix problem found by the folks at www.digit-labs.org. Process all theguy2007-07-141-9/+40
| | | | | | | | | | TLVs in decode_labeled_vpn_l2(), but don't format them unless there's buffer space left. If snprintf() returns a negative value, assume we've filled up the buffer - I think some platforms used to work that way. If it returns a value greater than the amount of space left, also assume we've filled up the buffer. Fix a typo in a comment.
* Properly check for a bogus andX offset - it has to move forward, notguy2007-07-141-2/+2
| | | | just not move backward.
* updated version for next timemcr2007-07-051-1/+1
|
* Print unsigned values as such. Rename a variable to correspond to whatguy2007-06-151-14/+14
| | | | it is (a reply status).
* Some systems with BPF have a cloning device; on those systems, you justguy2007-06-151-2/+5
| | | | open /dev/bpf.
* Many UN*Xes come with libpcap, so you might not have to installguy2007-06-151-14/+15
| | | | | | | | | | | | | | | | tcpdump.org's libpcap in order to build tcpdump.org's tcpdump (the configure script doesn't assume the latest version of libpcap, so it should be possible to build tcpdump with older versions of libpcap). By default, tcpdump is installed with universal execute permissions, and no special privileges; that way, anybody can use it to read a capture. Remove the comments about capture permissions, as it applies only to systems using BPF. The tcpdump man page gives the gory details of capture permissions; refer users there. Remove the comment about libpcap; it's in the libpcap INSTALL.txt, where it belongs.
* Pick up from NetBSD a change to squelch a "should not happen"guy2007-06-151-1/+4
| | | | uninitialized reference found by Coverity.
* Pick up from NetBSD a change to use a maximum string length on the scanfguy2007-06-151-3/+6
| | | | format used to parse ACL entries.
* Propagate from the main branchguy2007-06-151-2/+28
| | | | | | | | | | | | | | | | | | | | | revision 1.29 date: 2006-06-13 22:21:38 +0000; author: guy; state: Exp; lines: +28 -2 From NetBSD: revision 1.7 date: 2006/03/25 11:43:53; author: rpaulo; state: Exp; lines: +23 -3 PR 13604: detect and print correct information for 4.4BSD/NetBSD NFS filehandles. The heuristic may or may not be wrong, but no one replied in the tcpdump-workers mailing list. Extraction of the fsid information contributed by Chuck Silvers. Discussed with Chuck Silvers. ---------------------------- revision 1.6 date: 2006/03/22 04:30:28; author: christos; state: Exp; lines: +4 -2 Coverity CID 563: Kill SUNOS3 case; it is dead code. ----------------------------
* Pick up MSG_DENIED response dissection from NetBSD; don't interpret theguy2007-06-151-8/+82
| | | | reply as a possible NFS reply if it got MSG_DENIED.
* Prep for 3.9.6 releaseken2007-04-231-1/+31
|
* add support for the olsr protocol as per rfc3626 plus the LQ extensions from ↵hannes2007-03-288-5/+416
| | | | olsr.org
* Bugfix from Carles Kishimoto <carles.kishimoto@gmail.com>:hannes2007-03-181-3/+3
| | | | the port and prio fields of mstp PDUs need to be properly shifted.
* From From Carles Kishimoto <carles.kishimoto@gmail.com>:hannes2007-03-091-3/+9
| | | | print 802.1s digest
* From Swaminathan Chandrasekaran <chander@juniper.net>:hannes2007-03-082-6/+165
| | | | add support for Multiple-STP as per 802.1s
* minor typo: should be SPT instead of STPhannes2007-03-071-3/+3
|
* bugfix: root-pathcost is not a time-quantityhannes2007-03-071-2/+2
|
* From Hannes Gredler <hannes@juniper.net>:hannes2007-03-061-57/+156
| | | | | | | rework of the STP printer From From Carles Kishimoto <carles.kishimoto@gmail.com>: add support for rapid-SPT as per 802.1w
* bugfix: the Multi-topology header is just at the beginning of the TLV and ↵hannes2007-03-021-13/+15
| | | | not before every prefix
* From Carles Kishimoto <carles.kishimoto@gmail.com>:hannes2007-02-261-3/+126
| | | | add support for OIF RSVP Extensions UNI 1.0 Rev. 2
* move AF specific stuff into dedicated filehannes2007-02-269-92/+148
|
* From Carles Kishimoto <carles.kishimoto@gmail.com>:hannes2007-02-261-2/+62
| | | | add support for the GMPLS 'label set' RSVP object.
View Lorry Controller Status