Thanks for your hint, but I couldn't find a good heuristic to distinguish SPOP from TCP. I think, that the current implementation is usable enough for development purposes. Feel free to enhance it. :-)
There is a Wireshark feature called "Decode as...", where you can choose the SPOP dissector to decode frames for other ports.
Regards,
Danny
Gesendet: Dienstag, 28. November 2017 um 10:12 Uhr
Von: "Frederic Lecaille" <flecai...@haproxy.com>
An: my.card....@web.de
Betreff: Re: [RFC] Wireshark dissector for SPOP
Von: "Frederic Lecaille" <flecai...@haproxy.com>
An: my.card....@web.de
Betreff: Re: [RFC] Wireshark dissector for SPOP
On 11/20/2017 10:16 PM, my.card....@web.de wrote:
> Hi Fred,
> thanks for looking into this, I've fixed this issue (and introduced some
> new :-))
> The attached dissector code parses all SPOP frames sent from
> contrib/spoa_sample and haproxy and handles some fragmentation scenarios.
> Kind regards,
> Danny
Danny, please note that your wireshark dissector will work only for
agents listening on 12345 port.
You should have a look at doc/README.heuristic file to fix this easy to
fix issue ;).
Regards,
Fred.
> Hi Fred,
> thanks for looking into this, I've fixed this issue (and introduced some
> new :-))
> The attached dissector code parses all SPOP frames sent from
> contrib/spoa_sample and haproxy and handles some fragmentation scenarios.
> Kind regards,
> Danny
Danny, please note that your wireshark dissector will work only for
agents listening on 12345 port.
You should have a look at doc/README.heuristic file to fix this easy to
fix issue ;).
Regards,
Fred.
