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

Age	Commit message (Collapse)	Author	Files	Lines
2016-06-16	Finish getting making the Diameter XML valid XML.	Jeff Morriss	1	-4/+4
	... Except for the fact that many AVP names start with "3GPP". Make the AVP names XML IDs again. Fix all the grouped AVPs that reference AVPs (by name) or vice-versa. This includes: * Fixing a bunch of typos (including type mismatches). * Commenting out a number of references to vendor AVPs for which we don't have the specs. * Adding a few missing AVPs. Change-Id: Ic2ddb50cc947877de9086be51f7813e8f9be02b4 Reviewed-on: https://code.wireshark.org/review/15973 Reviewed-by: Anders Broman <a.broman58@gmail.com>
2016-06-16	Make the rest of the Diameter AVP names unique.	Jeff Morriss	1	-25/+25
	In most cases this means prepending the application- or vendor-name to force uniqueness. A few vendors have duplicates within their namespace--append the AVP code to these. Also fix a few other invalid names (with spaces or parentheses in the names). Change-Id: I5bb78d31526122dd5782055638af410cc497e49d Reviewed-on: https://code.wireshark.org/review/15960 Reviewed-by: Anders Broman <a.broman58@gmail.com>
2015-04-22	Misc. Diameter XML cleanups.	Jeff Morriss	1	-1468/+1230
	Consistently used (derived) type Enumerated (rather than Unsigned32 or Integer32) when the AVP is of type Enumerated. Use a uri of "none" when we don't have access to the specification. Update the URI of an Application or two. Clean up white space and formatting. Change-Id: Iad677db186469b7d8c4a23b7a7fca6c357dbc012 Reviewed-on: https://code.wireshark.org/review/8164 Reviewed-by: Jeff Morriss <jeff.morriss.ws@gmail.com>
2015-04-21	Allow the definition of AVPs within vendor IDs.	Jeff Morriss	1	-424/+421
	This allows for a more natural organization of AVP definitions: they can now be grouped by application (including the base application) or vendor ID. This means we can stop using the "workaround" (for those vendors who define AVPs but don't have their own application ID) of finding some random application ID to put in a vendor-specific xml file just to satisfy the parser. Rework a couple of Vendor-specific xml files as an example. Note: this does mean that vendor IDs can no longer be defined inside of the base or other application. If that's a problem the parser could be made (through some duplication of code) to understand the old format too. Change-Id: I5119f0dc7f8e3bbf59e2207046a8bb0f42ab0ca1 Reviewed-on: https://code.wireshark.org/review/8141 Petri-Dish: Jeff Morriss <jeff.morriss.ws@gmail.com> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Jeff Morriss <jeff.morriss.ws@gmail.com>
2014-03-31	Continue to remove $Id$ from top of file	Alexis La Goutte	1	-1/+0
	(Using sed : sed -i '/^<!-- \$Id\$ -->/,+0 d') (XML Comments) Change-Id: Ifd03f70ae84dfbbbe04d91f10fd30857fd197014 Reviewed-on: https://code.wireshark.org/review/882 Reviewed-by: Anders Broman <a.broman58@gmail.com>
2011-12-12	From Asmita:	Anders Broman	1	-1/+43
	Update to csg2 r7 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6661 svn path=/trunk/; revision=40160
2011-10-26	White space changes.	Anders Broman	1	-9/+9
	svn path=/trunk/; revision=39597
2011-09-01	From John Bradshaw:	Anders Broman	1	-2/+2
	Spelling fixes https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6296 svn path=/trunk/; revision=38834
2011-07-26	From Asmita:	Anders Broman	1	-4/+66
	Diameter AVP patch for Cisco.xml https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6169 svn path=/trunk/; revision=38209
2011-06-09	From Madhusudhan M:	Anders Broman	1	-0/+1378
	Cisco and Vodafone Diameter AVP:s I have axtracted the relevant vendor AVP:s and separated them out in Vendor specific xml files. Part of https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5972 svn path=/trunk/; revision=37627