Re: [Wireshark-dev] Problems with usb capture

2006-10-14 Thread Joerg Mayer
On Sun, Oct 15, 2006 at 12:09:35AM +0200, Joerg Mayer wrote: > I've just updated my libcap to cvs head and managed to capture some > frames with wireshark/tshark. For some reason not clear to me, I get the > following message: ... > [EMAIL PROTECTED]:~/work/wireshark/infos/usb> tshark -V -r mouse_r

[Wireshark-dev] Problems with usb capture

2006-10-14 Thread Joerg Mayer
Hello, I've just updated my libcap to cvs head and managed to capture some frames with wireshark/tshark. For some reason not clear to me, I get the following message: egg:~ # tshark -x -i usb4 Capturing on usb bus number 4 0.00 -> UNKNOWN WTAP_ENCAP = 0 00

Re: [Wireshark-dev] [PATCH] USB setup hdr

2006-10-14 Thread ronnie sahlberg
Hi Paolo. Nice work! In the example capture unplug_mouse2.cap it appears that the timestamp for the packet is not generated properly. All packets show up as JAN 1 1970. 1, Can you have a look at the timestamp generation of packets when capturing. 2, Can you provide some more example captures w

Re: [Wireshark-dev] [PATCH] plugins/rdm: Update to ANSI E1.20-2006

2006-10-14 Thread Shaun Jackman
On 10/14/06, Jaap Keuter <[EMAIL PROTECTED]> wrote: > On Sat, 14 Oct 2006, Shaun Jackman wrote: ... > > > 2. Please keep the original Wireshark (C) in place and the GPL clause > > > intact. > > > > I removed the section of the licensing information that gave the > > address of the FSF. The address

Re: [Wireshark-dev] [PATCH] plugins/rdm: Update to ANSI E1.20-2006

2006-10-14 Thread Jaap Keuter
On Sat, 14 Oct 2006, Shaun Jackman wrote: > Hello Japp, > > On 10/14/06, Jaap Keuter <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Some remarks: > > 1. The patch doesn't apply cleanly to the HEAD > > Grumble. I'll re-diff. Ok. > > > 2. Please keep the original Wireshark (C) in place and the GPL cla

Re: [Wireshark-dev] [PATCH] plugins/rdm: Update to ANSI E1.20-2006

2006-10-14 Thread Shaun Jackman
On 10/14/06, Shaun Jackman <[EMAIL PROTECTED]> wrote: > Hello Japp, Sorry, Jaap. In haste, I misspelled your name. Cheers, Shaun ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev

Re: [Wireshark-dev] [PATCH] plugins/rdm: Update to ANSI E1.20-2006

2006-10-14 Thread Shaun Jackman
Hello Japp, On 10/14/06, Jaap Keuter <[EMAIL PROTECTED]> wrote: > Hi, > > Some remarks: > 1. The patch doesn't apply cleanly to the HEAD Grumble. I'll re-diff. > 2. Please keep the original Wireshark (C) in place and the GPL clause > intact. I removed the section of the licensing information th

Re: [Wireshark-dev] [PATCH] plugins/rdm: Update to ANSI E1.20-2006

2006-10-14 Thread Jaap Keuter
Hi, Some remarks: 1. The patch doesn't apply cleanly to the HEAD 2. Please keep the original Wireshark (C) in place and the GPL clause intact. 3. Now that it became an ANSI standard it's time to move this plugin to the regular dissectors. Thanx, Jaap On Sat, 14 Oct 2006, Shaun Jackman wrote: >

Re: [Wireshark-dev] [PATCH] plugins/rdm: Update to ANSI E1.20-2006

2006-10-14 Thread Shaun Jackman
On 9/30/06, Shaun Jackman <[EMAIL PROTECTED]> wrote: The RDM protocol has been accepted as ANSI standard E1.20-2006. The following patch updates the decoder to that spec. Please apply. Cheers, Shaun 2006-09-30 Shaun Jackman <[EMAIL PROTECTED]> * plugins/rdm/moduleinfo.h (VERSION): Bu

Re: [Wireshark-dev] Writing a new packet dissector

2006-10-14 Thread Daniel Griscom
At 4:54 PM +0200 10/14/06, Ulf Lamping wrote: >Daniel Griscom wrote: >>> Bit more to the point: What platform are you developing on? Wild guess >>> Win32? >>> >> >> Well, I'm an OS X man by choice, but Wireshark is so much better >> integrated into Windows that I use it there. >> >Because

Re: [Wireshark-dev] Writing a new packet dissector

2006-10-14 Thread Ulf Lamping
Daniel Griscom wrote: >> Bit more to the point: What platform are you developing on? Wild guess >> Win32? >> > > Well, I'm an OS X man by choice, but Wireshark is so much better > integrated into Windows that I use it there. > Because I'm using Windows and (I often feel that I'm the only o

Re: [Wireshark-dev] Cygwin Bash update breaks verify_tools

2006-10-14 Thread Bill Meier
> Jacques, Olivier (OpenCall Test Infra) wrote: > > Hello list, > > > > I created a bug (1162) for that, as I had exactly the same issue and > > don't know either how to have a satisfactory solution. > > http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1162 > > > > Olivier. > > > I had the sa

Re: [Wireshark-dev] The empty "Tools" menu toplevel item must be removed before the next release

2006-10-14 Thread LEGO
The menu is there just when compiled with Lua, and the current init.lua adds one item for it. Howhever it would be nice to keep it hidden until it gets populated (I'll take a look at it soon). A second item for that menu (DTD generator), is coming, a tool that parses xml and adds the fields prese

Re: [Wireshark-dev] Writing a new packet dissector

2006-10-14 Thread Anders Broman
Hi, Below is an example on how to register your dissector in the media_type dissector table: void proto_reg_handoff_foo(void) { dissector_handle_t foo_handle; dissector_handle_t application_foo_handle; foo_handle = create_dissector_handle(dissect_foo, proto_foo); application_foo_handle =

Re: [Wireshark-dev] Writing a new packet dissector

2006-10-14 Thread Daniel Griscom
At 10:46 AM +0200 10/14/06, Jaap Keuter wrote: >Hi, > >Oke, here it goes: RTFM's at www.wireshark.org Yes, I've already spent quite a while going over the user and developer documentation. I've also already downloaded and sniffed around the source. End result: little detailed enlightenment. >Bi

[Wireshark-dev] The empty "Tools" menu toplevel item must be removed before the next release

2006-10-14 Thread Ulf Lamping
Hi List! Currently, the "Tools" top level menu item is empty. When I understand this correct, if a lua script is available it will be put into this menu item. IN IT'S CURRENT STATE, IT SHOULD BE REMOVED - at least when it's empty. Having an empty menu item that no one can use (except for it's

Re: [Wireshark-dev] Writing a new packet dissector

2006-10-14 Thread Jaap Keuter
Hi, Oke, here it goes: RTFM's at www.wireshark.org Bit more to the point: What platform are you developing on? Wild guess Win32? Then look into the Wireshark Developer Guide, which has the step by step guide of setting up the build environment. With all that in place check out doc/README.develope

Re: [Wireshark-dev] protocol on top of SUA layer

2006-10-14 Thread Michael Tuexen
All protocol which register for an sccp.ssn. Using grep sccp.ssn *.c in epan/packets/ tcap, bssap, ranap, rnsap, and sccpmg. Best regards Michael On Oct 13, 2006, at 9:54 AM, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> wrote: > Hi , > > I'm trying to write a dissector for a protocol which runs at