Wireshark 10.9

The Wireshark download page lists three types of releases: Stable, Old Stable, and Development.

  • The Stable release is the latest official version of Wireshark. In most cases this is the version you should use.
  • The Old Stable release is an older official version of Wireshark which is still supported. You may be required to use one of these, for example if your organization has strict software approval policies.
  • The Development version is used for testing new features. Use this if you need one of those features.

Wireshark Ethereal 0.10.9 Change Log Add info. Wireshark Comments. Blog comments powered by Disqus. Top 5 Contributors sofiane 41,005 Points PKO17 16,000. I get Tdelta value, in second. Next, assuming that the packet arrival time is the time at the end of the packet (when the packet was received and processed by kernel), I calculate idle time between packet N+1 and N, using simple formula: Tdelta - Psize. 8 / 1e9. Psize is packet size in bytes, 1e9 is due to 1GE Ethernet line rate (10^9 bps at L2). The installed version of Wireshark is version 1.10.x prior to 1.10.9. It is, therefore, affected by the following vulnerabilities: - A buffer underflow flaw exists in the 'dissectlog' function of the IrDA dissector, which is triggered when handling malformed packets. Using a specially crafted packet, a remote attacker could cause a denial of. 2011-11-08 22:45. Wireshark downloads sponsored by Riverbed Technology. Riverbed makes lots of nice products. Many of them work great with Wireshark.

The Stable and Old Stable release lifetimes conform to the following guidelines:

  • At least two (and preferably exactly two) branches will be supported at any given time.
  • Each release shall be supported for a minimum of 18 months. Support might be extended to 24 or 30 months, e.g. for releases preceding a major change.
  • Support for release X.Y ends when it reaches the end of its minimum lifetime or when version X.Y+4 is released, whichever comes later.

Depending on the pacing of major releases and their lifetimes we might have an 'Old Old Stable' branch in addition to the Stable and Old Stable ones.

See End of Life planning for life cycle information specific to each release.

A more detailed description can be found in the Release Policy.

Staying Current

Wireshark releases are announced on the wireshark-announce mailing list. A PAD file is also published at https://www.wireshark.org/wireshark-pad.xml.

Release Numbers

To understand the numbering of the releases, see the explanation of release numbers.

Release Planning

For the planning of the upcoming releases and their proposed contents see the roadmap.

Wireshark 10.9

Past Releases

Release Notes for each release are available on the main site.

The git change log provides good information about changes in each release:

  • master-3.2

  • master-3.0

  • master-2.6

  • master-2.4

  • master-2.2

  • master-2.0

  • master-1.12

Changes for older releases are listed in wiki pages:

  • Development/Trunk-1.10

  • Development/Trunk-1.8

  • Development/Trunk-1.6

  • Development/Trunk-1.4

  • Development/Trunk-1.2

  • Development/Trunk-1.0

  • Development/BetaReleases

End of Life planning

In order to limit the development burden, support for a (old-)stable release is eventually ended. This is the planning for abandoning old releases. A note is added why such release may still be relevant for you.

Wireshark 10.9

Version

Stable Release Date

End of Life

Notes

3.4

Q3 2020

Release + 18 or more months

Last release to support Red Hat EL 6? Support ends when 3.8.0 is released.

3.2

December 18, 2019

June 18, 2021 or later

Last release to support Windows 7 and Windows Server 2008 R2. Support ends when 3.6.0 is released.

3.0

February 28, 2019

August 28, 2020 or later

Support ends when 3.4.0 is released.

2.6

April 18, 2018

October 18, 2020

Long term support (LTS). Last release to support GTK+ and Qt4. Last release to support Mac OS X 10.6 and 10.7 and OS X 10.8, 10.9, 10.10, and 10.11.

2.4

July 19, 2017

July 19, 2019

GTK+ UI disabled by default.

2.2

September 7, 2016

September 7, 2018

Last release to support Windows Vista and (the non-R2) Windows Server 2008.

2.0

November 18, 2015

November 18, 2017

Last release to support OS X on 32-bit x86.

1.12

July 31, 2014

July 31, 2016

Last release using the GTK+ GUI by default. Last release to support Windows Server 2003.

1.10

June 5, 2013

June 5, 2015

Last release to support Windows XP and U3 packages.

1.8

June 21, 2012

June 21, 2014

Last release to support Mac OS X on PPC.

1.6

June 7, 2011

June 7, 2013

Last release that compiles on Red Hat EL 5.

1.4

August 30, 2010

August 30, 2012

1.2

June 15, 2009

June 30, 2011

Last release to support Windows 2000.

1.0

March 31, 2008

September 30, 2010

Last release to support GTK+ 1.0.

Discussion

Support for Windows 7 ended on January 14, 2020. Wireshark 3.2 is the last release that supports it.

Support for Windows Vista ended on April 11, 2017. Wireshark 2.2 is the last release that supports it.

Support for Windows XP ended on April 8, 2014. Wireshark 1.10 is the last release that supports it.

U3 reached end of life in 2009. We stopped producing U3 packages when 1.10 reached end of life.

What do SRE and SLE stand for in the packet capture display? I'm looking at TCP packets so I assume it has something to do with windowing.

asked 17 Dec '10, 13:57

catimossi
1111
accept rate:0%

They are the Right Edge (SRE) and Left Edge (SLE) of already acknowledged data when Selective Acknowledgments are used. This prevents retransmission of this data.

See also RFC 2018

answered 17 Dec '10, 17:05

SYN-bit ♦♦
17.1k957245
accept rate:20%

edited 28 Jan '13, 14:49

Guy Harris ♦♦
17.4k335196

Wireshark 10.9 Download

To add to Sake's post, SACK (Selective ACK) is used to identify holes in the TCP stream. This prevents the stack from having to go back to where the loss occurred and start all over. So the pkts from the normal ACK field (in the 'normal' ACK field) to the LE is good to go. But from the LE to the RE, pkts were lost. So if the pkts are transferred like this (1, through 10)

10 9 8 7 6 5 4 3 2 1 --->

in normal ACK scenario, if pkt 4 is lost, it will look like this to the receiver

10 9 8 7 6 5 XX 3 2 1 --->

So the receiver will repeatedly ack saying 'I need pkt 4...I need pkt 4, I need pkt 4' as other pkts (5-10) trickle in. When three of these acks are received, it triggers the fast retransmission, BTW.

When SACK is used, the receiver identifies the hole at pkt 4 position. So it doesn't throw pkts 5-10 away...instead, it sends a SACK requesting for pkt#4.

answered 21 Dec '10, 06:39

hansangb
7912619
accept rate:12%