Re: [Wireshark-dev] Alternatives to atoi and tolower

Hi Paul, 2017-07-07 10:03 GMT+02:00 Paul Offord : > Hi, > > A petri dish run against code I submitted failed with: > > > > Error: Found prohibited APIs in plugins/syncro/packet-syncro.c: > atoi,sprintf > > Error: Found prohibited APIs in plugins/syncro/syncroparser.c:

Re: [Wireshark-dev] Visual Studio 2013/2015/2017 compatibility and libraries

Hi Peter 2017-04-24 15:43 GMT+02:00 Peter Wu : > Hi, > > Are there possible issues to be aware of when using the libraries (built > with mingw/msvc2013) with the Wireshark binaries built with VS2017? > When trying it with a friend, it seems to build and run with no issues. >

Re: [Wireshark-dev] Visual Studio 2013/2015/2017 compatibility and libraries

2017-04-24 16:25 GMT+02:00 Graham Bloice <graham.blo...@trihedral.com>: > > > On 24 April 2017 at 14:56, Pascal Quantin <pascal.quan...@gmail.com> > wrote: > >> Hi Peter >> >> 2017-04-24 15:43 GMT+02:00 Peter Wu <pe...@lekensteyn.nl>: >&

Re: [Wireshark-dev] Visual Studio 2013/2015/2017 compatibility and libraries

2017-04-24 16:15 GMT+02:00 Peter Wu <pe...@lekensteyn.nl>: > On Mon, Apr 24, 2017 at 03:56:14PM +0200, Pascal Quantin wrote: > > Hi Peter > > > > 2017-04-24 15:43 GMT+02:00 Peter Wu <pe...@lekensteyn.nl>: > > > > > Hi, > > > > > >

Re: [Wireshark-dev] G729

Hi Dario, Le 5 août 2017 18:33, "Dario Lombardo" a écrit : I've noticed that cmake shows me -- The following OPTIONAL packages have not been found: * BCG729 , G.729 decoder , Support for G.729 codec

Re: [Wireshark-dev] LNK2019: unresolved external symbol proto_deregister_protocol

Hi Paul, 2017-07-28 19:34 GMT+02:00 Paul Offord : > Hi, > > > > I’d like to use the function proto_deregister_protocol in a dissector. > The problem is that when I build the dissector I get: > > > > packet-bds.obj : error LNK2019: unresolved external symbol >

Re: [Wireshark-dev] Including Qt5 libs in my plugin project

Hi Paul, 2017-06-24 21:48 GMT+02:00 Paul Offord : > I’m using VS 2013 on Windows 10 to build a plugin that uses Qt5 classes. > Currently I manually add the paths to the libraries I need to the Linker > Input parameters via VS like this: > > > >

Re: [Wireshark-dev] Pulling code from Gerrit

Hi Paul, 2017-06-24 18:13 GMT+02:00 Paul Offord : > Hi, > > > > I’m working on the Syncro plugin code – see https://code.wireshark.org/ > review/#/c/19666/ . Since I submitted the original code to Gerrit I have > switched to developing on a Windows 10 VM. I want to

Re: [Wireshark-dev] git problem

Hi Paul, Le 25 juin 2017 12:59, "Paul Offord" a écrit : I am trying to upload some patches to Gerrit. The start of my commit message looks like this: [WIP] First stage of updates to Syncro This patch set deals with several of the issues raised by Roland Knall

Re: [Wireshark-dev] packet-lorawan.c compile error because of stuff added yesterday ...

2017-06-13 22:33 GMT+02:00 Pascal Quantin <pascal.quan...@gmail.com>: > Hi Richard, > > 2017-06-13 22:29 GMT+02:00 Richard Sharpe <realrichardsha...@gmail.com>: > >> Hi folks, >> >> After I did a git pull, I started getting this error: >> >

Re: [Wireshark-dev] packet-lorawan.c compile error because of stuff added yesterday ...

Hi Richard, 2017-06-13 22:29 GMT+02:00 Richard Sharpe : > Hi folks, > > After I did a git pull, I started getting this error: > > CC packet-lorawan.lo > packet-lorawan.c: In function 'dissect_lorawan': > packet-lorawan.c:657:7: error: variable 'frame_length'

Re: [Wireshark-dev] Go to Qt 5.9 on Windows build bots?

Hi Anders, Le 14 juin 2017 13:49, "Anders Broman" a écrit : Hi, Should we go to Qt 5.9 on the build bots before SharkFest? I have used t without noticing any problems. Given that it's the new LTS, it probably makes sense. master-2.0 and master-2.2 should stay on

Re: [Wireshark-dev] Add a protocol to the "decode as" option

