Re: [Wireshark-dev] [External] Re: Problem building a dissector for 2.6

e.g for my cnad plugin. add_plugin_library(cnad epan) target_link_libraries(cnad epan) install_plugin(cnad epan) Thanks for the help Andy Ling --- This email has been scanned for email related threats and delive

Re: [Wireshark-dev] [External] Re: Problem building a dissector for 2.6

Yes, I've built the preparation project and it didn't generate any errors. I haven't installed Asciidocotorj, but nothing moaned about missing tools and I didn't notice mention of it in the build instructions (I probably didn't look hard enough). I will investigate tom

Re: [Wireshark-dev] [External] Re: Problem building a dissector for 2.6

quot; -> no files found. So it looks like the user guide didn’t get built. What do I need to do to fix this. Also I’m guessing the custom_plugins.txt format has changed. Is something like this correct? File "${STAGING_DIR}\plugins\${VERSION_MAJOR}.${VERSION_MINOR}\foo\foo.dll" T

Re: [Wireshark-dev] [External] Re: Problem building a dissector for 2.6

to be in a sub directory of plugins. Is that right? Regards Andy Ling From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Graham Bloice Sent: Mon 21 May 2018 16:37 To: Developer support list for Wireshark Subject: [External] Re: [Wireshark-dev] Problem building a

[Wireshark-dev] Problem building a dissector for 2.6

CMakeLists.txt file. This now builds the dissector, but I get a link error saying unresolved symbol sprintf (which is used in my dissector). I'm using Visual Studio 2015 So what do I need to do to make the custom cmake list work and how do I fix the link error. Thanks for any help Regards Andy

Re: [Wireshark-dev] Building CORBA dissectors

\omniORB-4.1.6\bin\x86_win32\omniidl.exe -p C:\wireshark-2.2.5\tools -b wireshark_be myCorba.idl > packet-myCorba.c HTH Andy Ling From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Michael Mann Sent: Mon 26 June 2017 13:17 To: wireshark-dev@wireshark.org Subject:

Re: [Wireshark-dev] Default enabled dissectors

things like the news and readme files. Thanks Andy Ling --- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com

Re: [Wireshark-dev] Default enabled dissectors

ark. Which is a per user folder. So how do I customise the contents of this file such that it gets copied there as part of the installation? Thanks for the help Andy Ling --- This email has been scanned for email

Re: [Wireshark-dev] Default enabled dissectors

doing this. Regards Andy Ling --- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mi

[Wireshark-dev] Default enabled dissectors

with other similar ones. So I'd like to turn those off by default in our installer. Thanks for any help Andy Ling --- This email has been scanned for email related threats and delivered safely by Mimecast

Re: [Wireshark-dev] Submitting a change to fix GIOP request reply association

OK, I’ve finally managed to make it work and I think I have submitted the change. Thanks Andy Ling From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Graham Bloice Sent: Thu 05 November 2015 14:05 To: Developer support list for Wireshark

Re: [Wireshark-dev] Submitting a change to fix GIOP request reply association

ory does have a .ssh directory and it contains github_rsa & github_rsa.pub, which I assume are the keys. Regards Andy Ling From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Graham Bloice Sent: Thu 05 November 2015 13:23 To: Developer

[Wireshark-dev] Submitting a change to fix GIOP request reply association

report and attached the change, but it looks like this has all changed. So what is the easiest way to submit this change? I had a quick look at the git gerrit stuff and it looks like quite a hill to climb just for a one off submission. Thanks for any advice. Andy Ling

[Wireshark-dev] Building 2.0.0rc_2

\build-win32\docbook\developer_guide_docbook.vcxproj" (default target) (90) -> C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(170,5): error MSB6006: "cmd.exe" exited with code 9009. [D:\wireshark-2.0.0rc2\build-win32\docbook\developer

Re: [Wireshark-dev] 2.0_rc2 - was GIOP dissector reply decode

icon on the taskbar and selecting move that I could get it on screen. This maybe because I am “upgrading” from 1.12. But something should really be checking the position is somewhere visible. Regards Andy Ling From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun

Re: [Wireshark-dev] GIOP dissector reply decode

e destination address, not the source. The initial request stores the source IP & port. So I would have thought the reply would have a destination IP & port to match, but it seems I have to use the source IP and destination port. Any id

Re: [Wireshark-dev] GIOP dissector reply decode

ched for. I assume this information is the src/dst/srcport/dstport entries in the packet_info structure. Any thoughts? Does this look like the way forward. Thanks for any help Regards Andy Ling From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf O

Re: [Wireshark-dev] GIOP dissector reply decode

d instructions and the first nmake -f Makefile.nmake verify_tools fails with a file win32.mak not found error. So I guess I'm looking at the wrong instructions. Can someone point me at how to build 2.0 for Windows. Thanks Andy Ling ---

[Wireshark-dev] GIOP dissector reply decode

k out what is doing this. So can someone point me in the right direction and maybe give me some clues about where and whether this can be fixed. Regards Andy Ling --- This email has been scanned for email relate

[Wireshark-dev] Disabling update checker

Thanks for any help Andy Ling --- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mi

Re: [Wireshark-dev] Problems creating CORBA dissector

me requests. So some requests and replies always cause this errors, others don't. I haven't been able to work out what is causing this, but is does seem to be a problem with my dissector. If I turn off my dissector the errors go aw

[Wireshark-dev] Problems creating CORBA dissector

oneNumber\000[Malformed Packet] 44 13:56:58.51223510.71.193.18 10.71.193.9 Q_QUENTIN GIOP 1.2 Request, s=64 id=1758785: op=serverIsUp\000 Any idea what I need to do to make this work prop

[Wireshark-dev] Error creating custom giop dissector

newThumbnail_data_int, tvb, *offset-4, 4, get_CDR_long(tvb,offset,stream_is_big_endian, boundary)); This used to work in version 1.6 (the last one I've used). So something got missed in the recent changes. Thanks f

Re: [Wireshark-dev] Modifying custom giop dissector

data = 769 Any ideas what I need to do to fix this. Thanks in advance Andy Ling ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark

Re: [Wireshark-dev] Modifying custom giop dissector

was a way of adding some formatting hints in the IDL comments or something like that. Regards Andy Ling ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: h

Re: [Wireshark-dev] Modifying custom giop dissector

L,HFILL}}, If I change it to FT_UINT64 & BASE_HEX I get an error in the dissector Message: proto.c:3258: failed assertion "hfinfo->type == FT_INT64" Making a similar change to variables that are FT_INT32 seems to work as expected. Thanks for any help Andy Ling _

Re: [Wireshark-dev] Modifying custom giop dissector

; proto_tree_add_int_format_value(tree, > hf_QuentinTimeline_CombinedTrackSegment_portTimecode, tvb, *offset-4, 4, > octet4, "%s", timecodeString(octet4)); > That seems to do the trick (assuming s_octet4 == octet4 or vice versa :-) Thanks Andy Ling __

[Wireshark-dev] Modifying custom giop dissector

f providing a custom function for some of the return results? Thanks for any help Andy Ling ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wiresh

Re: [Wireshark-dev] Problems building on Mac

ilds without a problem. So if that makes in into the next release it looks like it will be fixed. Thanks Andy Ling ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/li

Re: [Wireshark-dev] Problems building on Mac

I've downloaded. Had they been, it would have saved me a lot of trouble. Regards Andy Ling -- This e-mail is intended for the named addressees only. Its contents may be privileged or confidential and should be treated as such. If you are not an intended recipient please notify

Re: [Wireshark-dev] Problems building on Mac

editor and changing this to a file name relative to the package made it all work. Inside Wireshark package.pmdoc the index.xml file needs changing from /Users/gcombs/Development/wireshark/packaging/macosx/COPYING.txt to COPYING.txt Regards Andy Ling -- This e-mail is intended for the n

