Wireshark-users: [Wireshark-users] Wireshark 1.5.0 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Mon, 24 Jan 2011 14:39:16 -0800
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.5.0. 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. New Protocol Support ADwin, ADwin-Config, Apache Etch, Aruba PAPI, Constrained Application Protocol (COAP), Digium TDMoE, 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, SAMETIME, SCoP, SGSAP, Tektronix Teklink, WAI authentication, Wi-Fi P2P (Wi-Fi Direct) 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.0.tar.bz2: 20947661 bytes MD5(wireshark-1.5.0.tar.bz2)=6ad04bf822d47fa0f187665570e50d95 SHA1(wireshark-1.5.0.tar.bz2)=1042041afbf888d5cbb433908931af12838f55f7 RIPEMD160(wireshark-1.5.0.tar.bz2)=864ee893743ae0b4b5b525e1c62f56130c186861 wireshark-win32-1.5.0.exe: 18803967 bytes MD5(wireshark-win32-1.5.0.exe)=e0ed5ad56cd9693afa94285ca45c4adb SHA1(wireshark-win32-1.5.0.exe)=e406d27a3a9ffbcabb313e610b30eb3e12dbfcfe RIPEMD160(wireshark-win32-1.5.0.exe)=2e729bafc7a95843461e4a5aaface2a3460bd2b7 wireshark-win64-1.5.0.exe: 22240325 bytes MD5(wireshark-win64-1.5.0.exe)=0f5b07c78ef5bfeabaf6f216c512debf SHA1(wireshark-win64-1.5.0.exe)=f552528aed28469de1a6e820e7b9dc73218f328a RIPEMD160(wireshark-win64-1.5.0.exe)=cbf6a452b7d62235caae1f838945ea1a86c0ab2c wireshark-1.5.0.u3p: 25018222 bytes MD5(wireshark-1.5.0.u3p)=356c1c22ee50091fc4891ef829620569 SHA1(wireshark-1.5.0.u3p)=b09f6c8671fcd88779368e05b5a17b899557e76a RIPEMD160(wireshark-1.5.0.u3p)=3f32daafe824820de3d9d752411b2b4ef59cfd1d WiresharkPortable-1.5.0.paf.exe: 19543280 bytes MD5(WiresharkPortable-1.5.0.paf.exe)=bfbc14dfef641bf5c59f1ab7a91e0222 SHA1(WiresharkPortable-1.5.0.paf.exe)=f67a3ec0c29278d362c155780d9ad6c5439b6b1f RIPEMD160(WiresharkPortable-1.5.0.paf.exe)=32ac209a4c28c00d0a6ef229697722ad29d1d46f Wireshark 1.5.0 Intel 32.dmg: 47247290 bytes MD5(Wireshark 1.5.0 Intel 32.dmg)=527b5bf2c7ad87909837da282a6b4ab2 SHA1(Wireshark 1.5.0 Intel 32.dmg)=81178812f75155dbad38c70657bdf04fff038bdd RIPEMD160(Wireshark 1.5.0 Intel 32.dmg)=e7d1366d599b5c83f6a5c05551692d2270d26357 Wireshark 1.5.0 Intel 64.dmg: 42629294 bytes MD5(Wireshark 1.5.0 Intel 64.dmg)=a319c0ae8acbe3c96606021b294d1299 SHA1(Wireshark 1.5.0 Intel 64.dmg)=1eafaf283fa964c5e59125cab2de223b4082d7df RIPEMD160(Wireshark 1.5.0 Intel 64.dmg)=b6b8af502479c1dffa04648fcd5132ec411f0545 Wireshark 1.5.0 PPC 32.dmg: 49790053 bytes MD5(Wireshark 1.5.0 PPC 32.dmg)=ef56e129d6b68ba54522d84d5905dd25 SHA1(Wireshark 1.5.0 PPC 32.dmg)=67a7e68dc55caedfe20b69abd36e909423a74cd8 RIPEMD160(Wireshark 1.5.0 PPC 32.dmg)=63c0b440b646b78f69c0dc266cc2348fa121867e -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk09/5QACgkQpw8IXSHylJqGzwCgzgjSWUSkh7hl6+SDchJinGXz 1CwAnjfJKFL3yPxO1D5d35ozc+g2yjoD =sB4k -----END PGP SIGNATURE-----
- Prev by Date: Re: [Wireshark-users] take over responsibility of the pcap_pkthdr *
- Next by Date: [Wireshark-users] How source and destination is identified in Wireshark?
- Previous by thread: Re: [Wireshark-users] take over responsibility of the pcap_pkthdr *
- Next by thread: [Wireshark-users] How source and destination is identified in Wireshark?
- Index(es):