Wireshark-users: Re: [Wireshark-users] basic usage problem
Date: Wed, 12 Dec 2012 16:38:47 +0000
And I'm not sure of all the transport particulars.

What I do know is from past usage.  In the past I would see packets labeled GVCP for requests and answers (ie. parameter writing and reading) and other packets labeled UDP which had about 8k of data as we are using Jumbo Frames and Packets.  The coloring was different in the past - maybe there is a GVCP protocol analyzer?

Now, where there should be several hundred 8k+ UDP packets I see nothing. I see the commands that always fall before and after but the data is missing.

Kurt

-----Original Message-----
From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Bill Meier
Sent: Wednesday, December 12, 2012 9:21 AM
To: Community support list for Wireshark
Subject: Re: [Wireshark-users] basic usage problem

On 12/12/2012 9:59 AM, kurt.jensen@xxxxxxxxxxxxxxx wrote:
> Just installed Wireshark and started capture. Plugged in our GigE 
> camera under development.  Connected and collected a frame of data.
>
> Wireshark shows all of the GVCP requests and answers.  Very nice!  But 
> I am not seeing any of the UDP data.  I have no filters set, just 
> selected the interface then slicked start. I have run Wireshark before 
> on another computer where the UDP data just showed up along with the GVCP packets.
> I know the data is there because my PC app displays the image. But not 
> in Wireshark.
>
> How do I get the UDP data?
>
> Kurt
>

I'm not sure I understand.

It appears that GVCP is carried over UDP so it sounds like you are saying that only certain UDP frames are missing.

Is the "data" carried over the GVCP protocol ?

If so, I would expect the data show up as being under the GVCP layer of the protocol tree (as opposed to the frames just showing as UDP.
IOW: the "protocol" column would show GVCP as opposed to UDP.

(I've no knowledge of the GVCP protocol so I may be off-base).

Bill





___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe