Wireshark mailing list archives
Re: Heuristic check of T.125 dissector
From: Thomas Wiens <th.wiens () gmx de>
Date: Tue, 25 Feb 2014 17:51:30 +0100
Without knowing the protocol, I'd say there's almost always room for improvement. Open a bug with a sample capture and see if someone can figure out how to strengthen the check.
Ok, thanks. I will open a bug request then.
ps. you mentioned your dissector is hosted on sourceforge; would you consider submitting it to Wireshark?
The dissector is of a proprietary protocol which is completely reverse engineered. There is no official documentation available. The protocol is used in programmable logic controlles by Siemens, I think the most common vendor in Europe for those controllers. I don't know if there are other reverse engineered protocols in wireshark, but for myself I would like when the delivered plugins with wireshark refer to official documents or rfcs, and not guessed as my dissector. Is there a official wireshark point of view? The website is: http://sourceforge.net/projects/s7commwireshark/ There are some sample captures available. -- Regards Thomas Wiens ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Heuristic check of T.125 dissector Thomas Wiens (Feb 22)
- Re: Heuristic check of T.125 dissector Jeff Morriss (Feb 24)
- Re: Heuristic check of T.125 dissector Thomas Wiens (Feb 25)
- Re: Heuristic check of T.125 dissector ronnie sahlberg (Feb 25)
- Re: Heuristic check of T.125 dissector Thomas Wiens (Feb 25)
- Re: Heuristic check of T.125 dissector Jeff Morriss (Feb 24)