Wireshark-bugs: [Wireshark-bugs] [Bug 5720] New: I/O graph based on radius.time filters shows in
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 23 Feb 2011 04:28:27 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5720

           Summary: I/O graph based on radius.time filters shows incorrect
                    graph
           Product: Wireshark
           Version: unspecified
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: Gharge.Vijay@xxxxxxxxx


Created an attachment (id=5972)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=5972)
TCPDUMP PACKET TRACE CAPTURED ON RADIUS SERVER

Build Information:
Version 1.4.3 (SVN Rev 35482 from /trunk-1.4)

Copyright 1998-2011 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (32-bit) with GTK+ 2.16.6, with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with
Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Jan
11 2011), with AirPcap.

Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
I am facing issue with radius accounting request Vs response which is affecting
my radius proxy performance and throws "proxy retry" error message

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?

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.