Wireshark-dev: Re: [Wireshark-dev] Dealing with aggregated packets
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: "Darien Spencer" <cusneud@xxxxxxxx>
Date: Tue, 3 Jul 2018 07:09:52 +0200
Yes, that is what I had in mind about the packets list control.
 
What happens to the protocol tree when you click the sub packets is still an open question though
Maybe it should show the parent's protocol tree and highlight the protocol item where the sub packet "begin"
or maybe it should only show a partial protocol tree in the first place.
 
Darien
 
Sent: Monday, July 02, 2018 at 1:48 PM
From: "Guy Harris" <guy@xxxxxxxxxxxx>
To: "Developer support list for Wireshark" <wireshark-dev@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] Dealing with aggregated packets
On Jul 2, 2018, at 12:18 PM, Darien Spencer <cusneud@xxxxxxxx> wrote:

> What I had in mind is an option to 'expend' a packet in the main view so its aggregated sub packets are seen in a tree under it
> Here's a mock hoping it's get the idea across:
> https://i.imgur.com/WfSvg6x.png

So is the idea that the "list view" of packets would be turned into a "tree view", and packets with multiple sub packets would have the "open up the tree" triangle to the left, so that you could click on it and go from

1 0.000000 70.95.212.31 208.219.44.14 IUA (RFC 3057) 66 DATA [Malformed Packet]
> 2 0.000000 11353 10991 RANAP 490 LocationReportingControl DirectTransfer (DTAP) (MM) Authentication Request CommonID Security...
3 0.000000 70.95.212.31 208.219.44.14 IUA (RFC 3057) 66 DATA [Malformed Packet]

to

1 0.000000 70.95.212.31 208.219.44.14 IUA (RFC 3057) 66 DATA [Malformed Packet]
V 2 0.000000 11353 10991 RANAP 490 LocationReportingControl DirectTransfer (DTAP) (MM) Authentication Request CommonID Security...
RANAP 30 LocationReportingControl
RANAP 42 (DTAP) (MM) Authentication Request
RANAP 66 CommonID
RANAP 16 SecurityModeCommand
3 0.000000 70.95.212.31 208.219.44.14 IUA (RFC 3057) 66 DATA [Malformed Packet]

and then click on it again and go back to the original?
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe