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

Age	Commit message (Collapse)	Author	Files	Lines
2006-11-05	change all file offsets from long to gint64 so we can - theoretically - ↵	Ulf Lamping	1	-4/+4
	handle files > 2GB correct. Please distclean Win32 builds! svn path=/trunk/; revision=19814
2006-10-19	Rename get_epan_and_portaudio_version_info() to get_gui_compiled_info()	Gerald Combs	1	-1/+1
	and add version info for AirPcap. Add a corresponding get_gui_runtime_info(). Fix up whitespace. svn path=/trunk/; revision=19620
2006-10-19	Clean up the word wrap stuff a bit. (Arguably, that should be done in	Guy Harris	1	-1/+1
	the code that displays it - we might, for example, be able to have the About dialog word-wrap to the appropriate size, and word-wrap text printed to the standard output to the terminal width if it's going to a terminal and to 80 or whatever columns otherwise.) Don't report anything in dumpcap about libraries not used by dumpcap. (It was printing a blank, which looked a bit weird.) Fix the handling of _MSC_VER as per Gerald's fix for _MSC_FULL_VER. svn path=/trunk/; revision=19618
2006-10-19	Fix up the changes to put the Portaudio information at the end of the	Guy Harris	1	-1/+1
	version string, so the information comes out right for applications that don't use Portaudio. Get rid of an extra "with" in the version string for dumpcap. Get rid of an extra blank after the libpcap version string, and get rid of an extra newline before it. Attempt to add more compiler version information and to prettify the MSVC++ version information (both untested). svn path=/trunk/; revision=19613
2006-10-08	from Richard van der Hoff:	Ulf Lamping	1	-5/+2
	> [tshark from a fifo] > Ulf - I notice you made the relevant change here (r16787) - is there any reason why tshark shouldn't use capture_loop_dispatch to do its processing, rather than attempting to use cap_pipe_dispatch or pcap_dispatch directly? well, there didn't seem to be, so I've made a patch which does exactly this, and which fixes the problem. svn path=/trunk/; revision=19456
2006-09-22	Add support for reading from stdin under Windows. Based on a patch sent	Gerald Combs	1	-39/+28
	in last year by Gianluca Varenni. Add partial support for reading from named pipes (currently disabled). Move utf_8to16() and utf_16to8() to a separate module (unicode-utils.[ch]) so that we don't have to cut and paste code in dumpcap.c. Fix up whitespace. svn path=/trunk/; revision=19291
2006-08-26	Go back to setting the capture filter to an empty string when we start;	Guy Harris	1	-10/+3
	that obviates the need to check for a null capture filter string, and fixes bug 1055. Keep track of whether it was set from the command line, though, so we can catch attempts to set the filter more than once, and attempts to set it when we're not capturing. Clean up white space. svn path=/trunk/; revision=19047
2006-08-21	Initialize the cfilter field of a capture_opts structure to a null	Guy Harris	1	-4/+11
	pointer, so we can determine whether a capture filter has been set or not. Use that to check in TShark whether the user specified a filter with "-f" or not, rather than using the no-longer-set "capture_filter_specified" variable. Also, check for multiple "-f" options. If no capture filter is specified, use a null string, to work around broken versions of Linux libpcap. svn path=/trunk/; revision=18989
2006-08-18	guids are not olnly used in dcerpc interfaces and they often occur in many ↵	Ronnie Sahlberg	1	-0/+3
	other protocols such as ldap and smb/smb2 move the initialization of the guid mapping table from the dcerpc dissector to a more neutral place svn path=/trunk/; revision=18947
2006-08-01	Reported by Stephen Fisher <stephentfisher@yahoo.com>:	Jörg Mayer	1	-1/+1
	I believe this is a typo in the command line help for the -i option: Usage: wireshark [options] ... [ <infile> ] Capture interface: -i <interface> name or idx of interface (def: first none loopback) Shouldn't that read "first non-loopback" ? svn path=/trunk/; revision=18813
2006-06-30	Call init_progfile_dir() - on Windows, at least, it's necessary in order	Guy Harris	1	-0/+10
	to get the directory where the data files are stored, and on UN*X we might have an option in the future to have it search there for data files, to make it easier to run WireShark/TShark from the build directory and have it find plugins, etc.. svn path=/trunk/; revision=18622
2006-06-02	image/wireshark.rc.in	Jörg Mayer	1	-8/+8
	svn path=/trunk/; revision=18310
2006-05-31	Tethereal/tethereal -> TShark/tshark.	Gerald Combs	1	-0/+3067
	svn path=/trunk/; revision=18268