Wireshark-users: [Wireshark-users] Wireshark 1.5.1 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Mon, 11 Apr 2011 14:00:48 -0700
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.5.1. This is an experimental release intended to test features that will go into Wireshark 1.6. What is Wireshark? Wireshark is the world's most popular network protocol analyzer. It is used for troubleshooting, analysis, development and education. What's New Bug Fixes The following bugs have been fixed: o Wireshark is unresponsive when capturing from named pipes on Windows. (Bug 1759) o Ring buffers are no longer turned on by default when using multiple capture files. New and Updated Features The following features are new (or have been significantly updated) since version 1.4: o Wireshark can import text dumps, similar to text2pcap. o You can now view Wireshark's dissector tables (for example the TCP port to dissector mappings) from the main window. o TShark can show a specific occurrence of a field when using '-T fields'. o Custom columns can show a specific occurrence of a field. o You can hide columns in the packet list. o Wireshark can now export SMB objects. o dftest and randpkt now have manual pages. o TShark can now display iSCSI service response times. o Dumpcap can now save files with a user-specified group id. o Syntax checking is done for capture filters. o You can display the compiled BPF code for capture filters in the Capture Options dialog. o You can now navigate backwards and forwards through TCP and UDP sessions using Ctrl+, and Ctrl+. . o Packet length is (finally) a default column. o TCP window size is now avaiable both scaled and unscaled. A TCP window scaling graph is available in the GUI. o 802.1q VLAN tags are now shown by the Ethernet II dissector. o Various dissectors now display some UTF-16 strings as proper Unicode including the DCE/RPC and SMB dissectors. o The RTP player now has an option to show the time of day in the graph in addition to the seconds since beginning of capture. o The RTP player now shows why media interruptions occur. o Graphs now save as PNG images by default. o TShark can read and write host name information from and to pcapng-formatted files. Wireshark can read it. TShark can dump host name information via [-z hosts] o The tshark -z option now uses the [-z <proto>,srt] syntax instead of [-z <proto>,rtt] for all protocols that support service response time statistics. This syntax now matches Wireshark's syntax for this option. New Protocol Support ADwin, ADwin-Config, Apache Etch, Aruba PAPI, Babel Routing Protocol, Constrained Application Protocol (COAP), Digium TDMoE, Erlang Distribution Protocol, Ether-S-I/O, FastCGI, Fibre Channel over InfiniBand (FCoIB), Gopher, Gigamon GMHDR, IDMP, Infiniband Socket Direct Protocol (SDP), JSON, LISP Data, MikroTik MAC-Telnet, Mongo Wire Protocol, Network Monitor 802.11 radio header, OPC UA ExtensionObjects, PPI-GEOLOCATION-GPS, ReLOAD, ReLOAD Framing, RSIP, SAMETIME, SCoP, SGSAP, Tektronix Teklink, WAI authentication, Wi-Fi P2P (Wi-Fi Direct) Updated Protocol Support New and Updated Capture File Support Apple PacketLogger, Catapult DCT2000, Daintree SNA, Endace ERF, HP OpenVMS TCPTrace, IPFIX (the file format, not the protocol), Lucent/Ascend debug, Microsoft Network Monitor, Network Instruments, TamoSoft CommView Digests wireshark-1.5.1.tar.bz2: 21127616 bytes MD5(wireshark-1.5.1.tar.bz2)=9c934fa4e2d1cb1b0585c1a0956bd80b SHA1(wireshark-1.5.1.tar.bz2)=9a17ca74bbf9c508cd722f2287ea5e7eb93f51ee RIPEMD160(wireshark-1.5.1.tar.bz2)=f97f8f368a70c45568883d4f861eed36f9856b90 wireshark-win32-1.5.1.exe: 18907608 bytes MD5(wireshark-win32-1.5.1.exe)=5d8320020b853ccbe1c4644b7deb8685 SHA1(wireshark-win32-1.5.1.exe)=ed4e8215ffde454e3fef95d351cf10fbd7c69717 RIPEMD160(wireshark-win32-1.5.1.exe)=b93cfd3c71d1b154a1861fafb2651373ba58393c wireshark-win64-1.5.1.exe: 22356611 bytes MD5(wireshark-win64-1.5.1.exe)=2c7bfe85abd96f94542a7842ed6c84e5 SHA1(wireshark-win64-1.5.1.exe)=c489363f54b55ac19b33bf28febc1380520c68e3 RIPEMD160(wireshark-win64-1.5.1.exe)=a3ccccd29bd7000445b76c4d196ca0451e566fa9 wireshark-1.5.1.u3p: 25258080 bytes MD5(wireshark-1.5.1.u3p)=85cd0e52b03f4352e6508ae7589296a9 SHA1(wireshark-1.5.1.u3p)=8754d8a55299a0ea5f70d2b76075106c7d04b0e7 RIPEMD160(wireshark-1.5.1.u3p)=42b18ace398343ced2ab80544013020e85adc001 WiresharkPortable-1.5.1.paf.exe: 19769672 bytes MD5(WiresharkPortable-1.5.1.paf.exe)=271b31fe3e189e2a4ca5d5388d908024 SHA1(WiresharkPortable-1.5.1.paf.exe)=e23cefd36bdbab8e16f72acc4e441cf77fc0c91b RIPEMD160(WiresharkPortable-1.5.1.paf.exe)=3280f0de991939520407fd26b19b6507828e8a02 Wireshark 1.5.1 Intel 32.dmg: 47995111 bytes MD5(Wireshark 1.5.1 Intel 32.dmg)=6dc706bbc38b1a5865c0abeeb7dd2908 SHA1(Wireshark 1.5.1 Intel 32.dmg)=c45a2b2c7b94ebbcdd0512c8b3b8e38618902851 RIPEMD160(Wireshark 1.5.1 Intel 32.dmg)=0b4763402db772f39625f5df367f87ee3a47b711 Wireshark 1.5.1 Intel 64.dmg: 43314737 bytes MD5(Wireshark 1.5.1 Intel 64.dmg)=b3a5ce957aef3c95e4936b14bfeed36e SHA1(Wireshark 1.5.1 Intel 64.dmg)=a1959275c359c53ef681637bed34520b01934a13 RIPEMD160(Wireshark 1.5.1 Intel 64.dmg)=b9c2765f467ea24f92a6387f755ea1f190ee62f8 Wireshark 1.5.1 PPC 32.dmg: 50634026 bytes MD5(Wireshark 1.5.1 PPC 32.dmg)=b44232437fcc5c7b327f3a13b89b9111 SHA1(Wireshark 1.5.1 PPC 32.dmg)=66f8d09fd662fa903ebcd18815f8d5ed5311601f RIPEMD160(Wireshark 1.5.1 PPC 32.dmg)=c7f9d12fe7e13c887abff796212a97f8202e2519 patch-wireshark-1.5.0-to-1.5.1.diff.bz2: 1566926 bytes MD5(patch-wireshark-1.5.0-to-1.5.1.diff.bz2)=225103a1d2fc6890abbb62fe87a14b12 SHA1(patch-wireshark-1.5.0-to-1.5.1.diff.bz2)=2aea37c3f2fba0228832e5b9db42026f7bc06a37 RIPEMD160(patch-wireshark-1.5.0-to-1.5.1.diff.bz2)=8844b5570e821fbc6ddcc9d34c06e38ce78d9139 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2jbAAACgkQpw8IXSHylJpBIwCdFJnjTEYJJ/0HYFzcvoHET2Un oDQAoL9SLMuwSJLqx5L+MCe2KFBAKocp =bVG3 -----END PGP SIGNATURE-----
- Prev by Date: Re: [Wireshark-users] Wireshark runtime error in readin TCPDump trace
- Next by Date: [Wireshark-users] Error: invalid command name "errOut"
- Previous by thread: Re: [Wireshark-users] Wireshark-users Digest, Vol 59, Issue 9
- Next by thread: [Wireshark-users] Error: invalid command name "errOut"
- Index(es):