wireshark - wireshark.org protocol dissector with Osmocom additions (obsolete)

Age	Commit message (Collapse)	Author	Files	Lines
2018-02-12	dissectors: use SPDX identifiers.	Dario Lombardo	1	-13/+1
	Change-Id: I92c94448e6641716d03158a5f332c8b53709423a Reviewed-on: https://code.wireshark.org/review/25756 Petri-Dish: Dario Lombardo <lomato@gmail.com> Reviewed-by: Anders Broman <a.broman58@gmail.com>
2016-10-13	Convert most UDP dissectors to use "auto" preferences.	Michael Mann	1	-1/+1
	Similar to the "tcp.port" changes in I99604f95d426ad345f4b494598d94178b886eb67, convert dissectors that use "udp.port". More cleanup done on dissectors that use both TCP and UDP dissector tables, so that less preference callbacks exist. Change-Id: If07be9b9e850c244336a7069599cd554ce312dd3 Reviewed-on: https://code.wireshark.org/review/18120 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-02-25	Clean up modelines and indentation.	Guy Harris	1	-4/+4
	HT tab stops are set every 8 spaces on UNX; UNX tools that treat an HT character as tabbing to 4-space tab stops, or that even are configurable but default to 4-space tab stops (I'm looking at you, Xcode!) are broken. tab-width: 4, tabstop=4, and tabSize=4 are errors if you ever expect anybody to look at your file with a UNX tool, and every text file will probably be looked at by a UNX tool at some point, so Don't Do That. Adjust indentation to reflect the mode lines. Change-Id: Icf0831717de10fc615971fa1cf75af2f1ea2d03d Reviewed-on: https://code.wireshark.org/review/14150 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2016-02-03	Add Userlog dissector	Jun Wang	1	-0/+432
	Userlog is user flow logs of H3C device. Flow logging records users' access to the extranet. The device classifies and calculates flows through the 5-tuple information, which includes source IP address, destination IP address, source port, destination port, and protocol number, and generates user flow logs. Flow logging records the 5-tuple information of the packets and number of the bytes received and sent. With flow logs, administrators can track and record accesses to the network, facilitating the availability and security of the network. examplecapture: https://wiki.wireshark.org/SampleCaptures#UserLog Bug: 11878 Change-Id: If3b5ca75bdd6cd8dc12af4a35401c5a6aa193a73 Reviewed-on: https://code.wireshark.org/review/8148 Reviewed-by: Michael Mann <mmann78@netscape.net> Petri-Dish: Michael Mann <mmann78@netscape.net> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Anders Broman <a.broman58@gmail.com>