Hi Juan Jose, 2017-09-18 16:21 GMT+02:00 Juan Jose Martin Carrascosa : > Hi everybody, > > I have a set of plugins that work on top of the RTPS protocol. Which is > the cleanest and right way to get this set of plugins available when I > click in "decode as" in a RTPS packet? >

Re: [Wireshark-dev] Best way to give configuration information to a protocol

Hi Juan Jose, 2017-09-18 17:12 GMT+02:00 Juan Jose Martin Carrascosa : > Hi all, > > Which is the best way to pass configuration to a protocol? Do we have any > builtin mechanisms? I tried to upload a patch using CSV at some point but > it didn't succeed. So I wonder if there is

Re: [Wireshark-dev] Novice: Where do I place my own C dissector in Visual Studio 2015? Is it easy?

Hi Christopher, 2017-09-20 17:42 GMT+02:00 : > > > By following the instructions in the Wireshark Developer’s Guide Under > Section 2.2. Win32/64: Step-by-Step Guide, I have been able to create and > run Wireshark in Visual Studio 2015. I can load a capture

Re: [Wireshark-dev] Tips regarding measuring function execution times

2017-10-15 22:40 GMT+02:00 João Valverde : > > > On 15-10-2017 21:32, Peter Wu wrote: > >> On Sat, Oct 14, 2017 at 02:18:39PM +, Paul Offord wrote: >> >>> I'm investigating a performance problem with the TRANSUM dissector. I'd >>> like to measure the

Re: [Wireshark-dev] XXXX: avoid appending xxxx multiple times to frame.protocols field

Hi Guy, Le 5 oct. 2017 23:20, "Guy Harris" a écrit : A given frame's dissection can have multiple packets for a given protocol, if, at any protocol layer, a PDU can contain multiple PDUs for the next layer above it (or parts of multiple PDUs, as with byte-stream protocols

Re: [Wireshark-dev] XXXX: avoid appending xxxx multiple times to frame.protocols field

https://code.wireshark.org/review/19464 > On Fri, Oct 6, 2017 at 7:01 AM, Pascal Quantin <pascal.quan...@gmail.com> > wrote: > >> Hi Guy, >> >> Le 5 oct. 2017 23:20, "Guy Harris" <g...@alum.mit.edu> a écrit : >> >> A given frame's dissec

Re: [Wireshark-dev] How to use Wireshark dissectors and header fields? (looking for "WORKING" examples for windows)

Hi Christopher, there are several ways of writing a Wireshark dissector (using C or Lua for example). It's up to you to decide which one is the most comfortable for you. I highly encourage you to read the Sharkfest presentation 'Writing a dissector: 3 ways to eat bytes' done by Graham Bloice. The

[Wireshark-dev] Favoring Npcap over WinPcap at runtime?

Hi list, when we introduced Npcap support back in 2015/2016, we decided that WinPcap driver should have higher precedence due to its known stability (and despite issues with newer Windows versions). By that time, you could get a BSoD with Npcap. Time has elapsed since, and Npcap is now bundled

Re: [Wireshark-dev] Favoring Npcap over WinPcap at runtime?

2017-10-18 11:54 GMT+02:00 Graham Bloice <graham.blo...@trihedral.com>: > > > On 18 October 2017 at 09:45, Pascal Quantin <pascal.quan...@gmail.com> > wrote: > >> Hi list, >> >> when we introduced Npcap support back in 2015/2016, we decided that >&g

Re: [Wireshark-dev] Iperf dissector for wireshark

Hi, 2017-11-26 8:14 GMT+01:00 Ashhad Mohammed via Wireshark-dev < wireshark-dev@wireshark.org>: > Hi, > > I am trying to include iperf plugin for wireshark but having difficulty to > do so. > Do you already have a exe file that I can just install and use the iperf > plugin? > > Pls assist. >

Re: [Wireshark-dev] Processing packet before exporting it.

Hi Manik, Le 22 nov. 2017 16:39, "Manik Khandelwal" a écrit : Hi all, I want to process a dissected packet before *exporting *it as an hex file in wireshark but I am not able to find where to start from. Can someone help me out with this problem? As Guy already

Re: [Wireshark-dev] Processing packet before exporting it.

nges to that hex file. > Is there some way I can achieve this using wireshark or the answer is *no* > ? > Again, the answer is no. R, Pascal. > Regards, > Manik Khandelwal > > On Wed, Nov 22, 2017 at 9:13 PM, Pascal Quantin <pascal.quan...@gmail.com> > wrote: > >&

Re: [Wireshark-dev] Processing packet before exporting it.

