Wireshark 1.6.7 (32-bit)

[McLovin]

Wireshark is the world's foremost network protocol analyzer, and is the de facto standard across many industries and educational institutions.

• Deep inspection of hundreds of protocols, with more being added all the time
• Live capture and offline analysis
• Standard three-pane packet browser
• Multi-platform: Runs on Windows, Linux, OS X, Solaris, FreeBSD, NetBSD, and many others
• Captured network data can be browsed via a GUI, or via the TTY-mode TShark utility
• The most powerful display filters in the industry
• Rich VoIP analysis
• Read/write many different capture file formats
• Capture files compressed with gzip can be decompressed on the fly
• Live data can be read from Ethernet, IEEE 802.11, PPP/HDLC, ATM, Bluetooth, USB, Token Ring, Frame Relay, FDDI, and others (depending on your platfrom)
• Decryption support for many protocols, including IPsec, ISAKMP, Kerberos, SNMPv3, SSL/TLS, WEP, and WPA/WPA2
• Coloring rules can be applied to the packet list for quick, intuitive analysis
• Output can be exported to XML, PostScript®, CSV, or plain text

Change Log - Link.

The following bugs have been fixed:

• Wireshark could crash while reading SSL decryption keys on 64-bit Windows.
• Malformed Packets H263-1996 (RFC2190). (Bug 6996)
• Wireshark could crash while trying to open an rpcap: URL. (Bug 6922)

Updated Protocol Support:

• H.263

Download.

 

[savit]

Thanks~ Updated! http://www.wireshark.org/download.html

 

[McLovin]

# The following bugs have been fixed:
* Move Y.1711 out of MPLS dissector.
* Patch: Add frame.interface_id support for ERF file format.
* Freeze when Resizing or Moving while capturing.
* Wireshark crashes when using multiple files.
* Wireshark crashes on opening very short NFS pcap file.
* Analyze->Apply as Filter and Analyze->Prepare a Filter cause crashes.
* crashes in interface list, pipe handling.
* ISDN LAPD X.31 packet traffic can not be decoded.
* GIOP request_id used for sub dissectors is not assigned when decoding GIOP 1.2 Request message.
* pcap-ng -ISB always writes 0 for isb_ifrecv option.
* GSM classmark3 decode wrong.
* mem corruption\heap corruption\div0 bugs.
* DNS AD flag not shown properly.
* Wireshark and TShark crash at start with invalid color filter on SPARC.
# Updated Protocol Support
* AFP, Apache JServ Protocol v1.3, Bluetooth L2CAP, CIP, CTDB, DCP ETSI, ERF, EtherCAT Mailbox, FC Link Control, GIOP, GSM A, GSM RLC MAC, GTP, GTPv2, ISDN, LISP, MongoDB, MPLS ITU-T Y.1711 OAM, MPLS PM, NFS, RTPS2, SCTP, STUN, XTP
# New and Updated Capture File Support
* Ixia IxVeriWave, pcap-ng

Sources..

 

[McLovin]

# The following bugs have been fixed:
- The HTTP dissector does not reassemble headers when the first TCP segment does not contain a full header line.
- HDCP2 uses the wrong protocol id.
- Several I/O graph problems have been fixed.
- No markers show up when maps are displayed.
- Assertion when using tshark/wireshark on large captures.
- Volume label field of "SMB/TRANS2-QUERY_FS_INFO/InfoVolume level" reply packet is not displayed correctly due alignment issue.
- 64-bit Wireshark appears to hit 2-Gbyte memory limit on 64-bit Windows.
- Truncated/partial JPEG files are not dissected.
- Support for MPLS Packet Loss and Delay Measurement, RFC 6374.
- Memory leak in voip_calls.c.
- When listing protocols available for "Decode As", plugins are sorted after built-ins.
- Hidden columns should not be printed when printing packet summary line.
- Size wrong in "File Set List" for just-finished captures.
- Error: no dependency information found for debian/wireshark-common/usr/lib/wireshark/libwsutil.so.2 (used by debian/wireshark/usr/bin/wireshark).
- Parse and properly display LTE RADIUS AVP 3GPP-User-Location-Info.
- [PATCH] HomeplugAV dissector: decode device id.
- BACnet GetEnrollmentSummary-ACK does not decode correctly.
- epan/dissectors/packet-per.c dissect_per_constrained_integer_64b fails for 64 bits.
- New SCTP PPID 48.
- dissector of Qos attribute "Reliability Class" in GMM/SM message.
- Performance regression in tshark -z io,stat.
- Incorrect io-stat table format when unsupported "-t" operand is specified and when using AVG of relative_time fields.
- IEEE 802.11 TKIP dissection : wrong IS_TKIP macro.
- Homeplug AV dissectors does not properly dissect short frames.
- mm_context_nas_dl_cnt and mm_context_nas_ul_cnt are not dissected properly in ContextResponse message in Gtpv2.
- This trace causes Wireshark to crash when VoIP Calls selected.
- Some diameter Gx enumerations are missing values or value is incorrect.
- Wireshark 1.8.2 is only displaying 2 filters from the drop-down menu even when preferences are set to higher integer.
- BGP bad decoding for Graceful Restart Capability with only helper support & for Enhanced Route Refresh Capability.
- Dissection error of D-RELEASE and D-CONNECT in TETRA dissector.
- DND can cause Wireshark to crash.
- SCSI: WRITE BUFFER fields always display as zero.
# Updated Protocol Support
- ASN.1 PER, BACnet, BGP, DIAMETER, DRDA, DVB CI, DVB, GSM Management, GTP, GTPv2, HDCP2, HomePlug AV, ICMP, ICMPv6, IEEE 802.11, IEEE 802a, Interlink, JPEG, LDP, LPP, MPEG, MPLS, PCAP, PPP, RANAP, RRC, RRLP, SCCP, SCSI, SCTP, SDP, SMB, TETRA

