Any plans to support Currenex ITCH protocols
Hi, Do you have any plans to add the Currenex ITCH protocols?
Please find links to the latest specs below:-
- https://www.currenex.com/content/6-support/documentation/currenex/ITCH-Spec.pdf
- https://www.currenex.com/content/6-support/documentation/currenexnow/Currenex_NOW_Itch_Specification.pdf
Thanks Chris
We have a working binary data model but this is a new protocol structure. Can you please provide a pcap for testing/verification?
Can I share this securely or just provide the payload data?
Thanks - I can see Currenex has been added and going through testing. I currently get the following decoder errors:-
User Datagram Protocol, Src Port: 40100, Dst Port: 42705
<Wireshark Lua fake item>
Currenex Forex Esp Citch 9.0 (43 Bytes)
Lua Error: ...lua\Currenex\Currenex_Forex_Esp_Citch_v9_0_Dissector.lua:1570: attempt to call a nil value (field 'itch_soh')
[Expert Info (Error/Undecoded): Lua Error: ...lua\Currenex\Currenex_Forex_Esp_Citch_v9_0_Dissector.lua:1570: attempt to call a nil value (field 'itch_soh')]
[Lua Error: ...lua\Currenex\Currenex_Forex_Esp_Citch_v9_0_Dissector.lua:1570: attempt to call a nil value (field 'itch_soh')]
<Message: Lua Error: ...lua\Currenex\Currenex_Forex_Esp_Citch_v9_0_Dissector.lua:1570: attempt to call a nil value (field 'itch_soh')>
[Severity level: Error]
[Group: Undecoded]
Lua Traceback
[Community ID: 1:Fz6tFGnvVKMAvgIZ8ISE08G14fY=]
Currenex ITCH is also available over TCP, once the UDP decoder is working is it possible to develop a TCP one also?
It would be very hard to debug this over GitHub. While we do our best to generate directly from the pdf specifications, the reality is that we only understand the actual parsing rules of the protocols through trial and error. Please post a pcap or send us one at contact at openmarketsinitiative dot com. We will fix any issues and regenerate.
We can generate TCP also (please include a test pcap). Additionally, shortly we will post dissectors for ESP and Ouch; test pcaps for these protocols will be much appreciated.
Thanks.
Please try again. We found an issue with the ESP dissector when working on OUCH.