Le 22 nov. 2017 17:36, "Dario Lombardo" a écrit : On Wed, Nov 22, 2017 at 5:21 PM, Manik Khandelwal < manik123khandel...@gmail.com> wrote: > I want to edit the bytes with full knowledge of structure. > > There was such a feature in wireshark GTK gui. It has not been

Re: [Wireshark-dev] reduce tshark memory usage

Hi, 2017-11-22 17:32 GMT+01:00 杜 伟强 : > Hello > > I start up a tshark process and print some usefull message into my > database. > > But as times goes on ,the memory usage of tshark has been grown so big. > > And I find here are some word to explain this phenomenology

Re: [Wireshark-dev] Making zlib a required dependency

Hi João, 2017-11-11 16:04 GMT+01:00 João Valverde : > I pushed a change making zlib 1.2.3 or greater a required build dependency: > > https://code.wireshark.org/review/#/c/24352/1 > Why this change? Is it because you fear we might not test the conditional

Re: [Wireshark-dev] rpcap support seems to have disappeared ...

Le 11 nov. 2017 17:15, "Richard Sharpe" <realrichardsha...@gmail.com> a écrit : On Sat, Nov 11, 2017 at 7:50 AM, Pascal Quantin <pascal.quan...@gmail.com> wrote: > Hi Richard, > > 2017-11-11 16:45 GMT+01:00 Richard Sharpe <realrichardsha...@gmail.com>: >&g

Re: [Wireshark-dev] rpcap support seems to have disappeared ...

Hi Richard, 2017-11-11 16:45 GMT+01:00 Richard Sharpe : > Hi folks, > > I am hearing from one user that they could no longer use rpcap from > 2.0.2 of Wireshark, and I see that while I can enable it in configure > (--with-remote-pcap) it does not seem to show up in

Re: [Wireshark-dev] Make Qt required in CMake.

