Ask Your Question
0

IO Graph too many data points

asked 2019-06-10 13:45:26 +0000

tmelton gravatar image

I am graphing IGMP data using the dot format, but instead of showing a dozen dots I get one for each time frame even though there is not a record for it. In previous versions this was not a problem.

Is there a work around or an update coming soon to fix this.

edit retag flag offensive close merge delete

Comments

Can you share a capture, and an image of your graph settings? You can upload to a public file sharing site, e.g. Google Drive, DropBox etc and post a link back here.

grahamb gravatar imagegrahamb ( 2019-06-10 13:59:45 +0000 )edit

http://webguide.cimtel.net/wireshark/... You should be able to view this.

tmelton gravatar imagetmelton ( 2019-06-10 14:09:26 +0000 )edit

Without the capture file itself, it's hard to say if there's anything wrong with the graph. The graph appears to show an IGMP packet received at various intervals, are you saying the capture does NOT have an IGMP packet at the times indicated on the graph?

grahamb gravatar imagegrahamb ( 2019-06-10 17:31:42 +0000 )edit

Sorry, not paying attention.see below Thanks,

http://webguide.cimtel.net/WireShark/

Weirdly, I had to change the extension to get it to download. so remove the .txt and add a period before pcapng after you download it.

tmelton gravatar imagetmelton ( 2019-06-10 18:09:06 +0000 )edit

2 Answers

Sort by ยป oldest newest most voted
0

answered 2019-06-10 19:55:53 +0000

tmelton gravatar image

I did find that changing the graph type to BAR gives the expected result, but is not as precise to read as DOT. This is only a work around and not a solution.

edit flag offensive delete link more
0

answered 2019-06-10 18:26:45 +0000

grahamb gravatar image

Looks fine to me, the dots showing 1 packet and 2 packets correspond with the actual packets in the capture. All the dots at the 0 line show intervals where no IGMP packets were received, i.e. the dot reflects the fact of 0 packets in that interval.

I suspect that your "previous versions" comment refers to the deprecated GTK UI, the graphing has been totally rewritten for the Qt UI, and this may have turned out with differences in displays.

If you feel the current graph is deficient, please raise a bug\enhancement request at the Wireshark Bugzilla.

edit flag offensive delete link more

Comments

That may be how it was designed, but it is not as expected. Previous versions of Wireshark did not show these zero values and I seem unable to filter them out.

If I had chose LINE, I could understand why there would be a line at zero. the Line would be connecting the two existing data points. With DOT, it should only show where there is a data point. the DOTS showing up now are new.

tmelton gravatar imagetmelton ( 2019-06-10 18:31:30 +0000 )edit

I visited Wireshark Bugzilla and found that this bug has been submitted twice and have added my confirmation to on of those listed.

tmelton gravatar imagetmelton ( 2019-06-10 19:54:51 +0000 )edit

For reference, the Bugzilla item is 11694, which has been open for 3.5 years.

grahamb gravatar imagegrahamb ( 2019-06-10 20:25:45 +0000 )edit

I guess that does not bode well for the user base then.

tmelton gravatar imagetmelton ( 2019-06-10 20:27:53 +0000 )edit

I noted the length of time the item has been open to indicate that it doesn't seem to have interested anyone enough to submit a change.

We just need someone with the time and skills to step up and submit a change. Most of the code in Wireshark is submitted by developers working in their spare time on tasks that interest them and meet their needs, and unfortunately this doesn't seem to be an itch for anyone.

grahamb gravatar imagegrahamb ( 2019-06-10 21:16:05 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2019-06-10 13:45:26 +0000

Seen: 47 times

Last updated: Jun 10