cdpr - Cisco Discovery Protocol Reporter
Copyright (c) 2002-2008 MonkeyMental.com

*Version 2.4

Work around OSX buffering issue that prevented the bpf interface from passing the packets up to the decoder

Allow reading from a pcap file using -r for debugging purposes.

*Version 2.3

Decode IPv6 responses in the CDP packet and send them in the http response if
using cdpr server updates.

Sample of GET request:
?switch_ip=6x.3x.2xx.2xx&switch_ip6=fxxx::2xx:cxxx:fxxx:2xxx&switch_ip6=2xxx:1xxx:2xx::1&port=GigabitEthernet1%2F45&host=monkeymental.com

*Version 2.2.1

Fixed the logic that will select a default port of 80 if no port is specified.
Updated copyrights and license details on all source files with the exception
of the MS Visual Studio project files. I'm unsure if I can add license and
copyright info to these files and still have them work. However, these are
not source files, so think of them as nothing more than Makefiles for Visual
Studio.

*Version 2.2.0

Added the ability to specify what port to send the updates to.

*Version 2.1.0

This version provides the ability to include a timeout so that you can put cdpr
into startup scripts and not have it hang if for some reason a CDP packet is never
received (i.e. CDP is disabled, machine is plugged into a hub, etc.) The following
command line option has been added:

-t timeout: Specify a timeout (in seconds) to wait for a CDP packet.

Please note that the default time between CDP packets is 60 seconds so you should
set your timeout to something greater than 60. There is a default timeout of 5 minutes
so that should you not provide a timeout, cdpr will still exit if there is no CDP
packet received within 5 minutes.

This version also allows you to specify the server and URL to send CDP updates to on
the command line. The following command line options have been added:

-s server: Server to send information to requires -p (overridden by -u)
-p path: Path of server script to send data to requires -s (overridden by -u)

As you can see if you specify -s, -p and -u on the command line, the config file is actually
used, and the -s and -p options are ignored. Both the -s and -p options must be specified and
cdpr will exit if only one of them is given. An example as to how to use the -s and -p flags:

	cdpr -d eth0 -s localhost -p /cgi-bin/cdprs.cgi -t 120

This will listen for a CDP announcement on device eth0 for up to 2 minutes (120 seconds) and
send the results to the webserver running on the local machine by calling the /cgi-bin/cdprs.cgi
page.

*Versions 2.0.1 - 2.0.5
These version were never officially released, they were code cleanups and timeout implementation.

*Version 2.0.0

This version provides the functionallity to report CDP data back to a centralized server.
Please see the file README.cdprs for details, but in general, the following command line
options have been added:

-u conf.file: Send updates to the host listed in the config file.
-l location: Send a location string to help identify the port.
-n hostname: Override the hostname sent to the server.

Platform Update: Some of the newer HP Switch firmware will broadcast CDP packets. cdpr
will decode these packets just the same as they would if they came from a Cisco product.
It was tested on a HP ProCurve 4000M running revision C.09.16.

*Version 1.0.8

Support for ARM processor. Tested on the Sharp Zaurus SL-5500.

*Version 1.0.7

Support for Win32 clients please read README.Win32.
To support the Win32 clients, modified so that if a network device is not specified
on the command line with -d, then to find all devices that are capable of being used
by the pcap libary and provide a selection list.

*Version 1.0.6

Fixed up some more bus errors/segmentation faults.

*Version 1.0.5

Copy packet data to local variable to resolve alignment issues that caused Bus Errors
on some architectures. cdpr has now been compiled and tested on the following
Operating Systems:
 - Linux 2.4.18 (x86)
 - FreeBSD 4.6 (x86)
 - Sun Solaris 8 (SPARC)
 - HP HP-UX 11.11 (PA-Risc)
 - IBM AIX 4.3.3 (PowerPC)

On some operating systems (like Solaris) the u_int* typedefs are not defined, to resolve
this issue, include u_ints.h in cdp.h.

On AIX you must load the dlpi kernel module using the following command:

 strload -f /etc/dlpi.conf

On AIX you may recieve some warnings about "Primitive issued in improper state",
these can be safely ignored.

On HP-UX you may recieve a warning about "any missing unit number", this can be
safely ignored

*Version 1.0.4

Added 1 ms timeout to pcap_open_live to fix BSD hang issues.

*Version 1.0.3

Loop on pcap_next until a valid packet is received, some implementations of pcap will
return a null. Patch provided by Martin Buck <martin.buck@ascom.ch>.