Hi Graham, 2017-11-14 15:57 GMT+01:00 Graham Bloice : > Yet another question on Ask today (https://ask.wireshark.org/ > question/339/getting-error-msb4018-when-trying-to-build- > wireshark-sources/?answer=343#post-id-343) about getting a build error > because Qt

Re: [Wireshark-dev] g_free throwing an exception

Hi Paul, 2017-11-05 12:15 GMT+01:00 Paul Offord : > Hi, > > > > I am working on a plugin dissector. It works OK except when I change > profiles Wireshark throws an exception in code in proto.c as follows: > > > > static void > > free_deregistered_field (gpointer data,

Re: [Wireshark-dev] Protocol tree - indicating a missing value

Hi Paul, 2017-11-02 10:17 GMT+01:00 Paul Offord : > Hi, > > > > Is it possible to add an item to the protocol tree but indicate in some > way that the value for the field is missing? I want to produce something > like this: > > > > Frame 13: 155 bytes on wire (1240

Re: [Wireshark-dev] tshark: export to pdml improvements

Hi Pavel, Le 2 déc. 2017 16:45, "Pavel Strnad" a écrit : Hi list, I am proposing following pdml export improvements: 1) fix for bug introduced in 2.4 in SHA-1:b8ead953758304 where level incrementing was missed in the fake protocol wrapper and due to that level is getting

Re: [Wireshark-dev] Wireshark configure issue

Hi Manik, 2017-10-25 16:54 GMT+02:00 Manik Khandelwal : > Hello all, > While building wireshark on Ubuntu 16.04, I successfully generated > configure file. Unfortunately encountered the following error: > > *checking for LIBGCRYPT - version >= 1.4.2... no* > >

Re: [Wireshark-dev] Info column with multiple PDUs in one frame

Hi Thomas, 2017-10-25 21:02 GMT+02:00 Thomas Wiens : > On 25.10.2017 18:36, Jeff Morriss wrote: > > > Typically how multiple PDUs are handled is by setting a "fence" in the > INFO > > column. Calling col_clear() only clears as far back as the fence; this > > allows upper-layer

Re: [Wireshark-dev] asn2wrs: autodetection for 64 bits X constrained integers

Hi Pavel, 2017-10-25 8:34 GMT+02:00 Pavel Strnad : > Hi list, > can we improve auto detection for 64b variant of constrained integers? > In the master branch we handle the cases of integers over/under +/- 2^32 > but > what about MIX.. and ..MAX constants? > There are such

Re: [Wireshark-dev] extcaps not showing up under windows

Hi Dirk, Le mer. 23 mai 2018 à 09:24, Dirk Eibach a écrit : > I have successfully setup a windows build-environment and did a wireshark > build. > It starts up successfully and the pcap-interfaces show up. But I > cannot get any extcap-interfaces. > Checking the extcap

Re: [Wireshark-dev] Push failed after amend (Change 27518)

Hi David, Le lun. 11 juin 2018 à 09:29, a écrit : > > > I still have to learn a lot. I’ve got a pending review, so I’ve updated my > code, amended as I thought I needed to, and tried to push once more (as I > did last time except the last push did not have the author populated). > > > > However

Re: [Wireshark-dev] Push failed after amend (Change 27518)

ebase -I HEAD~2 (any a few others). That seems to work, but > not the subsequent push. I’ve attached a log if that helps. > > > > Regards > > David > > > > > > *From:* Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] *On > Behalf O

Re: [Wireshark-dev] Sometimes SLL/Linux cooked-mode capture is decoded and sometimes its not (difference between two packets?)

Hi Michael, Le jeu. 7 juin 2018 à 23:32, Michael Lum a écrit : > Hi, > > I've attached two captures with a single packet in each. > > They are both supposed to be syslog events injected into the capture with > SLL (Linux cooked capture). > > On one everthing is decoded as expected in the other

Re: [Wireshark-dev] 2.5.0 release on January 16

Hi Anders, 2018-01-18 18:23 GMT+01:00 Anders Broman : > > > Den 17 jan. 2018 8:37 em skrev "Stig Bjørlykke" : > > On Wed, Jan 17, 2018 at 2:05 AM, Gerald Combs > wrote: > > On 1/13/18 4:16 AM, Stig Bjørlykke wrote: > >> - Qt:

Re: [Wireshark-dev] bug found in dissector u3v

Hi Rene, Le 10 janv. 2018 09:25, "Weber René" a écrit : Hi, I have found a little issue in packet-u3v.c – is there someone interested ? to generate the gencp_transaction_t record is req_id as key used – but the req_id exists twice : 1. For cmd – ack from host to

Re: [Wireshark-dev] Does tshark use the preferences that you have established with Wireshark?

Hi Richard, Le 12 janv. 2018 19:28, "Richard Sharpe" a écrit : Hi Folks, Does tshark use your Wireshark preferences as well? Yes it uses your default profile unless you specify another one using the command line. Cheers, Pascal.

Re: [Wireshark-dev] report from the bleeding edge (VS 2017)

2018-02-14 11:24 GMT+01:00 Graham Bloice <graham.blo...@trihedral.com>: > > > On 14 February 2018 at 06:24, Anders Broman <a.broma...@gmail.com> wrote: > >> >> >> Den 14 feb. 2018 6:58 fm skrev "Pascal Quantin" <pascal.quan...@gmail.com

Re: [Wireshark-dev] report from the bleeding edge (VS 2017)

Le 14 févr. 2018 02:24, "Gerald Combs" a écrit : On 2/13/18 8:26 AM, Anders Broman wrote: > > For what it's worth I have been building and distributing for VS 2017 for almost a year on Win7 > Cygwin and python set up as per developers guide from way back. > I have the

Re: [Wireshark-dev] Regenerate asn dissector

2018-02-19 15:26 GMT+01:00 Dario Lombardo <dario.lombardo...@gmail.com>: > > > On Mon, Feb 19, 2018 at 3:13 PM, Pascal Quantin <pascal.quan...@gmail.com> > wrote: > >> >> As indicated by Alexis, Anders and Graham, CMake should already have >> created

Re: [Wireshark-dev] Regenerate asn dissector

Hi Dario, 2018-02-19 15:04 GMT+01:00 Dario Lombardo : > That's what I needed. I was close to it, but I didn't get the right > starting point for regenerating. > What's missing IMHO is a cmake target for that. Maybe I will take some > time to add one (many, actually).

Re: [Wireshark-dev] (no subject)

Hi Ralf, You patch is under review in Gerrit: https://code.wireshark.org/review/29147 You did not get it with a fresh clone because it has not gone through the review process test and has not been merged in the repository. Best regards, Pascal. Le mer. 15 août 2018 à 10:24, Nasilowski, Ralf a

Re: [Wireshark-dev] Cannot push patch to Gerrit - Found WIP commit

Hi Dario, Le jeu. 6 sept. 2018 à 09:08, Dario Lombardo a écrit : > Maybe this is not related, but shouldn't it be refs/for/master/ ? > The topic is optional. BR, Pascal. > On Wed, Sep 5, 2018 at 5:39 PM Andrii Vladyka wrote: > >> I am trying to push a patch (single commit on top of the

Re: [Wireshark-dev] Dissector H.265 : when it will be available

Hi Asaf, master branch corresponds to the upcoming Wireshark 3.0 version (while all the 2.6.x versions come from the master-2.6 branch). Based on https://www.wireshark.org/lists/wireshark-dev/201802/msg00012.html it should be out around November. Best regards, Pascal. Le mar. 4 sept. 2018 à

Re: [Wireshark-dev] Lua update?

Le jeu. 12 juil. 2018 à 20:44, Pascal Quantin a écrit : > Hi Chris, > > Le jeu. 12 juil. 2018 à 20:30, Maynard, Chris > a écrit : > >> Is there any particular reason why Wireshark for Windows still ships with >> Lua 5.2.4? An upgrade to 5.3+ would be a welcome one. &

Re: [Wireshark-dev] Lua update?

Hi Chris, Le jeu. 12 juil. 2018 à 20:30, Maynard, Chris a écrit : > Is there any particular reason why Wireshark for Windows still ships with > Lua 5.2.4? An upgrade to 5.3+ would be a welcome one. > > Thanks. > Can our current code run fine with Lua 5.3/5.4? Based on previous discussions in

Re: [Wireshark-dev] Retrieving dissection result from another dissector

Hi Dario, Le mar. 3 juil. 2018 à 17:11, Dario Lombardo a écrit : > Actually I'm using the blob to pass data from the caller to the called. I > guess it's a design flow to re-use this blob to have data back... > Simply add a parameter to your structure that is used to retrieve the output data

Re: [Wireshark-dev] Retrieving dissection result from another dissector

Le mar. 3 juil. 2018 à 20:57, Richard Sharpe a écrit : > On Tue, Jul 3, 2018 at 11:48 AM, Guy Harris wrote: > > On Jul 3, 2018, at 9:24 AM, Peter Wu wrote: > > > >> Another possibility is to use p_add_proto_data/p_get_proto_data with > packet scope > > > > 1) Presumably you mean pinfo->pool

