Wireshark-users: Re: [Wireshark-users] Wireshark 1.4.0 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Tue, 31 Aug 2010 08:25:25 -0700
Which platform build are you using? Note that the 64-bit Windows
installer doesn't yet support libsmi, which is required for SNMP:
http://wiki.wireshark.org/Development/Win64 Glenn Andrews wrote:
Hello Mr Combs, Are SNMP MIBs no longer supported by Wireshark 1.4.0 (SVN Rev 34005 from /trunk1.4) ?Edit, Preferences, Name Resolution doesn't list SMI (MIB and PIB) pathsSMI (MIB and PIB) modules. GlennOn Mon, Aug 30, 2010 at 2:03 PM, Gerald Combs <gerald@xxxxxxxxxxxxx <mailto:gerald@xxxxxxxxxxxxx>> wrote:-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.4.0. 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 Update time display in background. (Bug 1275) o Wireshark is unresponsive when capturing from named pipes on Windows. (Bug 1759) o Tshark returns 0 even with an invalid interface or capture filter. (Bug 4735) New and Updated Features The following features are new (or have been significantly updated) since version 1.2: o The packet list internals have been rewritten and are now more efficient. o Columns are easier to use. You can add a protocol field as a column by right-clicking on its packet detail item, and you can adjust some column preferences by right-clicking the column header. o Preliminary Python scripting support has been added. o Many memory leaks have been fixed. o Wireshark 1.4 does not support Windows 2000. Please use Wireshark 1.2 or 1.0 on those systems. o Packets can now be ignored (excluded from dissection), similar to the way they can be marked. o Manual IP address resolution is now supported. o Columns with seconds can now be displayed as hours, minutes and seconds. o You can now set the capture buffer size on UNIX and Linux if you have libpcap 1.0.0 or greater. o TShark no longer needs elevated privileges on UNIX or Linux to list interfaces. Only dumpcap requires privileges now. o Wireshark and TShark can enable 802.11 monitor mode directly if you have libpcap 1.0.0 or greater. o You can play RTP streams directly from the RTP Analysis window. o Capinfos and editcap now respectively support time order checking and forcing. o Wireshark now has a "jump to timestamp" command-line option. o You can open JPEG files directly in Wireshark. New Protocol Support 3GPP Nb Interface RTP Multiplex, Access Node Control Protocol, Apple Network-MIDI Session Protocol, ARUBA encapsulated remote mirroring, Assa Abloy R3, Asynchronous Transfer Mode, B.A.T.M.A.N. Advanced Protocol, Bluetooth AMP Packet, Bluetooth OBEX, Bundle Protocol, CIP Class Generic, CIP Connection Configuration Object, CIP Connection Manager, CIP Message Router, collectd network data, Control And Provisioning of Wireless Access Points, Controller Area Network, Device Level Ring, DOCSIS Bonded Initial Ranging Message, Dropbox LAN sync Discovery Protocol, Dropbox LAN sync Protocol, DTN TCP Convergence Layer Protocol, EtherCAT Switch Link, Fibre Channel Delimiters, File Replication Service DFS-R, Gateway Load Balancing Protocol, Gigamon Header, GigE Vision Control Protocol, Git Smart Protocol, GSM over IP ip.access CCM sub-protocol, GSM over IP protocol as used by ip.access, GSM Radiotap, HI2Operations, Host Identity Protocol, HP encapsulated remote mirroring, HP NIC Teaming Heartbeat, IEC61850 Sampled Values, IEEE 1722 Protocol, InfiniBand Link, Interlink Protocol, IPv6 over IEEE 802.15.4, ISO 10035-1 OSI Connectionless Association Control Service, ISO 9548-1 OSI Connectionless Session Protocol, ISO 9576-1 OSI Connectionless Presentation Protocol, ITU-T Q.708 ISPC Analysis, Juniper Packet Mirror, Licklider Transmission Protocol, MPLS PW ATM AAL5 CPCS-SDU mode encapsulation, MPLS PW ATM Cell Header, MPLS PW ATM Control Word, MPLS PW ATM N-to-One encapsulation, no CW, MPLS PW ATM N-to-One encapsulation, with CW, MPLS PW ATM One-to-One or AAL5 PDU encapsulation, Multiple Stream Reservation Protocol, NetPerfMeter Protocol, NetScaler Trace, NexusWare C7 MTP, NSN FLIP, OMRON FINS Protocol, packetbb Protocol, Peer Network Resolution Protocol, PKIX Attribute Certificate, Pseudowire Padding, Server/Application State Protocol, Solaris IPNET, TN3270 Protocol, TN5250 Protocol, TRILL, Twisted Banana, UMTS FP Hint, UMTS MAC, UMTS Metadata, UMTS RLC, USB HID, USB HUB, UTRAN Iuh interface HNBAP signalling, UTRAN Iuh interface RUA signalling, V5.2, Vendor Specific Control Protocol, Vendor Specific Network Protocol, VMware Lab Manager, VXI-11 Asynchronous Abort, VXI-11 Core Protocol, VXI-11 Interrupt, X.411 Message Access Service, ZigBee Cluster Library Updated Protocol Support There are too many to list here. New and Updated Capture File Support Accellent 5Views, ASN.1 Basic Encoding Rules, Catapult DCT2000, Daintree SNA, Endace ERF, EyeSDN, Gammu DCT3 trace, IBM iSeries, JPEG/JFIF, libpcap, Lucent/Ascend access server trace, NetScaler, PacketLogger, pcapng, Shomiti/Finisar Surveyor, Sun snoop, Symbian OS btsnoop, Visual Networks Getting Wireshark Wireshark source code and installation packages are available from http://www.wireshark.org/download.html. Vendor-supplied Packages Most Linux and Unix vendors supply their own Wireshark packages. You can usually install or upgrade Wireshark using the package management system specific to that platform. A list of third-party packages can be found on the download page on the Wireshark web site. File Locations Wireshark and TShark look in several different locations for preference files, plugins, SNMP MIBS, and RADIUS dictionaries. These locations vary from platform to platform. You can use About->Folders to find the default locations on your system. Known Problems Wireshark may appear offscreen on multi-monitor Windows systems. (Bug 553) Wireshark might make your system disassociate from a wireless network on OS X 10.4. (Bug 1315) Dumpcap might not quit if Wireshark or TShark crashes. (Bug 1419) The BER dissector might infinitely loop. (Bug 1516) Capture filters aren't applied when capturing from named pipes. (Bug 1814) Filtering tshark captures with display filters (-R) no longer works. (Bug 2234) The 64-bit Windows installer does not ship with the same libraries as the 32-bit installer. (Bug 3610) Hex pane display issue after startup. (Bug 4056) Packet list rows are oversized. (Bug 4357) Summary pane selected frame highlighting not maintained. (Bug 4445) Getting Help Community support is available on the wireshark-users mailing list. Subscription information and archives for all of Wireshark's mailing lists can be found on the web site. Commercial support is available from CACE Technologies. Training is available from Wireshark University. Frequently Asked Questions A complete FAQ is available on the Wireshark web site. Digests wireshark-1.4.0.tar.bz2: 20481773 bytes MD5(wireshark-1.4.0.tar.bz2)=13b188baea23cdad40b7a55921384a77 SHA1(wireshark-1.4.0.tar.bz2)=a1dc5fa6eff0320da5dad7ec9c8f3a8f5a18be81 RIPEMD160(wireshark-1.4.0.tar.bz2)=8eb683e1a1175a0386fc5f1262f0289af177d17c wireshark-win32-1.4.0.exe: 18827151 bytes MD5(wireshark-win32-1.4.0.exe)=4b77599018805c3ae1869b4ae31be2cb SHA1(wireshark-win32-1.4.0.exe)=01ab870fddd7813c52d5d233a20e709d36be6457 RIPEMD160(wireshark-win32-1.4.0.exe)=aa5f9349b1e4e9977c505a5ed9aac24b174f681f wireshark-win64-1.4.0.exe: 21095401 bytes MD5(wireshark-win64-1.4.0.exe)=1b498da1fd5b61abc2602e40f4f7a1cd SHA1(wireshark-win64-1.4.0.exe)=e191aee1f4f2b6dc015661731c9747ce6fea0c38 RIPEMD160(wireshark-win64-1.4.0.exe)=368a90a1a57464d8b8284e6b37a0453048ce5906 wireshark-1.4.0.u3p: 25142153 bytes MD5(wireshark-1.4.0.u3p)=4e6b11494bf79d674ebbc54f41e8bd45 SHA1(wireshark-1.4.0.u3p)=173ab33117bb9b8657a6ceeeaf8063cb72cb0458 RIPEMD160(wireshark-1.4.0.u3p)=04b605328afaca0b15d0df8c87583a0285e1ef02 WiresharkPortable-1.4.0.paf.exe: 19766405 bytes MD5(WiresharkPortable-1.4.0.paf.exe)=29bfb59eb0822c6be211af6d57972fd7 SHA1(WiresharkPortable-1.4.0.paf.exe)=f50ef39816a57f10e89c09a278f9c472f961f059 RIPEMD160(WiresharkPortable-1.4.0.paf.exe)=de10abacc421fc7b9e21b814620bbdc15c010686 Wireshark 1.4.0 Intel 32.dmg: 47536650 bytes MD5(Wireshark 1.4.0 Intel 32.dmg)=318ee8a2b011a0ab87231f45155ece09 SHA1(Wireshark 1.4.0 Intel 32.dmg)=08bf9ea50d7d9b5dd9557d24392a98b8507e5593 RIPEMD160(Wireshark 1.4.0 Intel 32.dmg)=155cf98c4918375973adea1adfc4cf9c9e7239ba Wireshark 1.4.0 Intel 64.dmg: 44052694 bytes MD5(Wireshark 1.4.0 Intel 64.dmg)=effca506e358c972f9da2e329be0a862 SHA1(Wireshark 1.4.0 Intel 64.dmg)=a63660e53f8885570765b217055c15c31162d620 RIPEMD160(Wireshark 1.4.0 Intel 64.dmg)=c486a29c56ed8f00820135f3ae614d2d1fa1d4c3 Wireshark 1.4.0 PPC 32.dmg: 50055091 bytes MD5(Wireshark 1.4.0 PPC 32.dmg)=505f0c186c89efef3cc8a22d7b939a0b SHA1(Wireshark 1.4.0 PPC 32.dmg)=60e3bf44c4ee695b7e5e75921a1dde5d1ee5d843 RIPEMD160(Wireshark 1.4.0 PPC 32.dmg)=7604b68fb9845d35385ce6784c703f5eadc25b44 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkx78ogACgkQpw8IXSHylJpUUgCfX0wKWBws0RPudyOb0GHU3FpQ KbIAnjL9q6+9ski3GvfvtTjGrodZAhQT =lgFh -----END PGP SIGNATURE----- ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx <mailto:wireshark-users@xxxxxxxxxxxxx>> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx <mailto:wireshark-users-request@xxxxxxxxxxxxx>?subject=unsubscribe ------------------------------------------------------------------------ ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
- Follow-Ups:
- Re: [Wireshark-users] Wireshark 1.4.0 is now available
- From: Glenn Andrews
- Re: [Wireshark-users] Wireshark 1.4.0 is now available
- From: Glenn Andrews
- Re: [Wireshark-users] Wireshark 1.4.0 is now available
- References:
- [Wireshark-users] Wireshark 1.4.0 is now available
- From: Gerald Combs
- Re: [Wireshark-users] Wireshark 1.4.0 is now available
- From: Glenn Andrews
- [Wireshark-users] Wireshark 1.4.0 is now available
- Prev by Date: Re: [Wireshark-users] Wireshark 1.4.0 is now available
- Next by Date: Re: [Wireshark-users] Wireshark 1.4.0 is now available
- Previous by thread: Re: [Wireshark-users] Wireshark 1.4.0 is now available
- Next by thread: Re: [Wireshark-users] Wireshark 1.4.0 is now available
- Index(es):