Project

General

Profile

WireSharkPage » History » Version 1

zecke, 04/22/2017 04:18 PM

1 1 zecke
= Extending Wireshark =
2 1 zecke
The !WireShark packet sniffer normally doesn't support APCO P25. If you want to sniff P25 traffic using !WireShark then you'll need to patch the sources and rebuild it.
3 1 zecke
4 1 zecke
=== Downloading !WireShark ===
5 1 zecke
You first need to obtain the source code for !WireShark. The stable release of !WireShark is available from the [http://www.wireshark.org/download.html downloads section of the !WireShark web-site]. On that page you should be go to the "Get !WireShark" for the stable release (1.8.5 at the time of writing). Click on "Source Code" to download the file.
6 1 zecke
7 1 zecke
=== Unpacking !WireShark ===
8 1 zecke
To unpack the source tree you need to open a shell and execute the following commands:
9 1 zecke
{{{
10 1 zecke
mkdir -p SourceCode
11 1 zecke
cd SourceCode
12 1 zecke
tar xjvf ~/Downloads/wireshark-1.8.5.tar.bz2
13 1 zecke
cd wireshark-1.8.5
14 1 zecke
}}}
15 1 zecke
(Remember your download directory may not be in ~/Downloads and the version number of !WireShark you download maybe different to that used here).
16 1 zecke
17 1 zecke
=== Patching !WireShark ===
18 1 zecke
Once you've downloaded the wireshark source tree, check out p25 plugin:
19 1 zecke
20 1 zecke
{{{
21 1 zecke
(cd plugins && svn checkout http://op25.osmocom.org/svn/trunk/wireshark/plugins/p25 p25)
22 1 zecke
}}}
23 1 zecke
24 1 zecke
This adds the necessary code to !WireShark for it to decode APCO P25 messages. A few small changes also need to be made to the !WireShark tree outside of the plugins directory. To do this the easiest way is to apply the appropriate patch. This can be done as follows:
25 1 zecke
26 1 zecke
{{{
27 1 zecke
svn checkout http://op25.osmocom.org/svn/trunk/wireshark/patches
28 1 zecke
patch -p1 < patches/wireshark-1.8.5.patch
29 1 zecke
}}}
30 1 zecke
31 1 zecke
Of course, it is inevitable that you will download a !WireShark version for which we haven't provided a patch. Don't fret - the patches will probably work for your version but if it fails to apply you may need to download one an earlier version of !WireShark for which we have a patch or make the changes manually using the existing patch as a guide.
32 1 zecke
33 1 zecke
=== Building + Installing !WireShark ===
34 1 zecke
35 1 zecke
You may need to install prerequisites beforehand. These are a minimum set for Ubuntu/Debian based systems:
36 1 zecke
{{{
37 1 zecke
sudo apt-get install bison flex libgtk2.0-dev libpcap-dev
38 1 zecke
}}}
39 1 zecke
40 1 zecke
The standard build for wireshark requires that ./autogen.sh be run first. To compile !WireShark run the following commands:
41 1 zecke
42 1 zecke
{{{
43 1 zecke
./autogen.sh && ./configure && make clean && make
44 1 zecke
}}}
45 1 zecke
46 1 zecke
If it compiles cleanly then you can install it as follows:
47 1 zecke
48 1 zecke
{{{
49 1 zecke
sudo make install
50 1 zecke
}}}
51 1 zecke
52 1 zecke
=== Using !WireShark to sniff P25 ===
53 1 zecke
54 1 zecke
Now you've got a modified !WireShark installed it should be a simple matter to start the receiver and use !WireShark to capture its output. To do so simply sniff on your computer's network interface and use the following capture filter: "udp port 23456". At present all P25 traffic is sent to the multicast address 224.0.0.1 so it should be visible on other computers on your subnet - this allows you to sniff in one place and monitor from another.
Add picture from clipboard (Maximum size: 48.8 MB)