path: root/docbook/release-notes.xml

<?xml version="1.0"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

<!-- $Id$ -->

<!--
DOCUMENT SECTION
-Use this section to encode all document information
-->

<!--
Wireshark Info
-->
  <!ENTITY WiresharkCurrentVersion "1.3.6">

]>

<article>
  <title>Wireshark &WiresharkCurrentVersion; Release Notes</title>

  <section id="WhatIs"><title>What is Wireshark?</title>
    <para>
      Wireshark is the world's most popular network protocol analyzer.  It
      is used for troubleshooting, analysis, development and education.
    </para>
  </section>

  <section id="WhatsNew"><title>What's New</title>
    <section id="BugFixes"><title>Bug Fixes</title>

    <para>

    The following bugs have been fixed:

      <itemizedlist>

        <listitem><para>
          Wireshark is unresponsive when capturing from named pipes on Windows.
          (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1759">Bug
          1759</ulink>)
        </para></listitem>

      </itemizedlist>

    </para>

    </section>

    <section id="NewFeatures"><title>New and Updated Features</title>
    <para>
      The following features are new (or have been significantly updated)
      since version 1.2:

      <itemizedlist>

        <listitem>
          <para>
            The packet list internals have been rewritten and are now more
            efficient.
          </para>
        </listitem>

        <listitem>
          <para>
            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.
          </para>
        </listitem>

        <listitem>
          <para>
            Preliminary Python scripting support has been added.
          </para>
        </listitem>

        <listitem>
          <para>
            Many memory leaks have been fixed.
          </para>
        </listitem>

        <listitem>
          <para>
            Wireshark no longer supports Windows 2000. Please use
            Wireshark 1.2 or 1.0 on those systems.
          </para>
        </listitem>

        <listitem>
          <para>
            Packets can now be ignored (excluded from dissection), similar to
            the way they can be marked.
          </para>
        </listitem>

        <listitem>
          <para>
            Manual IP address resolution is now supported.
          </para>
        </listitem>

        <listitem>
          <para>
            Columns with seconds can now be displayed as hours, minutes and
            seconds.
          </para>
        </listitem>

        <listitem>
          <para>
            You can now set the capture buffer size on UNIX and Linux if you have
            libpcap 1.0.0 or greater.
          </para>
        </listitem>

        <listitem>
          <para>
            TShark no longer needs elevated privileges on UNIX or Linux to list
            interfaces. Only dumpcap requires privileges now.
          </para>
        </listitem>

        <listitem>
          <para>
            Wireshark and TShark can enable 802.11 monitor mode directly if you
            have libpcap 1.0.0 or greater.
          </para>
        </listitem>

        <listitem>
          <para>
            Play the RTP stream directly from the RTP Analysis.
          </para>
        </listitem>

        <listitem>
          <para>
            Capinfos now checks the time order of capture files.
          </para>
        </listitem>

      </itemizedlist>

    </para>
    </section>

    <section id="NewProtocols"><title>New Protocol Support</title>
    <para>

    </para>
    </section>

    <section id="UpdatedProtocols"><title>Updated Protocol Support</title> <para>

    </para>
    </section>

    <section id="NewCapture"><title>New and Updated Capture File Support</title>
    <para>

    </para>
    </section>

  </section>

  <section id="GettingWireshark"><title>Getting Wireshark</title>
    <para>
      Wireshark source code and installation packages are available from
      <ulink url="http://www.wireshark.org/download.html">http://www.wireshark.org/download.html</ulink>.
    </para>

    <section id="VendorPackages"><title>Vendor-supplied Packages</title>
      <para>
        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
        <ulink url="http://www.wireshark.org/download.html#thirdparty">download page</ulink>
        on the Wireshark web site.
      </para>
    </section>

  </section>

  <!-- XXX needs to be written
  <section id="RemovingWireshark"><title>Removing Wireshark</title>
    <para>
    </para>
  </section>
  -->

  <section id="FileLocations"><title>File Locations</title>
    <para>
      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.
    </para>
  </section>

  <section id="KnownProblems"><title>Known Problems</title>

    <para>
      Wireshark may appear offscreen on multi-monitor Windows systems.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=553">Bug
      553</ulink>)
    </para>

    <para>
      Wireshark might make your system disassociate from a wireless network
      on OS X 10.4.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1315">Bug
      1315</ulink>)
    </para>

    <para>
      Dumpcap might not quit if Wireshark or TShark crashes.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419">Bug
      1419</ulink>)
    </para>

    <para>
      The BER dissector might infinitely loop.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516">Bug
      1516</ulink>)
    </para>

    <para>
      Capture filters aren't applied when capturing from named pipes.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814">Bug
      1814</ulink>)
    </para>

    <para>
      Filtering tshark captures with display filters (-R) no longer works.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234">Bug
      2234</ulink>)
    </para>

    <para>
      The 64-bit Windows installer does not ship with the same libraries as the
      32-bit installer.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3610">Bug
      3610</ulink>)
    </para>

    <para>
      Application crash when changing real-time option.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035">Bug
      4035</ulink>)
    </para>

    <para>
      Hex pane display issue after startup.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056">Bug
      4056</ulink>)
    </para>

    <para>
      Crash when sorting column while capturing.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4273">Bug
      4273</ulink>)
    </para>

    <para>
      Packet list rows are oversized.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357">Bug
      4357</ulink>)
    </para>

    <para>
      Summary pane selected frame highlighting not maintained.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4445">Bug
      4445</ulink>)
    </para>

  </section>

  <section id="GettingHelp"><title>Getting Help</title>
    <para>
    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 <ulink url="http://www.wireshark.org/lists/">the
    web site</ulink>.
    </para>
    <para>
    Commercial support is available from
    <ulink url="http://www.cacetech.com/products/sharknet.html">CACE Technologies</ulink>.
    </para>
    <para>
    Training is available from
    <ulink url="http://www.wiresharktraining.com/">Wireshark University</ulink>.
    </para>
  </section>

  <section id="FAQ"><title>Frequently Asked Questions</title>
    <para>
    A complete FAQ is available on the
    <ulink url="http://www.wireshark.org/faq.html">Wireshark web site</ulink>.
    </para>
  </section>

</article>