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

Age	Commit message (Collapse)	Author	Files	Lines
2013-03-01	Export libwireshark symbols using WS_DLL_PUBLIC define	Balint Reczey	1	-4/+0
	Also remove old WS_VAR_IMPORT define and related Makefile magic everywhere in the project. svn path=/trunk/; revision=47992
2013-02-28	Export libwiretap symbols using WS_DLL_PUBLIC define	Balint Reczey	1	-0/+5
	TODO: hide flex-generated functions svn path=/trunk/; revision=47948
2012-06-28	Update Free Software Foundation address.	Jakub Zawadzki	1	-1/+1
	(COPYING will be updated in next commit) svn path=/trunk/; revision=43536
2011-06-04	Fix wiretap headers to allow error-free ABI dumping.	Balint Reczey	1	-0/+1
	svn path=/trunk/; revision=37543
2011-04-12	"This file format can't be written to a pipe" and "this file format	Guy Harris	1	-2/+2
	can't be saved in compress form" are both equivalent to "this file file format requires seeking when writing it". Change the "can compress" Boolean in the file format table to "writing requires seeking", give all the entries the proper value, and do the checks for attempting to write a file format to a pipe or write it in compressed format to common code. This means we don't need to pass the "can't seek" flag to the dump open routines. svn path=/trunk/; revision=36575
2009-05-22	From Kovarththanan Rajaratnam via bug 2680:	Gerald Combs	1	-1/+2
	Currently Wireshark doesn't support saving WTAP_ENCAP_BLUETOOTH_H4_WITH_PHDR files as btsnoop files. svn path=/trunk/; revision=28442
2008-02-03	From Shane Kearns (bug 2237):	Stig Bjørlykke	1	-0/+30
	Added support for Symbian OS btsnoop. The bluetooth HCI layer in Symbian OS can be configured to log all packets to a file. The log format, "btsnoop" is based on the RFC1761 "snoop" format - but differences in the header make it incompatible. The btsnoop format supports logging of these formats: "H1" (raw HCI packets without framing) "H4" (HCI UART packets including packet type header) "H5" (HCI 3 wire UART packets including framing) "BCSP" (HCI bluecore serial protocol including framing) "H1" and "H4" are section numbers in the original v1 bluetooth specifications, but still used colloquially - wireshark's existing support for Linux bluez HCI logs uses the "H4" name. In practice, the "H1" format is used for H5,BCSP and USB HCI logs, as the HCI packet logs are mainly useful for debugging higher layers, bluetooth profiles and bluetooth applications. From me: Deleted some unused prototypes. Mark an unused parameter. svn path=/trunk/; revision=24263