Wireshark-bugs: [Wireshark-bugs] [Bug 10487] New: RADIUS Disconnect-NAK replies not associated w
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 19 Sep 2014 15:57:38 +0000
Bug ID 10487
Summary RADIUS Disconnect-NAK replies not associated with Disconnect-Requests
Product Wireshark
Version 1.12.0
Hardware x86-64
OS Windows 7
Status UNCONFIRMED
Severity Normal
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter dandreye@cisco.com 

Created attachment 13078 [details]
2 request-reply pairs illustrating the difference between ACK and NAK

Build Information:
Version 1.12.1 (v1.12.1-0-g01b65bf from master-1.12)
--
RADIUS Disconnect-NAK replies are not associated with their respective
Disconnect-Requests based on Packet ID value in them:
- they have no "This is a response to a request in frame x" line
- their respective Disconnect-Request messages have no "The response to this
request is in frame y" line

Disconnect-ACK replies have no such problem, so seems like RADIUS dissector
effectively doesn't consider NAK as a response. This doesn't look right since
there should never be any further response following a NAK: ACK and NAK they
are 2 alternative valid responses on Disconnect-Request.

Initially discussed here:
https://ask.wireshark.org/questions/36451/radius-disconnect-nak-replies-not-associated-with-disconnect-requests


Thanks in advance!

You are receiving this mail because:
  • You are watching all bug changes.