osmocom
/
osmo-pcap
mirror of https://gerrit.osmocom.org/osmo-pcap
11
0
Fork 0
Code Issues Releases Wiki Activity
Tools for distributed pcap recording (osmo-pcap-server, osmo-pcap-client) https://osmocom.org/projects/osmo-pcap
89 Commits 6 Branches 21 Tags 845 KiB
C 84.6%
Shell 6.4%
M4 5%
Makefile 2.6%
Python 1%
Other 0.4%
Go to file
Holger Hans Peter Freyther c266796caa client: Initial support for TLS in the client 
Use GNUtls because it is GPL compatible and instead of mbedTLS seems
to have a working non-blocking I/O integration. GNUtls has various
issues that could not be resolved easily:

* Pick spdy as sub protocol
* gmt_time not randomized
* private key loaded to RAM (but not verified)

This is the beginning and not the end. Client support might need more
work with actual tls verification. Maybe more manual x509 cert
verification is needed and maybe client certs don't work at all. I try
to ignore renegotiation as I threw away the key.

Reload x509 creds and keys as they might have changed from one
connection to another.

Change-Id: I9128e14084da1fc2705f858393f98b8133996172
 		2016-09-08 16:16:55 +02:00
contrib tests: Enable the vty tests for the osmo-pcap as well 2016-09-08 15:21:29 +02:00
debian Make a new release with 64bit client fixes 2015-12-03 22:17:26 +01:00
doc server: Add zmq based event and data interface to the server 2016-08-05 16:10:05 +02:00
include client: Initial support for TLS in the client 2016-09-08 16:16:55 +02:00
src client: Initial support for TLS in the client 2016-09-08 16:16:55 +02:00
tests tests: Enable the vty tests for the osmo-pcap as well 2016-09-08 15:21:29 +02:00
.gitignore tests: Enable the vty tests for the osmo-pcap as well 2016-09-08 15:21:29 +02:00
.travis.yml client: Initial support for TLS in the client 2016-09-08 16:16:55 +02:00
AUTHORS osmo-pcap: Start with the autoconf/automake skeleton for this project 2011-05-31 10:19:47 +02:00
COPYING osmo-pcap: Start with the autoconf/automake skeleton for this project 2011-05-31 10:19:47 +02:00
Makefile.am tests: Enable the vty tests for the osmo-pcap as well 2016-09-08 15:21:29 +02:00
README.md Mention the packages available 2016-01-18 14:25:19 +01:00
TLS_TODO tls: Add initial ideas about TLS in the client/server 2016-09-08 15:48:02 +02:00
TODO misc: Update the todo with an obvious thing to do 2016-08-12 11:01:59 +02:00
configure.ac client: Initial support for TLS in the client 2016-09-08 16:16:55 +02:00
git-version-gen misc: Fix the version determination of git-version-gen 2012-11-06 08:48:33 +01:00
osmoappdesc.py tests: Enable the vty tests for the osmo-pcap as well 2016-09-08 15:21:29 +02:00

README.md

osmo-pcap distributed network capture

osmo-pcap has been created to collect network traces at different nodes but store them centrally at a dedicated note for further analysis. This might be needed for auditing, resolving conflicts, post processing or debugging a distributed system.

The system consists out of the osmo-pcap-client to cpature traffic at a host and osmo-pcap-server to receive the traffic, store and rotate the traffic at a centralized server. There is a shell script to compress and expire old traces.

osmo-pcap-client

The osmo-pcap-client is using libpcap and has a built-in detector for the GPRS-NS/BSSGP protocol to exclude user traffic. The client is known to work on 32/64 bit systems. It can be configured through the VTY and the minimal config includes the interface to monitor, the pcap filter to use and the server to send it to.

osmo-pcap-server

The osmo-pcap-server will listen for new TCP connections and then will receive the data from the client if it is coming from a known/good source IPv4/port. The server is configured to write one file per client and to change/rotate the file when the link encapsulation is changing. It can be configured to rotate the file a given time interval and/or if the filesize is over a threshold.

The osmo-pcap-server comes with a shell script to rotate and compress old traces. Currently the configuration parameters (age or amount based) need to be tuned in the script itself.

Installation and Configuration

There are Debian, Ubuntu, SLES, OpenSUSE and CentOS packages available via the excellent openSUSE Build Service.

Please see the contrib/osmo-pcap-server.cfg and contrib/osmo-pcap-client.cfg file in the repository

Wishlist/TODO

  • Add non-blocking TLS (probably GNUtls) support between client and server.
  • Improve the clean-up script, maybe re-write in python with exteral configuration.
  • Add hooks to the server to have an application receive all packages

Author and License

osmo-pcap has been created by Holger Hans Peter Freyther (holger@freyther.de) and is licensed as AGPLv3+. The author appreciates failure or success reports of using the software.