Wireshark · Wireshark-users: Re: [Wireshark-users] Wireshark 1.4.0rc1 is now available, Signatur Fehler

[<joerg.jacobsen@xxxxxx>]

Hi Gerald,

maybe i'm just too blind and it's to early in the morning for me,
but i am missing the IP flags. Where are they gone?

Jörg



-----Ursprüngliche Nachricht-----
Von: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] Im Auftrag von Gerald Combs
Gesendet: Mittwoch, 9. Juni 2010 23:45
An: wireshark-announce@xxxxxxxxxxxxx; Community support list for Wireshark; Developer support list for Wireshark
Betreff: [Wireshark-users] Wireshark 1.4.0rc1 is now available, Signatur Fehler


I'm proud to announce the release of Wireshark 1.4.0rc1. This is the first release candidate of the upcoming 1.4 (stable) branch.

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)

  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, 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.0rc1.tar.bz2: 20400088 bytes MD5(wireshark-1.4.0rc1.tar.bz2)=ca5ee30ed798900142d9cd4d81637b58
SHA1(wireshark-1.4.0rc1.tar.bz2)=35978e507966d18fefcf63f8746dbd31d2cb94ac
RIPEMD160(wireshark-1.4.0rc1.tar.bz2)=0518fe9acf84867360086acb3dde930f0862dae7

wireshark-win32-1.4.0rc1.exe: 18809931 bytes MD5(wireshark-win32-1.4.0rc1.exe)=69d775f9f99c928f7807fe684b7b6a29
SHA1(wireshark-win32-1.4.0rc1.exe)=27154545cbe486d09909f27a94a2cb9940672e73
RIPEMD160(wireshark-win32-1.4.0rc1.exe)=3419a20d598e4afea2460ac28850d939f7b5c25b

wireshark-win64-1.4.0rc1.exe: 21076356 bytes MD5(wireshark-win64-1.4.0rc1.exe)=cb90223fce5623b370f2819d96c1532f
SHA1(wireshark-win64-1.4.0rc1.exe)=6540b93572cbc91d41d488d90bd37ec83c3cea61
RIPEMD160(wireshark-win64-1.4.0rc1.exe)=5215ed82cfa6351953ca1765f5ebc02a2aed0719

wireshark-1.4.0rc1.u3p: 25113395 bytes MD5(wireshark-1.4.0rc1.u3p)=250132693632807eb7d93e3fbc9b7abf
SHA1(wireshark-1.4.0rc1.u3p)=6952bbbc35e08f6dff772db3a224309591d5a654
RIPEMD160(wireshark-1.4.0rc1.u3p)=e726f8e5c98622fb7fdd1602c20d686cae4122ec

WiresharkPortable-1.4.0rc1.paf.exe: 19662284 bytes MD5(WiresharkPortable-1.4.0rc1.paf.exe)=ab28e06c55388d6dfa5d14ce5b47d8c5
SHA1(WiresharkPortable-1.4.0rc1.paf.exe)=f49d31d0e903014cb70fecd861054286b9b63750
RIPEMD160(WiresharkPortable-1.4.0rc1.paf.exe)=cbc146c82c243b0b49a7657b822a424588c284f5

Wireshark 1.4.0rc1 Intel.dmg: 47434237 bytes
MD5(Wireshark 1.4.0rc1 Intel.dmg)=c2b6ace0c8afebdec137b12723939a99
SHA1(Wireshark 1.4.0rc1 Intel.dmg)=d7ab04567653f5020c0b962f5c190525c90ff82d
RIPEMD160(Wireshark 1.4.0rc1 Intel.dmg)=7d215a95f319be1925109c71f5c77bb46e156547

Wireshark 1.4.0rc1 PPC.dmg: 49948660 bytes
MD5(Wireshark 1.4.0rc1 PPC.dmg)=2477acb66d321c2a95dee61f1f11a74e
SHA1(Wireshark 1.4.0rc1 PPC.dmg)=f30067d367146727ce66485b4b3c88742168bd71
RIPEMD160(Wireshark 1.4.0rc1 PPC.dmg)=98aee9f38b7272281c2cddc08ae63782c2f19457