Hi, I am facing issue with radius accounting request Vs response which is affecting my radius proxy performance. I am seeing delay between radius proxy & radius server. So whenever I plot IO graph (filter name = radius.time) it shows me delay of 5 secs between Request Vs Response. But my radius server vendor is saying that "wireshark is incorrectly showing that information and actually there is no such delay" Could someone please help me identifying what exactly is wrong in wireshark handling? If required I can share radius packet trace. Regards, Vijay asked 22 Feb '11, 12:40  Vijay Gharge |
One Answer:
Have you checked the responses manualy? One thing I can imagine is that your RadiusID is being rotated within the time frame of the capture file. I'm not sure whether the radius dissector currently account for that situation. It might just link each response to the first request with the same RadiusID. If that's the case, please open a bug report at https://bugs.wireshark.org If not, please do share the radius trace-file so we can have a look at what is causing this behavior... answered 22 Feb '11, 14:24  SYN-bit ♦♦ |
Hi Sake,
I have raised bug in wireshark bugzilla. I have also provided radius packet trace for more info. I hope that this will be fixed :-)