Sources.

 

[Nige_40]

Never Used Wireshark I've never understood the comsept of it, and How to use it.

So if I knew what it was about, and how it was used then I would try it.

Regards

Nigel

 

[McLovin]

Never Used Wireshark I've never understood the comsept of it, and How to use it.

So if I knew what it was about, and how it was used then I would try it.

Regards

Nigel

Only thing is and for all I know it's this

Wireshark is the world's foremost network protocol analyzer, and is the de facto standard across many industries and educational institutions.

• Deep inspection of hundreds of protocols, with more being added all the time
• Live capture and offline analysis
• Standard three-pane packet browser
• Multi-platform: Runs on Windows, Linux, OS X, Solaris, FreeBSD, NetBSD, and many others
• Captured network data can be browsed via a GUI, or via the TTY-mode TShark utility
• The most powerful display filters in the industry
• Rich VoIP analysis
• Read/write many different capture file formats
• Capture files compressed with gzip can be decompressed on the fly
• Live data can be read from Ethernet, IEEE 802.11, PPP/HDLC, ATM, Bluetooth, USB, Token Ring, Frame Relay, FDDI, and others (depending on your platfrom)
• Decryption support for many protocols, including IPsec, ISAKMP, Kerberos, SNMPv3, SSL/TLS, WEP, and WPA/WPA2
• Coloring rules can be applied to the packet list for quick, intuitive analysis
• Output can be exported to XML, PostScript®, CSV, or plain text

 

[Nige_40]

Never Used Wireshark I've never understood the comsept of it, and How to use it.

So if I knew what it was about, and how it was used then I would try it.

Regards

Nigel

Only thing is and for all I know it's this

Wireshark is the world's foremost network protocol analyzer, and is the de facto standard across many industries and educational institutions.

• Deep inspection of hundreds of protocols, with more being added all the time
• Live capture and offline analysis
• Standard three-pane packet browser
• Multi-platform: Runs on Windows, Linux, OS X, Solaris, FreeBSD, NetBSD, and many others
• Captured network data can be browsed via a GUI, or via the TTY-mode TShark utility
• The most powerful display filters in the industry
• Rich VoIP analysis
• Read/write many different capture file formats
• Capture files compressed with gzip can be decompressed on the fly
• Live data can be read from Ethernet, IEEE 802.11, PPP/HDLC, ATM, Bluetooth, USB, Token Ring, Frame Relay, FDDI, and others (depending on your platfrom)
• Decryption support for many protocols, including IPsec, ISAKMP, Kerberos, SNMPv3, SSL/TLS, WEP, and WPA/WPA2
• Coloring rules can be applied to the packet list for quick, intuitive analysis
• Output can be exported to XML, PostScript®, CSV, or plain text

Thanks Mc Lovin

 

[McLovin]

Thanks Mc Lovin

No problem. Glad that I could help

 

[Deleted member 178]

Never Used Wireshark I've never understood the comsept of it, and How to use it.

Wireshark is a packet/protocol/network analyzer, used mostly by network admins, but also by war-driving hackers who can capture wifi packets then crack the password and "read" the transmitted datas

 

[Nige_40]

Never Used Wireshark I've never understood the comsept of it, and How to use it.

Wireshark is a packet/protocol/network analyzer, used mostly by network admins, but also by war-driving hackers who can capture wifi packets then crack the password and "read" the transmitted datas

Thanks you for that Umbra.

I kind of got the hang of it now.

Thanks for the info.

Regards

Nigel