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

Age	Commit message (Collapse)	Author	Files	Lines
2008-05-22	Move the file utility functions from wiretap to libwsutil so that	Jeff Morriss	1	-6/+5
	libwireshark (and the plugins using those functions) do not depend on wiretap on Windows. While doing that, rename the eth_* functions to ws_*. svn path=/trunk/; revision=25354
2008-04-13	Add IPv6 multicast support.	Jaap Keuter	1	-2/+5
	svn path=/trunk/; revision=24970
2008-04-13	sort #includes by directories	Ulf Lamping	1	-14/+18
	svn path=/trunk/; revision=24969
2008-04-07	Fix for bug 2414:	Jaap Keuter	1	-2/+3
	- Do not compare to the possibly resolved address, but the address itself - Do not leak memory when comparing addresses svn path=/trunk/; revision=24837
2008-02-18	Add $Id$	Bill Meier	1	-0/+2
	svn path=/trunk/; revision=24382
2007-03-21	fix all warnings in gtk dir & set the "treat all warnings as errors" MSVC flag	Ulf Lamping	1	-8/+8
	svn path=/trunk/; revision=21080
2006-05-21	name change	Ronnie Sahlberg	1	-2/+2
	svn path=/trunk/; revision=18197
2006-04-30	Get rid of extra semicolon - GCC warns that ISO C doesn't allow it.	Guy Harris	1	-1/+1
	svn path=/trunk/; revision=18045
2006-04-24	From Miha Jemec:	Anders Broman	1	-0/+450
	With the new feature we can: 1. Measure how big the bursts are for a video streams (it uses sliding window algorithm) 2. Measure how big the output buffer should be that no packet drop will occur (it uses Leaky bucket algorithm) 3. Detect if we have loses inside the MPEG2 video stream (if there are already MPEG2 packets missing) - this part of code is not added yet, see Limitations The addition is called Multicast streams and works as follows: - it uses the TAP system - the main "stream" logic is taken from rtp_strems.* files - the TAP system checks for UDP packets where the destination MAC address starts with "01:00:5E" (ethernet multicast address) - it creates an entry for every new multicast stream - based on sliding window and leaky bucket algorithm it calculates for every stream average BW, max BW, burst size, max buffer needed, some alarms if the limits are exceeded,... - the same calculation is done for all streams together - inside the window dialog you can specify the burst interval, the alarm limits and output speeds To do & limitations: - Currently the analysis can be done only for multicast streams, it means that VoD (Video on demand) or PayTV streams, which are normally unicast can not be analysed. - since the MPEG2 is patended I don't know if decoding of MPEG2 packets is allowed? Can we look inside this packets and calculate packets drops based on some counter information inside the payload? Can someone please answer this question? If we can do this, I will post this part of code too. - some more flexibility will be added svn path=/trunk/; revision=17980