a list of fields, prints the field values found in each packet.
Packet data can be specified as a libpcap DLT, e.g. "EN10MB" or an upper-layer protocol, e.g. "http".
svn path=/trunk/; revision=24339
(The fix is to cd back to "../portableapps/win32", rather than
"../u3/win32", at the end of the nsis-bits target in makefile.nmake.)
Me:
Get rid of some whitespace at the end of lines.
svn path=/trunk/; revision=24031
The U3 and portableapps packaging will use this generic manifest to package the
correct set of components. Thus all three packages will be kept in sync.
svn path=/trunk/; revision=24011
a) Check that UPX is configured correctly and offer solutions;
b) Ignore any errors generated from UPX (e.g. from previously compressed files); and
c) Clean up the tools directory when cleaning the U3 distribtion
svn path=/trunk/; revision=23622
For the U3 package, this results in a 40% smaller package.
For the PortableApps version, the package size is not much different, but the install time is quicker.
svn path=/trunk/; revision=23484
This allows Wireshark to be run from any USB stick, unlike the U3 packaging which must be installed on a specific U3 device.
The packaging basically builds upon the U3 distribution so new libraries/config only need to be added to the U3 makefile to update both distributions.
It still takes a "dumb" approach to WinPcap - installing it if it is not already installed and removing it (if WSP installed it) when Wireshark quits. (This is worse than the U3 packaging which only uninstalls WinPcap when the device is removed.) Really must talk to the WinPcap guys to see how we can make this less intrusive.
I am talking to John Haller (the Portable Apps guy) about fine tuning the distribution.
svn path=/trunk/; revision=23340
1. wireshark.bat: Quote %U3_HOST_EXEC_PATH%\wireshark.exe so pathname
with spaces will work;
2. makefile.nmake: Use $(MAKE) /$(MAKEFLAGS) so things like
invoking nmake at the top level with /E to have environment
variables override config.namke definitions will work.
svn path=/trunk/; revision=23297
a) include smi.dll if SMI_DIR is set
b) add a batch script to run the U3 wireshark configuration by simulating the U3 environment
c) include a test step in the build process to verify that the U3 package contains all the required files (tries to run "wireshark -D")
d) include the wireshark.bat in the U3 zip file.
This final step means that the U3 package can be unzipped on any drive and run using the wireshark.bat script. (Note this currently creates an unwanted cmd window.)
svn path=/trunk/; revision=23295
Author :
Richard Kuemmel <r.kuemmel[AT]beckhoff.de>
Updates and bugfixes:
Peter Johansson <peterjohansson73[AT]gmail.com>
svn path=/trunk/; revision=23174
Q: are the plugins unconditionally installed by the win32 installer? i.e. should the installation of these files be conditional?
svn path=/trunk/; revision=23157
references to h223 in README.plugins with agentx since it's small and
no one seems to be in a hurry to move it to epan/dissectors.
svn path=/trunk/; revision=22641
add it to the distributed files, to the Win32 NSIS and U3 packages. UNIX packages will still miss this (optional) file.
svn path=/trunk/; revision=22487
94630be0-e031-11db-974d-0002a5d5c51b
It is based upon the example code from RFC4122 and links against gcrypt.
Using this tool allows the U3 packaging UUID to be automatically changed for new versions as well as giving each buildbot version a different UUID.
svn path=/trunk/; revision=21694
Also tweak the space requirements and restore the VERSION_EXTRA information to the description, both within the manifest.u3i.
svn path=/trunk/; revision=20964
a) remove schema reference
b) assign new GUID for 0.99.6
Update makefile.nmake to:
a) include user-guide.chm - user-guide.chm is copied from the nsis packaging directory
b) include the example_snmp_users_file
c) other tidy-ups
svn path=/trunk/; revision=20555
The U3 Deployment Guide recommends a sub-directory of U3_DEVICE_DOCUMENT_PATH, so the u3util creates a "My Captures" sub-directory to use as the personal data file directory.
svn path=/trunk/; revision=20441
- add redistributables (msvcr*.dll) to the NSIS installer (depending on MSVC_VARIANT)
- split MSVC2006 and MSVC2006EE (Express Edition) settings in config.nmake, as redistributable settings for NSIS are different
- remove Platform SDK setting from config.nmake, it's not needed
svn path=/trunk/; revision=20411
This copying should be controlled by the MSVC_VARIANT setting in config.nmake instead (just like all the other alike settings).
svn path=/trunk/; revision=20286
"Apply the ugly attached patch to the installer"
... it's not that ugly at all - and installs (deletes) the manifest files if available
svn path=/trunk/; revision=20285
a) Packaging changes - including the latest GTK/GLIB/PANGO libaries
b) File associations - made when Wireshark is first run and removed when device is removed.
c) Install WinPcap - by running the installer if WinPcap is not installed. Uninstalled (if the U3 device installed it) when the device is removed. (This is an interim approach until the appropriate WinPcap U3 installation can be determined).
svn path=/trunk/; revision=19985
Here is a DTD for the MSCML protocol, draft-07. This implementation is not entirely up-to-date (draft-09 is out), but this is a good base to start from.
I updated the WIKI with info, snapshot and sample capture: http://wiki.wireshark.org/MSCML
svn path=/trunk/; revision=19901
Note from a mail on gtk dev list:
-rwxr-xr-x 1 tml Administ 224510 Oct 3 18:35 libpango-1.0-0.dll
-rwxr-xr-x 1 tml Administ 37952 Oct 3 18:35 libpangocairo-1.0-0.dll
-rwxr-xr-x 1 tml Administ 58749 Oct 3 18:35 libpangowin32-1.0-0.dll
(That's the relevant DLLs from the "bin" folder in Pango 1.14.5, where
the module(s) are built-in into the DLLs, so no
lib/pango/1.5.0/modules folder is needed.)
svn path=/trunk/; revision=19880