Re: [Wireshark-dev] --with-ssl action when gnutls is not found

2007-07-10 Thread Andrew Hood
Guy Harris wrote: At least one of the reasons why we might need -lcrypto is that we use NetSNMP to get information about particular SNMP variable bindings. So why not use libsmi instead? It has no reliance on any external libraries. The only disadvantage is that it is more picky than

Re: [Wireshark-dev] TCP Reassembly issues

2007-07-10 Thread ronnie sahlberg
On 7/10/07, Graham Bloice [EMAIL PROTECTED] wrote: DNP application message fragments are carried in a transport layer which has a single byte header containing a 6 bit sequence number (tr_seq, 0-63) and two flags, first (tr_fir) and final (tr_fin). A single fragment message will have both

[Wireshark-dev] wireshark dissector and GPL

2007-07-10 Thread MKS {}
Hi, In case I write a wireshark dissector for a protocol I have developed and then attempt to sell the dissector, am I required to share the code of the dissector with the General Public under GPL? Thanks, --MK Missed the show?  Watch videos of the Live Earth Concert on MSN.

Re: [Wireshark-dev] how to disable dissectors when I build TShark ?

2007-07-10 Thread Jean-Grégoire Foulon
On 7/5/07, Shehjar Tikoo [EMAIL PROTECTED] wrote: Jean-Grégoire Foulon wrote: I just managed to have a lib 50% smaller by removing some protocols. I will try to post a diff file here (or somewhere else) when I have a satisfying result. I think it can be useful for people trying to get a

Re: [Wireshark-dev] size of wireshark installation files

2007-07-10 Thread Sebastien Tandel
HOW TO REMOVE DISSECTORS First, modify some files so the unwanted dissectors won't be compiled anymore: Makefile.in http://Makefile.in epan/Makefile.in epan/dissectors/Makefile.in You must choose the unwanted dissectors so that they were no dependencies

Re: [Wireshark-dev] wireshark dissector and GPL

2007-07-10 Thread Abhik Sarkar
Hi, Something similar was discussed in this thread: http://www.wireshark.org/lists/wireshark-dev/200701/msg00708.html The short answer is 'yes'. Best regards, Abhik. On 7/10/07, MKS {} [EMAIL PROTECTED] wrote: Hi, In case I write a wireshark dissector for a protocol I have developed and

[Wireshark-dev] filters diameter

2007-07-10 Thread cco
hi! has anyone tested a filter like this: (diameter.avp.code == 829) (diameter.avp.data.uint32 == 1) is it suppossed to work? is it actually working in your config/ver? in my version, it does not in the sense that it will always show all the diameter commands having an avp with the code 829

Re: [Wireshark-dev] filters diameter

2007-07-10 Thread Martin Mathieson
That expression will match any frame that has at least one avp with code value 829 and at least one avp whose data is uint32 whose value is 1. I suspect that what you want is to match the *same* AVP with both parts of the expression, which I don't think is possible with a simple display filter.

Re: [Wireshark-dev] filters diameter

2007-07-10 Thread Abhik Sarkar
Hi Christian, As you are probably aware, version 0.99.6 came out a few days back which I am sure has several fixes, including those for the diameter dissector. Have you tried using the latest version? Hope this helps, Abhik. On 7/10/07, cco [EMAIL PROTECTED] wrote: hi! has anyone tested a

Re: [Wireshark-dev] filters diameter

2007-07-10 Thread Martin Mathieson
There are several ways this could be tackled: (1) A script. Export capture to PDML, parse output and match/check them yourself (2) We could add a new filterable field, diameter.avp, whose type was hex data. You could right-click to create a filter for that AVP, then edit the last word to check

Re: [Wireshark-dev] size of wireshark installation files

2007-07-10 Thread Jaap Keuter
Hi, Should we make dissector_add() and friends fail silently when the referenced dissector is not available? Currently the g_assert() is killing, while a return would suffice. This becomes more relevant since we can delete a dissector on the fly, so we may run into this assert while not