*Version 1.0.2

Use a new filter to better identify CDP packets. Solves the majority of the segfaults
due to trying to decode a non-CDP packet (i.e. a VTP packet)

*Version 1.0.1

Add preprocessor macros to only include the Link Type defines provided by the pcap and
bpf headers.

*Version 1.0.0

I originally wrote this program to report which switch, and port a machine
is connected to. In a large environment sometimes it is difficult to determine
which port on which switch a machine is connected to.

By default (with no command line options) cdpr will determine a network interface
to open, put into promiscuous mode and wait for a single CDP packet to be received.

On multi-homed machines, you can specify which interface to use with the -d option.

Example (to determine which switch/port eth1 is connected to):
	cdpr -d eth1

You can dump the whole cdp packet using -v (more v's = more output).

Sample Output:
cdpr - Cisco Discovery Protocol Reporter Version 1.0.0
Copyright (c) 2002 - MonkeyMental.com

Using Device: eth0
Waiting for CDP advertisement, default config is to transmit CDP packets every 60 seconds
Device ID
  value:  mtview-3548-access-1.i2.com
Addresses
  value:  10.100.230.14
Port ID
  value:  FastEthernet0/4

As you can see above, by default CDP packets are broadcast every 60 seconds, cdpr will wait
until a CDP packet is received.

I hope you find this utility useful. Thanks to Manfred Siemsen for helping to decode the
packet data.

Regards,
Lance O'Connor
lance@monkeymental.com

Version 1.0.8+ update: Supports the WinPcap Version 3.0 release

cdpr version 1.0.7 supports Win32 clients, it has been tested against
WinPcap version 3.0 alpha 4 (http://winpcap.polito.it/install/default.htm).

I have compiled it with Microsoft Visual C++ 6.0.

To build it from source download the WinPcap Developers Pack version
3.0 alpha 4 and unzip it into the cdpr source tree.

Your directory structure should looks something like this:

\cdpr
 +-wpdpack
  +-docs
  +-Examples
  +-Include
  +-Lib

I have included the Workspace files so that you should be able to just
open cdpr.dsw

When you build it it will create a directory called Release and Debug and
put the appropriate binaries in each (cdpr.exe)

Lance O'Connor
lance@monkeymental.com

Version 2.0.0 of cdpr now supports transmiting the data decoded to a server.

In lieu of writing my own cdpr server, I decided that I would send the data to
a web server using a GET request. This has several advantages:

 - I didn't have to write a server
 - You can have your webserver do whatever you want with the data
 	- Put it in a database
 	- Log it to a text file
 	- etc.
 - You can write your server piece in the language of your choice (PHP, ASP, Perl, C, etc.)
   as it's just a standard HTTP GET request.

*Details on the config file

The config file should contain one line that has the host to connect to and the relative URL
to request. For example:

	[cdpr.conf]
	cdpr_svr.monkeymental.com	/cdprs.php
	<EOF>

This will instruct cdpr to connect to the machine cdpr_svr.monkeymental.com and request the URL
/cdprs/cpdrs.php. This would be the same as http://cdpr_svr.monkeymental.com/cdprs/cdprs.php in
a web browser. The server and the URL should be seperated by a whitespace character (i.e. a [Tab])

*Details on the GET request:

cdpr will execute the following query to port 80 of the server in the config file:

GET /cdprs.php??switch_ip=6x.3x.2xx.2xx&switch_ip6=fxxx::2xx:cxxx:fxxx:2xxx&switch_ip6=2xxx:1xxx:2xx::1&port=GigabitEthernet1%2F45&host=monkeymental.com HTTP/1.0

The request will have the following variables assosciated with it:

switch_ip:	The IP address of the switch the machine running cdpr is connected to.
switch_ip6: The IPv6 address of the switch the machine running cdpr is connected to (may be more than one.)
port:		The port that the machine running cdpr is connected to.
loc:		The optional location identifier passed on the command line using -l
host:		The hostname of the machine running cdpr (or whatever is passed on the command
			line if using the hostname override option -n)

How you access this data depends on what language you are writing your scripts in. If you were
using PHP, you could access them with $_GET["variable"] (i.e. $_GET["switch_ip"]) Once you have
the data in your web page/cgi script, you can do with it as you wish, such as store it in a text
file, Populate a SQL database, etc.

*Notes:

A few things to note about the CDPR Server functionallity:

	- Any output from the webserver is ignored
	- Only one attempt is made to send the data
	- Port and location are urlencoded to handle any "odd" characters (like a /)