CoMo-UPC: TMA evaluation service @ UPC
CoMo-UPC: TMA evaluation service @ UPC
CoMo-UPC is a UPC-CCABA initiative within the COST-TMA action (IC0703) to provide an evaluation platform to the TMA research community. CoMo-UPC is a passive network monitoring platform deployed in the UPC network that can be used by the COST-TMA participants to run their traffic analysis methods (e.g., anomaly detection algorithms) on both online traffic and packet traces collected at UPC. TMA participants only need to send us their code as a CoMo module (following the procedure described below) and we will run it on our CoMo-UPC box.
The main advantage of this evaluation model is that it significantly lowers the privacy concerns of data providers (UPC, in this case) compared to the traditional approach of sharing anonymized packet traces, since:
The CoMo-UPC system is continuously monitoring the Gigabit Ethernet access link of the UPC (1 Gb/s full-duplex), which connects about 25 faculties and 40 departments (geographically distributed in 10 campuses) to the Internet through the Catalan Research and Education network (Scientific Ring). The average traffic in this link during peak hours is about 1 Gb/s (with ~60K flows/s).
Online statistics of the UPC traffic can be obtained at:
The CoMo-UPC box runs CoMo 2.0. To develop a CoMo module you therefore need to download and install CoMo 2.0 in your system. Since CoMo 2.0 is still in development, it is, as of today, only available for download via its official subversion code repository hosted at sourceforge. The source code can be obtained and compiled as follows:
$ svn co https://como.svn.sourceforge.net/svnroot/como/src/branches/2.0 como2.0 $ cd como2.0 # enter source code directory $ make # compile $ sudo make install # install $ make modules # build the example modules $ sudo make modules-install # install them
CoMo 2.0 should compile on any mainstream linux distribution. At the moment, 64 bit architectures are not supported. You should be aware, though, of software dependencies. The CoMo build process requires CMake, Bison and Flex. Also, it is highly recommended to install the libpcap packet collection library. This software will usually be easily installed via your distribution's package manager. For example, on debian boxes, these packages can be obtained as follows:
# apt-get install cmake bison flex libpcap-dev
Since CoMo 2.0 is, as noted, still under development, you can potentially encounter difficulties compiling and installing it. If this is the case, please send bug reports as detailed as possible to CoMo's development mailing lists that you can find on its sourceforge project page.
To run your CoMo module on the CoMo-UPC box you have to follow these instructions:
| Name | Date | Start (duration) | Content | Dir. | Mean traffic | Size |
|---|---|---|---|---|---|---|
| UPC-I | 11-Dec-2008 | 10:00 (15 min) | payload | both | 471 Mb/s | 53 GB |
| UPC-II | 11-Dec-2008 | 12:00 (15 min) | payload | both | 560 Mb/s | 63 GB |
| UPC-III | 12-Dec-2008 | 16:00 (15 min) | payload | both | 488 Mb/s | 55 GB |
| UPC-IV | 12-Dec-2008 | 18:30 (15 min) | payload | both | 426 Mb/s | 48 GB |
| UPC-V | 21-Dec-2008 | 16:00 (1 h) | payload | both | 275 Mb/s | 124 GB |
| UPC-VI | 22-Dec-2008 | 12:30 (1 h) | payload | both | 573 Mb/s | 258 GB |
| UPC-VII | 10-Mar-2009 | 03:00 (1 h) | payload | both | 175 Mb/s | 79 GB |
| CESCA-II | 02-Nov-2005 | 16:30 (30 min) | headers | in | 360 Mb/s | 8 GB |
| CESCA-III | 11-Apr-2006 | 08:00 (30 min) | payload | in | 133 Mb/s | 29 GB |
| CESCA-IV | 24-Oct-2006 | 09:00 (8 h) | headers | in | 750 Mb/s | 156 GB |
| CESCA-V | 25-Oct-2006 | 09:00 (8 h) | headers | in | 719 Mb/s | 153 GB |
| CESCA-VI | 05-Dec-2006 | 09:00 (8 h) | headers | in | 403 Mb/s | 139 GB |
At this moment, there is very few documentation about CoMo 2.0. The only documentation available on how to write CoMo 2.0 modules can be downloaded from the Onelab project:
Additional information:
