Skip to main content
This is a pre-production deployment of Warehouse. Changes made here affect the production instance of PyPI (
Help us improve Python packaging - Donate today!

Generate DITG script files from a pcap file

Project Description

Generates [DITG’s] ( flow definition Files for each IP using a Packet Capture (.pcap) file as input



  • The help section of the program describes the usage details

    usage: [-h] [-t START_TIME] [-e END_TIME] [-s PACKET_SIZE_OPTIONS] [-p]
          pcap_file mapper_file list_file
    Generate DITG script files from a pcap file
    positional arguments:
      pcap_file             .pcap file to be used in generation
      mapper_file           Mapper file to be used in generation
      list_file             File containing all distinct IPs to be used in
    optional arguments:
      -h, --help            show this help message and exit
      -t START_TIME, --start-time START_TIME
                            Timestamp (in sec) from which the file should be read
      -e END_TIME, --end-time END_TIME
                            Timestamp (in sec) until which the file should be read
      -s PACKET_SIZE_OPTIONS, --packet-size-options PACKET_SIZE_OPTIONS
                            Packet size options to be used for each flow (for ex.
                            For Anonymized trace pcap files). If not provided,
                            *_ps files are created for each flow by using packet
                            sizes as per the pcap file
      -p, --print-all-ips   Print all distinct IPs appearing in the pcap file and
      -c, --clean           Remove any older generated files and exit the program
  • The format of list_file is as follows:,,
    • These are the IPs that are appearing in the PCAP file (as specified by pcap_file argument)

    • You can generate this list automatically by running the example program with -p option

      $ touch list_file
      $ python -p pcap_file mapper_file list_file > list_file
    • Note: While running the program with -p option, the files mapper_file and list_file are not actually used but still have to be provided as argument and should exist.

  • The format of mapper_file is as follows:

  • Usage in a different script or in interpreter mode is as:

    >> from pcap_to_ditg import pcap_to_ditg
    >> pcap_file_path = '***'
    >> mapper_file_path = '***'
    >> list_file_path = '***'
    >> options = {'end_time' : 60}
    >> p = pcap_to_ditg.pcap_to_ditg(
    The flow scripts and the IDT files have been generated and have been saved in separate sub-folders *_ditg_files.
Release History

Release History

This version
History Node


History Node


History Node


Download Files

Download Files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
pcap_to_ditg-0.1.1.tar.gz (5.0 kB) Copy SHA256 Checksum SHA256 Source Oct 20, 2016

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting