Hello Bill, Guy,
Thus wrote Martin Kaiser (li...@kaiser.cx):
> Thus wrote Guy Harris (g...@alum.mit.edu):
> > > 2. The dissector processes both the pseudo-header and the actual
> > > data.
> > > I.E., From the Wireshark perspective, the pseudo-header is just
> > > part
> > > of the capture
Hi
Yes, that is exactly what I want to see. Let me explain for a second.
I work for a company, developing SPS systems for machines. One of our
system uses a so called "Bus Controller" which communicates using a
Realtime Ethernet Protocol like Sercos III oder Powerlink V2. "Behind"
this Controller
Roland,
Do you want to see the following:
-- FRAME 1
-- ETHERNET II FRAME
-- IP FRAME
-- UDP FRAME
-- MY PROTOCOL FRAME 1/4
-- FRAME 1
-- ETHERNET II FRAME
-- IP FRAME
-- UDP FRAME
-- MY PROTOCOL FRAME 2/4
etc?
Why that? Do yo have a post processing step that relies on this? wireshark is a
p
Steffen DETTMER wrote:
(OT, sorry for my noise on the list)
Well, it IS a development discussion, so I'm not sure it's completely OT.
Also, I think for NULL pointers this is much more easy than to
check for possibly deleted pointers (or otherwise stale pointers
or copies of pointers realloc'd
(OT, sorry for my noise on the list)
Hi,
thanks a lot for your explanations and regarding the
non-buggy/buggy analyzers.
I'm sorry to ask again an OT but I'm not sure if I understood
correctly your explanation regarding `if(pointer)'-checks in
general for `mandatory' pointers. Also it could be t
The Buildbot has detected a new failure of OSX-10.5-PowerPC on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/OSX-10.5-PowerPC/builds/2110
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-ppc
Build Reas
Hello
I have the following situation. The trace identifies (correctly)
packets I am interested in. These packets come from a device, which
collects packets, puts them together into one udp frame, and sends
them over the network. Right now I trace the udp payload, and call the
packet dissector for
The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/2450
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-x86
Build Reason:
Bui