[Wireshark-dev] Problems building on Mac

cting flat mpkg make: *** [osx-package] Error 1 Not really being a Mac expert, I'm now stuck. So any help would be much appreciated. Regards Andy Ling -- This e-mail is intended for the named addressees only. Its contents may be privileged or confidential and should be treated as such

[Wireshark-dev] Error compiling 0.99.5 for win32

direction from 'int ' NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~3\VC98\BIN\NMAKE.EXE' : return code '0x2' Stop. Can someone point me at what I need to do to fix this. Thanks Andy Ling

Re: [Wireshark-dev] Malformed packets in CORBA protocol plugin

in the capture. OK, I'll accept it should use the reported length. So is this likely to get accepted as an "official" patch? Thanks for the help Andy Ling ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev

Re: [Wireshark-dev] Malformed packets in CORBA protocol plugin

(tvb_length_remaining(tvb, offset) > 0) set_new_alignment(&offset, GIOP_HEADER_SIZE, 8); This stops the offset getting moved past the end of the buffer when there is no more data. Can anyone see any problem with this? Regards Andy Ling ___

Re: [Wireshark-dev] Malformed packets in CORBA protocol plugin

p it trying to add the proto tree if there are no items. Thanks for any help Andy Ling ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev

Re: [Wireshark-dev] Malformed packets in CORBA protocol plugin

o items expected. > > See, for example, genOperationRequest() in wireshark_gen.py; it could, > for example, start out by setting a flag to false and, before the > self.getCDR3() call, if the flag is false, put out the > start_dissecting() call and set the flag to true, so that

Re: [Wireshark-dev] Malformed packets in CORBA protocol plugin

dissector source from the CORBA idl. This is outside my experience. I also don't understand the detail of the wireshark code to know the best way to fix this problem. So what is the best way to move forward on this? Regards Andy Ling ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev

Re: [Wireshark-dev] Malformed packets in CORBA protocol plugin

ents will show up. > True. > I would, instead, have start_dissecting() take a gboolean argument > indicating whether the are any arguments to be dissected and, if so, > have it return after setting the protocol column. Now it's getting beyond my abilities with python etc. I'm not sure if omniidl and the python back-end can detect methods with & without arguments to call start_dissecting correctly. Which is why I'm asking for some help ;-) Thanks for the input Andy Ling ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev

Re: [Wireshark-dev] Malformed packets in CORBA protocol plugin

is dissector yet. So leave it as is from the GIOP dissector. * TODO: add something useful to COL_INFO * if (check_col(pinfo->cinfo, COL_INFO)) * col_clear(pinfo->cinfo, COL_INFO); */ +if (tvb_length_remaining(tvb, *offset) < 0) + return NULL ;

Re: [Wireshark-dev] Malformed packets in CORBA protocol plugin

For the case where it throws *length = -1 I now need someone who undall this code to advise the best place to fix it. I guess the dissector shouldn't add a tree item if there are no arguments, but that requires changes to the python that generates that file. Thanks for any help Andy Ling __

Re: [Wireshark-dev] Malformed packets in CORBA protocol plugin

ssage? I can't see anything in my dissector, so is it done by the cleanup call or something later on? Any help greatfully received Andy Ling [EMAIL PROTECTED] wrote on 07/12/2006 12:52:43: > Hi, > Perhaps a fault in the GIOP dissector. Can you send the text output of > the failed d

Re: [Wireshark-dev] Malformed packets in CORBA protocol plugin

filter to giop then the info in the main window looks like :- Q_QUENTINV3 GIOP 1.2 Request 236: getRefTime[Malformed Packet] Without the giop filter the "[Malformed Packet]" string is missing Regards Andy Ling ___ Wireshark-dev mailing list

[Wireshark-dev] Malformed packets in CORBA protocol plugin

then no packets show errors. I'm using version 0.99.3a on Win2K Thanks for any help Andy Ling ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev