https://wiki.packet-o-matic.org/ 2026-04-25T14:48:04+00:00 https://wiki.packet-o-matic.org/ https://wiki.packet-o-matic.org/lib/tpl/dokuwiki/images/favicon.ico text/html 2020-05-26T21:59:16+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.packet-o-matic.org/pom/command_reference?rev=1590530356&do=diff Command reference General commands config write [filename] Write the current configuration. You can optionally specify a different file name. debug cli set <off,0-5> Set the debug level of the management console (CLI). debug cli show Display the current debug level. text/html 2020-05-26T21:59:16+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.packet-o-matic.org/pom/config_examples?rev=1590530356&do=diff Packet-o-matic can be quite complicated due to the infinite number of possibilities it provides. Here are a few configuration example that you may find useful to understand how certain aspects can be configured. Scan for a DOCSIS stream using a DVB card text/html 2020-05-26T21:59:16+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.packet-o-matic.org/pom/datastore_config?rev=1590530356&do=diff Datastore configuration To use a datastore, 3 steps are required. First you need to add the datastore to the configuration : pom> datastore add sqlite datastore1 Datastore "datastore1" added (type sqlite) Other datastore types such as postgres or mysql are available if the configure script found the required files. text/html 2020-05-26T21:59:16+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.packet-o-matic.org/pom/getting_started?rev=1590530356&do=diff Getting started First, start packet-o-matic. This will start the program without any configuration. packet-o-matic At this point, packet-o-matic listens on port 4655. Simply telnet it and start configuring it. telnet localhost 4655 You can also use the web interface. If you compiled it with xmlrpc-c support, start with the -X switch to enable the web interface. text/html 2020-11-12T10:31:55+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.packet-o-matic.org/pom/installation?rev=1605177115&do=diff Installation Dependencies * libxml2 : Required for parsing and writing the configuration. * libpcap : Required for input_pcap, target_pcap, target_tcpkill and target_inject. * xmlrpc-c : Required for XML-RPC interface and the web interface. * text/html 2020-05-26T21:59:16+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.packet-o-matic.org/pom/rules_syntax?rev=1590530356&do=diff Rules syntax Syntax You can either match a protocol or a specific parameter of this protol. To match a protocol: <match> Example : ipv4 To match a specific field : <match>.<field> <op> <value> Example : ipv4.src == 10.0.0.0/8 See the start page for a list of match modules and their documentation. text/html 2020-05-26T21:59:16+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.packet-o-matic.org/pom/start?rev=1590530356&do=diff Packet-o-matic (old version) The below is only applicable to the old version called “packet-o-matic” and not pom-ng ! If you are looking for instructions about pom-ng, see here. General * Installation : All you need to know to install packet-o-matic * Getting started : Quick steps to have it up and running text/html 2020-05-26T21:59:16+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.packet-o-matic.org/pom/tips_and_tricks?rev=1590530356&do=diff Tips and tricks File path expansion Some target support file path expansion. For example target_http can have the following prefix configured : prefix = /mnt/data/${ipv4.src}/${tcp.sport}/http/dump- If the connection is established from 10.0.0.1 and the source port is 3000, the new directory /mnt/data/10.0.0.1/3000/http/ will be created and files will be put there. text/html 2020-05-26T21:59:16+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.packet-o-matic.org/pom/xmlrpc_interface?rev=1590530356&do=diff XML-RPC interface The XML-RPC interface allow easy configuration of packet-o-matic by remote applications. The arguments can be either strings (s/) or integers (i/). By default, packet-o-matic listens on TCP port 8080 and the path for the XML-RPC queries is /RPC2. If you did specify a password for the XML-RPC interface, the user will be 'admin'.