Re: [Wireshark-dev] Dissector - plugin or built-in

Hi Paul, Le 1 mars 2018 10:47, "Paul Offord" a écrit : Hi Pascal, Thanks for your note regarding my change 26203 - https://code.wireshark.org/ review/#/c/26203/ . You suggested that I submit it as a built-in dissector, not a plugin. I’m not keen for two reasons:

Re: [Wireshark-dev] register_tap_listener memleak

Hi Peter, 2018-03-15 13:24 GMT+01:00 Peter Wu : > Hey Dario, Pascal and others, > > I was looking at memleaks as reported by LSAN while running the > decryption test suite, there are quite a number of occurrences. > > One of them is tap (return value of

Re: [Wireshark-dev] 2.6 branch planning and post-branch changes

Hi Gerald, 2018-03-14 21:41 GMT+01:00 Gerald Combs : > I plan on releasing 2.5.1 tomorrow and I've tentatively scheduled creating > the 2.6 branch on April 2, followed by 2.6.0 on April 18. > > As discussed previously we'll drop support for Qt 4 and GTK+ in the master >

Re: [Wireshark-dev] Error loading plugin

Hi Juanjo, 2018-04-10 14:02 GMT+02:00 Juanjo Martin Carrascosa : > Hi all, > > I am developing a plugin. It works for me but when I try to give it to > other developers, some of them get the following error: > > > > I am using VS2012 in Windows 64 bits and I have asked one of the

[Wireshark-dev] GLib update for Windows

Hi all, With the drop of the GTK UI in master branch, I was thinking about updating the GLib pre compiled libraries we are using on Windows. OpenSUSE currently provides 2.52.2, so I will probably give it a try in the near future. Pascal.

Re: [Wireshark-dev] Extracting filter

Hi Dario, 2018-04-05 8:57 GMT+02:00 Dario Lombardo : > Hi > I need to extract all the display filters to have a list with > > > > example > > dns dns.a6.address_suffix FT_IPv6 > dns dns.a6.prefix_len FT_UINT8 > dns dns.a6.prefix_name FT_STRING > dns dns.

Re: [Wireshark-dev] Overriding a builtin dissector

Hi Jason, 2018-04-25 17:40 GMT+02:00 Jason Cohen : > I've already asked some of this privately, but submitting to the full list > for archival as well. > > Is there a way or any thoughts of being able to override an existing, > built-in dissector? > You can deactivate a

Re: [Wireshark-dev] Bug-13388 - TCP level reassembly bug in 2.x ??

Hi Graham, Le mar. 27 mars 2018 à 18:40, Graham Bloice a écrit : > > > On 27 March 2018 at 16:42, wrote: > >> >> >> I stepped through a DICOM capture multiple times, and the result is a >> little surprising. >> >> I’ve attached an analysis

Re: [Wireshark-dev] Lua Dissector Dev Tool

Hi Markus, 2018-03-28 2:12 GMT+02:00 Markus Leballeux : > Hello Wireshark Devs, > > I am currently working on a lightweight Lua library called Wirebait (here > on GitHub ), which enables users > to execute and step through their

Re: [Wireshark-dev] export_pdu

Hi Dario, Le 17 mars 2018 17:42, "Dario Lombardo" a écrit : To reduce the duplicated code between libwireshark and udpdump I tried to move the export_pdu code from epan to a shared library (as done for writecap and randpkt_core) in this change:

Re: [Wireshark-dev] No Interfaces found issue

Hi, Le dim. 7 oct. 2018 à 09:25, Jaap Keuter a écrit : > HI, > > Little more context, especially Operating System of the platform you’re > building / testing on? > As Jaap explained it would be much easier for us to help you if you posted the content of the Wireshark about dialog window. Best

Re: [Wireshark-dev] No Interfaces found issue

Hi Igor, Le dim. 7 oct. 2018 à 09:36, Igor Chetverovod a écrit : > OS Ubuntu 16.04 LTS on laptop Lenovo B590 Intel Core I3-2348M > As you are running on Linux, you need to set the right privileges for dumpcap to have access to the interfaces. See

Re: [Wireshark-dev] asn2wry.py - showing protocol version ?

Hi Martin, Le mer. 17 oct. 2018 à 21:51, Martin Mathieson via Wireshark-dev < wireshark-dev@wireshark.org> a écrit : > Hi, > > I would like to be able to show, for the generated dissectors, the version > of the protocol. For 3GPP protocols, in theory they are > backwards-compatible, but not at

Re: [Wireshark-dev] Is there a need for a 0, NULL element at the end of value strings

Hi Richard, Le mar. 16 oct. 2018 à 17:26, Richard Sharpe a écrit : > Hi folks, > > I have always put a {0, NULL} element on the end of value strings, but > it seems the lua code for constructing value strings when you use > ProtoField(..., some_value_string) does not terminate the list with an

Re: [Wireshark-dev] Anyone at the Hotel?

Hi Richard, We are out of the restaurant, heading back to the hotel. Le dim. 28 oct. 2018 à 21:32, Richard Sharpe a écrit : > Hi folks, > > Who is at the hotel already? > > Anyone not had dinner yet? > > -- > Regards, > Richard Sharpe > (何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者) >

Re: [Wireshark-dev] Question about asn2wrs

Hi Craig, Le jeu. 8 nov. 2018 à 19:44, Craig Jackson a écrit : > I'm working on a decoder for the NISO Z39.50 protocol. This is an > ASN.1/BER protocol used in the library automation community. > > There some things I'm having trouble figuring out how to configure, and > there are also a bunch

Re: [Wireshark-dev] Wireshark seems to require Python 3.4 or better now ...

Hi Richard, Le sam. 10 nov. 2018 à 18:33, Richard Sharpe a écrit : > Hi folks, > > I am running into problems with building the latest Wireshark master > release on CentOS 7.5.1804. > > Wireshark seems to need Python 3.4 or better, and I have Python 3.6 > installed and am using the software

Re: [Wireshark-dev] What's wrong with %ll ?

Hi Antoine, Le jeu. 15 nov. 2018 à 22:09, Antoine d'Otreppe a écrit : > Hi devs :) > > Small pickle here. Can you enlighten me? Travis clang builds complain > about my format strings not using the right placeholders: > > ``` > ../epan/dissectors/packet-syncthing.c:156:57: error: format

Re: [Wireshark-dev] Decrypt encrypted eapol key data (in 802.11 4-way handshake)

Hi Mikael, Le mer. 7 nov. 2018 à 10:53, Mikael Kanstrup a écrit : > Hi, > > I've started to implement support for decrypting the eapol keydata. With > an early prototype I've been able to successfully decrypt and dissect the > data. Though I run into a problem where I need to access parent

Re: [Wireshark-dev] Question about asn2wrs

I'm not sure what per-packet storage means in that case. I guess it's time > for "Use the Source, Luke". > Per packet seems the right choice. See the s1ap_get_private_data() function in packet-s1ap-template.c for an example. Pascal. > Craig > > On Thu, Nov 8, 2018 at 2:06

Re: [Wireshark-dev] [Wireshark-commits] wireshark-win64-libs rev 533: /trunk/ /trunk/packages/: GeoIP-1.6.10-win64ws.zip GeoIP-1.6.6-win64ws.zip /trunk/: README.txt

Hi Chris, Le mer. 7 nov. 2018 à 17:11, Maynard, Chris a écrit : > I was just curious if the removal of these packages is in prepration for > updated 1.6.12 packages or if GeoIP support is being removed altogether, > and if that's the case, then what might be the reason for that? > we

Re: [Wireshark-dev] Unused dissector headers

Hi Gerald, Le ven. 21 sept. 2018 à 20:13, Gerald Combs a écrit : > We have a bunch of header files in epan/dissectors that are only used > once. Is there any reason we shouldn't move the contents of most of them to > their corresponding .c files? > > file-file.h 20 lines > packet-dcc.h 390

Re: [Wireshark-dev] TRANSUM Enhancements

HI Paul, Le ven. 7 déc. 2018 à 19:40, Paul Offord a écrit : > Hi, > > > > I want to add a couple of enhancements to the TRANSUM plugin. I’ve been > out of the loop for a while and so I need some advice re. development. Are > feature additions still being accepted on Wireshark 2.x branches, or

Re: [Wireshark-dev] TRANSUM Enhancements

d my question; > I should add to master for Wireshark 2. > Master is gonna be Wireshark 3.0 soon. Best regards, Pascal. > Thanks and regards...Paul > > > > Sent from Samsung Mobile on O2 > > > ---- Original message > From: Pascal Quantin > Date: 07/

Re: [Wireshark-dev] Looking for a base32_encode

Hi Antoine, Le jeu. 29 nov. 2018 à 10:26, Antoine d'Otreppe a écrit : > Makes sense. > > I had a look at a few sample implementations, the algorithm looks rather > lengthy and error-prone. What's your policy on including source code from > other open source projects? Which would be the best

Re: [Wireshark-dev] Unhandled exception

Hi Anders, Le mar. 18 sept. 2018 à 10:19, Anders Broman a écrit : > Hi, > I think that the problem is that one of these fields has changed name, but > debugging the registration phase is hard on Windows as the console is not > open...GRR > this seems to be the ssl.record.content_type field. We

Re: [Wireshark-dev] Unhandled exception

https://code.wireshark.org/review/c/29715/ Cheers, Pascal. Le mar. 18 sept. 2018 à 10:22, Pascal Quantin a écrit : > I'm uploading a patch. > > Pascal. > > Le mar. 18 sept. 2018 à 10:20, Pascal Quantin > a écrit : > >> Hi Anders, >> >> Le mar. 18 sept.

Re: [Wireshark-dev] Unhandled exception

I'm uploading a patch. Pascal. Le mar. 18 sept. 2018 à 10:20, Pascal Quantin a écrit : > Hi Anders, > > Le mar. 18 sept. 2018 à 10:19, Anders Broman > a écrit : > >> Hi, >> I think that the problem is that one of these fields has changed name, >> but debuggi

Re: [Wireshark-dev] Npcap 0.9-r9 causing WiFi disconnect?

Hi Anders, I do not face such issue with my Windows 10 1809 x64 build 17763, but had similar symptoms a few years back when testing development builds of Npcap on Windows 7 x64. Starting Wireshark was workarounding the issue. Those users should go to https://github.com/nmap/nmap/issues to report

Re: [Wireshark-dev] PFCP Trace information issue in WS 3.0.0 rc1

Hi Varun, Le ven. 22 févr. 2019 à 17:09, Varun Goyal a écrit : > HI , > > I have seen the code of WS of version 3.0.0 rc1 and found that WS is not > able to decode the IE Trace information correctly. > > Observation : > 1. Trace info has parameter > uint32_t Traceid:24, > uint32_t

Re: [Wireshark-dev] No interfaces showing (Win 10, WS 3.0)

hub.com/nmap/nmap/issues Best regards, Pascal. > > > *From:* Wireshark-dev *On Behalf Of > *Pascal Quantin > *Sent:* Monday, March 18, 2019 2:22 PM > *To:* Developer support list for Wireshark > *Subject:* Re: [Wireshark-dev] No interfaces showing (Win 10, WS 3.0) > > >

Re: [Wireshark-dev] No interfaces showing (Win 10, WS 3.0)

einstall you still have issues, the Nmap team is likely to ask you to check with their last version. Best regards, Pascal. > > > *From:* Wireshark-dev *On Behalf Of > *Pascal Quantin > *Sent:* Monday, March 18, 2019 2:38 PM > *To:* Developer support list for Wireshark &

Re: [Wireshark-dev] No interfaces showing (Win 10, WS 3.0)

Hi Graham and David, Le lun. 18 mars 2019 à 19:12, Graham Bloice a écrit : > As you had WinPcap before, there might be conflicts. I've always manually > uninstalled WinPcap before upgrading to npcap. > > Suggestions at this point are: > >1. Reboot. >2. Manually uninstall any existing

Re: [Wireshark-dev] issue to set up an RTP conversation

Hi Nicolas, Le ven. 22 mars 2019 à 12:53, Bertin Nicolas < nicolas.ber...@al-enterprise.com> a écrit : > Hello, > > I've a dissector (packet-ua3g) that calls rtp_add_address(...) to set up > an RTP conversation. > It was working but now it fails. I've checked on master, 3.0.0 (windows) > and

Re: [Wireshark-dev] Cannot find krb5.h

Hi David, Le jeu. 7 févr. 2019 à 12:58, a écrit : > > > I’ve updated my machine to VS2017, Latest, Qt, Git, Python, …. And I got > rid of cygwin and vs2015 > > The setup should match the instruction, but apparently not quite. (win10, > x64) > > > > Right now I fail to build latest master (a

Re: [Wireshark-dev] become an editor - EditorGroup

utions> | YouTube > <https://www.youtube.com/channel/UCCCGcTKD1teKf8VyaEKm-MA> | LinkedIn > <https://www.linkedin.com/company/viavi-solutions> > > > > > > -- > *Von:* Pascal Quantin > *Gesendet:* Dienstag, 19. Februar 2019 18:2

Re: [Wireshark-dev] become an editor - EditorGroup

Hi Maximilian, Le mar. 19 févr. 2019 à 18:18, Maximilian Kohler via Wireshark-dev < wireshark-dev@wireshark.org> a écrit : > Hello, > > I’m writing you, because I want to be an editor. > > I want to write a wiki page for the eCPRI-protocol. > > > We need your username (once you have created your

Re: [Wireshark-dev] help Ascii protocol

Hi Anis, Le ven. 1 févr. 2019 à 17:38, Anis Siad a écrit : > Hello, > > > > So I need some help. I have ascii protocol (text based) but I don’t know > how to dissect this protocol in C. > > I explained the problem here: >

Re: [Wireshark-dev] patching ASN.1 dissectors

Hi Dario, Le jeu. 31 janv. 2019 à 14:24, Dario Lombardo a écrit : > Hi > I want to fix a bug in the tcap dissector, specifically in the > function dissect_UniDialoguePDU_PDU. This is a generated dissector, > therefore I've looked for the generating code, but I got lost in the maze > of the

Re: [Wireshark-dev] patching ASN.1 dissectors

erencing it (it is properly set when decoding a TCP message thanks to the dissect_tcap() function, but not when decoding a subset of a TCAP message called from another dissector). This needs to be done for all instances of p_tcap_private use. Regards, Pascal. > > On Thu, Jan 31, 2019 a

Re: [Wireshark-dev] Lua script reads every packet twice

Hi Jerry, Le mer. 5 juin 2019 à 21:35, Jerry White a écrit : > HI all, > > Please forgive for such a basic question. I noticed that my lua dissector > processes a trace file twice. To isolate the issue I have removed nearly > all my business code and reduced to a function that does one thing.

Re: [Wireshark-dev] IDE for C development on Linux

Hi Paul, Le lun. 3 juin 2019 à 17:41, Paul Offord a écrit : > Hi, > > > > I want to learn a bit more about Wireshark running on Linux. I’ve been > using VS Community Edition on Windows for some time, and now I’m deciding > which IDE to use on Linux (specifically Centos 7). I use Eclipse on

Re: [Wireshark-dev] Proper way to handle changes in the preferences

Hi Sake, Le lun. 17 juin 2019 à 07:10, Sake Blok | SYN-bit a écrit : > Hi, > > I'm working on a patch to add the possibility to show times in milli- or > microsecond units. While working this out, I see a need to change the name > of certain preferences and/or change the values of other

Re: [Wireshark-dev] Error while building NSIS package

Hi Martin, Le mar. 14 mai 2019 à 14:46, Martin Mathieson via Wireshark-dev < wireshark-dev@wireshark.org> a écrit : > As the last step of building a Windows package, I ran > msbuild /m /p:Configuration=RelWithDebInfo nsis_package.vcxproj > > and got the error below. There are lots of libs

Re: [Wireshark-dev] Question about dissector "enhancement" / bug

Hi, Le ven. 28 juin 2019 à 06:06, Anders Broman a écrit : > > > Den fre 28 juni 2019 00:44Jason Cohen skrev: > >> The question about about weather or not adding dissection of additional >> information in a dissector is an enhancement or a bug; I think this is kind >> of a grey area. If a

Re: [Wireshark-dev] Speex for Windows?

Hi Chris, Le lun. 8 juil. 2019 à 18:35, Maynard, Chris via Wireshark-dev < wireshark-dev@wireshark.org> a écrit : > When compiling master (v3.1.0rc0-1232-gd8ad7a686384) on Windows, I noticed: > > -- Could NOT find SpeexDSP (missing: SPEEXDSP_LIBRARY > SPEEXDSP_INCLUDE_DIR) > … > -- The

<    2   3   4   5   6   7   8   9   >