Michael Mann 3120536012 Have TPKT support a TCP port range preference instead of having "subdissectors?" register their own. ... There are a number of dissectors who are subdissectors of TPKT (and OSITP) that are not called by TCP dissector directly, yet can possibly register a TCP port "on the behalf" of TPKT. Just allow TPKT to support a range of ports to possibly include these protocols. Remove the preferences from these dissectors, but add backwards compatibility for the preferences by hooking into set_prefs and have the preferences just hook into Decode As functionality directly. Change-Id: Ic1b4959d39607f2b6b20fa6508da8d87d04cf098 Reviewed-on: https://code.wireshark.org/review/17476 Petri-Dish: Michael Mann <mmann78@netscape.net> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Michael Mann <mmann78@netscape.net>		2016-09-16 14:58:24 +00:00
..
CMakeLists.txt	…
MSAbstractService.asn	…
MSAccessProtocol.asn	…
MSGeneralAttributeTypes.asn	…
MSUpperBounds.asn	…
Makefile.am	Remove Makefile.common files	2016-06-30 11:04:17 +00:00
p7.cnf	…
packet-p7-template.c	Have TPKT support a TCP port range preference instead of having "subdissectors?" register their own.	2016-09-16 14:58:24 +00:00
packet-p7-template.h	…