[Wireshark-dev] Wireshark Windows VERSIONINFO resource

Hi list, Currently Wireshark sports in the Windows VERSIOINFO resource the FILEOS parameter VOS__WINDOWS32 (File was designed for 32-bit Windows). Since we don't support Win95/98/ME any more should we change this into VOS_NT (File was designed for Windows Server 2003 family, Windows XP, Windows 20

Re: [Wireshark-dev] Using Lua to parse TCP encapsulated IP protocol

Hi, * Can you test it against 0.99.5pre1? I cannot make it crash (works OK for me), could you send the capture file that does crash? Could you eventually send in also the output of wireshark -v Thanks Luis BTW sub_buf = buffer( 4, buffer:len() - 4 ):tvb() is the same as sub_buf = buffer(4):tvb()

Re: [Wireshark-dev] Win32: Visual Studio Express as default?

Hi, Well, in a perfect world this scheme would work. Unfortunately. So how do we help a user with an 'inperfect' plugin developer? Could the whole range of runtime DLL's help? I guess not, mixing runtimes doesn't sound like a plan. Check DLL dependancies? Could help if we can detect a mismatch

Re: [Wireshark-dev] [Patch] airpcap_loader.h

Checked in with r20535. Thanks! Gisle Vanem wrote: > A case of conflict in definition and implementation: > > --- SVN-Latest\airpcap_loader.h Mon Jan 22 22:20:27 2007 > +++ airpcap_loader.hMon Jan 22 22:37:08 2007 > @@ -309,7 +309,7 @@ > * Will return null if no device is found. > */ > GL

Re: [Wireshark-dev] Win32: Visual Studio Express as default?

> > I can see version hell on the horizon :/ > Would it be wise to add the compiler version to the plugin version > resource? If time permits I'll start looking into it tonight. > sort of... It's like the problem with our current plugin mechanism in general, a plugin build for a different

[Wireshark-dev] Using tcp_dissect pdus and fragment, segment reassembly

I've been attempting to add tcp fragment reassembly using tcp_dissect_pdus() to an existing dissector that already used the epan reassembly code for an internal part of the protocol. However it seems that when I add the tcp_dissect_pdus() call then the other reassembly stops working. The call to

Re: [Wireshark-dev] Win32: Visual Studio Express as default?

Hi, I can see version hell on the horizon :/ Would it be wise to add the compiler version to the plugin version resource? If time permits I'll start looking into it tonight. Thanx, Jaap On Tue, 23 Jan 2007, Ulf Lamping wrote: > > > I have successfully compiled WS by following the new proced

Re: [Wireshark-dev] proto_tree_add_item problem

[EMAIL PROTECTED] wrote: > I've developed a dissector and it has one statement as : > proto_tree_add_item(proto_tree, hf_xyz_any_field, tvb, offset, 16, > FALSE); > > > This statement is not getting executed , the wireshark is giving error " > malformed packet ". > But when I'm changing

Re: [Wireshark-dev] Win32: Visual Studio Express as default?

> I have successfully compiled WS by following the new procedure on the WS > developer guide: > http://www.wireshark.org/docs/wsdg_html/#ChSetupWin32 > The team did a great job: now everybody can compile WS for free! Thanks, it was indeed some hard work to make this as smooth as possible. > > N

Re: [Wireshark-dev] proto_tree_add_item problem

Hi Vikash, You should rather write proto_tree_add_item(proto_tree,hf_xyz_any_field, tvb, offset, 1,FALSE) because the value that you want to display is a single byte (FT_UINT8). David Bored stiff? Loosen u

[Wireshark-dev] Win32: Visual Studio Express as default?

Hello, I have successfully compiled WS by following the new procedure on the WS developer guide: http://www.wireshark.org/docs/wsdg_html/#ChSetupWin32 The team did a great job: now everybody can compile WS for free! Now, the issue I have is that plugins compiled with this setup do not load in ear

[Wireshark-dev] proto_tree_add_item problem

Hi , I've developed a dissector and it has one statement as : proto_tree_add_item(proto_tree, hf_xyz_any_field, tvb, offset, 16, FALSE); This statement is not getting executed , the wireshark is giving error " malformed packet ". But when I'm changing the length ( 16 ) to smaller value ,

Re: [Wireshark-dev] [PATCH] New menu items to copy packet data

Hi Steve > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Stephen Fisher > Sent: 22 January 2007 20:24 > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] [PATCH] New menu items to copy > packet data > > On Mon, Jan 22, 200

Re: [Wireshark-dev] How to modify hf_register_info hf[] ?

Hi, That doesn´t seem to work. In the dissect_zigbee I read the 4 Bit and calculate them to an offset value. This value I use in: proto_tree_add_item(adr_tree, hf_zigbee_adr_dest,tvb,5, dest_offset, FALSE); So the added Item should have the correct length.(dest_offset = 0 / 2 / 8) In the hf_re

[Wireshark-dev] [PATCH] update wiretap and sub dissector

hello, the attached patch update the usb dissector and wiretap to sync with current libpcap for usb sniffing. The data link type for usb capture has been changed (and is now DLT_USB_LINUX 189). Each usb 'packet' is preceded by a linux specific header in host byte order. The usb data and usb heade