Re: [Wireshark-dev] New WiMAX R6 plug-in

2007-07-10 Thread Jaap Keuter
Hi, First thing to so it testdrive it using fuzztest. Have a collection of capture files ready which fuzztest will feed to your Wireshark+plugin. That way you may find bugs not found during code review. Then make sure all support files are in as stated in README.plugin. Then 'make clean' the

Re: [Wireshark-dev] filters diameter

2007-07-10 Thread Martin Mathieson
OK, I just implemented (2) with change 22284. You should be able to right-click on a whole AVP that matches the code you're interested in, choose 'Prepare as Filter | Selected', edit the last 4 bytes and apply it. Martin On 7/10/07, Martin Mathieson [EMAIL PROTECTED] wrote: There are several

Re: [Wireshark-dev] filters diameter

2007-07-10 Thread Luis EG Ontanon
A year or more ago I abandoned a way towards (3) (similar to what I did for radius dictionary) a while ago, due to a personal lack of diameter use after switching jobs and a stall about how to handle recursion in attribute_groups. I will be able to get back into it in September (I'll be

Re: [Wireshark-dev] capturing data from a propietary device

2007-07-10 Thread Ulf Lamping
[EMAIL PROTECTED] schrieb: I'm trying to figure out how to format (or where to place the data) in the pcap buffer when capturing my WAN protocols. I've built a system that will capture the data and feed it via pcap to wireshark, and I've got it working for Ethernet data and for frame relay

[Wireshark-dev] accessing tcp data

2007-07-10 Thread Michael Ngo
Hi all I'm currently writing a wireshark dissector and I'm stuck at a certain stage. My problem basically is that I need to access the tcp information for particular frames (ex: first frame). When I say tcp information I am referring to the tcp flags. Any help would be appreciated. Thanks. Mike

[Wireshark-dev] Fwd: accessing tcp data

2007-07-10 Thread Michael Ngo
Sorry for the double email, but I forgot to mention that the problem stems from frames that contain only the IP and TCP information, thus causing my dissect_XXX function to not be called, where XXX is the name of my protocol. Note: forwarded message attached.

Re: [Wireshark-dev] capturing data from a propietary device

2007-07-10 Thread Guy Harris
On Jul 10, 2007, at 2:17 PM, [EMAIL PROTECTED] wrote: Yes, I did, and I am in theory following it. The difference is that the document refers to the 'file format' and not the live stream, so the global header is not applicable. This information is (somehow) exchanged in a different

Re: [Wireshark-dev] capturing data from a propietary device

2007-07-10 Thread Ulf Lamping
[EMAIL PROTECTED] schrieb: Did you noticed http://wiki.wireshark.org/Development/LibpcapFileFormat? Yes, I did, and I am in theory following it. The difference is that the document refers to the 'file format' and not the live stream, so the global header is not applicable. This

Re: [Wireshark-dev] Python wrappers for pcapio.[ch]

2007-07-10 Thread Guy Harris
On Jul 10, 2007, at 6:08 PM, Shehjar Tikoo wrote: Does anyone know of Python bindings for the pcapio.[ch] code in Wireshark source root? I am looking for Python wrappers for writing pcap files and I havent been able to find a library that does it or does it cleanly. Shehjar PS: I ask

[Wireshark-dev] variable TCP port in plugin

2007-07-10 Thread Rahul Ruikar
Hi, I am working on plugin which will decode TCP based protocol. my problem is port of that protocol is variable one.. I want it to configure it before decoding ..How can i do that in plugin..? -- Rahul Ruikar ___ Wireshark-dev mailing list

Re: [Wireshark-dev] variable TCP port in plugin

2007-07-10 Thread Stephen Fisher
On Wed, Jul 11, 2007 at 09:52:34AM +0530, Rahul Ruikar wrote: I am working on plugin which will decode TCP based protocol. my problem is port of that protocol is variable one.. I want it to configure it before decoding ..How can i do that in plugin..? There are various dissectors that have