SoupBinTCP (soupbintcp)

SoupBinTCP provides framing, authentication, heartbeats, message sequencing and recovery for a higher-level application protocol. In practice, it's used by NASDAQ's ITCH and OUCH protocols.

History

Originally, SOUP was an ASCII-based protocol, with messages terminated by an EOL character. SoupBinTCP replaces SOUP, and supports framing messages that contain arbitrary byte values.

SoupBinTCP version 3.0 was released to support OUCH-4.0 and ITCH-4.0, the first versions of those protocols that required arbitrary byte contents.

Protocol dependencies

Example traffic

XXX - Add example decoded traffic for this protocol here (as plain text or Wireshark screenshot).

Wireshark

The SoupBinTCP dissector was added to version 1.10.0

Example capture file

TDB

Display Filter

A complete list of SoupBinTCP display filter fields can be found in the display filter reference

Capture Filter

You cannot directly filter SoupBinTCP protocols while capturing. However, if you know the TCP port used (see above), you can filter on that one.

Discussion

SoupBinTCP (last edited 2015-10-23 21:29:45 by JaapKeuter)