Wireshark 1.8.6

Egemen

Kilopat
Katılım
28 Ağustos 2011
Mesajlar
8.856
Makaleler
1
Çözümler
10
Yer
Ankara
Daha fazla  
Meslek
Doktor
Bu sürüm ile;
Kod:
# The following bugs have been fixed:
- Lua pinfo.cols.protocol not holding value in postdissector.
- data combined via ssl_desegment_app_data not visible via "Follow SSL Stream" only decrypted ssl data tabs. 
- HTTP application/json-rpc should be decoded/shown as application/json. 
- Maximum value of 802.11-2012 Duration field should be 32767. 
- Voice RTP player crash if player is closed while playing. 
- Display Filter Macros crash. 
- RRC RadioBearerSetup message decoding issue. 
- R-click filters add ! in front of field when choosing "apply as filter>selected". 
- BACnet - Loop Object - Setpoint-Reference property does not decode correctly. 
- WMM TSPEC Element Parsing is not done is wrong due to a wrong switch case number. 
- Incorrect RTP statistics (Lost Packets indication not ok). 
- Registering ieee802154 dissector for IEEE802.15.4 frames inside Linux SLL frames. 
- Version Field is skipped while parsing WMM_TSPEC causing wrong dissecting (1 byte offset missing) of all fields in the TSPEC. 
- [BACnet] UCS-2 strings longer than 127 characters do not decode correctly. 
- Malformed IEEE80211 frame triggers DISSECTOR_ASSERT. 
- Decoding of GSM MAP SMS Diagnostics. 
- Incorrect packet length displayed for Flight Message Transfer Protocol (FMTP). 
- Netflow dissector flowDurationMicroseconds nanosecond conversion wrong. 
- BE (3) AC is wrongly named as "Video" in (qos_acs). 
# Updated Protocol Support
-  ACN, AMQP, ASN.1 PER, BACnet, CIMD, CSN.1, DOCSIS TLVs, DTLS, FCSP,  FMP/NOTIFY, FMTP, GSM MAP SMS, HART/IP, IEEE 802.11, IEEE 802.15.4,  JSON, Linux SLL, LTE RRC, Mount, MPLS Echo, Netflow, RELOAD, RSL, RTP,  RTPS, RTPS2, SABP, SIP, SSL, TCP

İndirme Bağlantısı (32 Bit) : Download Wireshark 1.8.6 (32-bit) - Download - FileHippo.com

İndirme Bağlantısı (64 Bit) : Download Wireshark 1.8.6 (64-bit) - Download - FileHippo.com
 
Uyarı! Bu konu 12 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Geri
Yukarı