Re: [Wireshark-dev] Builds without PCAP fail the unit tests

2018-12-18 Thread Antoine d'Otreppe
Yes, those are the tests I was referring to. Well then it's all fine I guess. Thanks for clearing that up :) ‐‐‐ Original Message ‐‐‐ On Tuesday, December 18, 2018 8:45 PM, Guy Harris wrote: > On Dec 18, 2018, at 11:18 AM, Antoine d'Otreppe a.dotre...@aspyct.org wrote: > &g

[Wireshark-dev] Builds without PCAP fail the unit tests

2018-12-18 Thread Antoine d'Otreppe
Hi all, Half of my builds, those without PCAP, failed recently on travis during the test step: https://travis-ci.org/aspyct/wireshark/builds/469639514 (Mind you, they were broken before, but for a different reason). The logs say, among other things: "tshark: This version of TShark was not

[Wireshark-dev] ws_base32_decode should be named *_encode and seems non standard

2018-11-29 Thread Antoine d'Otreppe
Hi all, Something about the ws_base32_decode function looks weird, and I'm a little confused. Can I please have a sanity check? 2 things: 1. ws_base32_decode is actually an encode 2. it's not the standard base32 as defined in RFC4648 Let me explain. 1. It's actually an encode The function is

Re: [Wireshark-dev] Looking for a base32_encode

2018-11-29 Thread Antoine d'Otreppe
e only implement function s > that are actually needed. > > kind regards > Roland > > Am Do., 29. Nov. 2018 um 09:35 Uhr schrieb Antoine d'Otreppe > : > >> Hi all, >> >> Still working on the syncthing dissector, I need a base32_encode. >> I've

[Wireshark-dev] Looking for a base32_encode

2018-11-29 Thread Antoine d'Otreppe
Hi all, Still working on the syncthing dissector, I need a base32_encode. I've noticed there's a wsutil/base32.c file, which contains a base32_decode. Unfortunately I couldn't find the corresponding encode. Do we have that

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

2018-11-15 Thread Antoine d'Otreppe
Spot on! Thanks Pascal! ‐‐‐ Original Message ‐‐‐ On Thursday, November 15, 2018 10:14 PM, Pascal Quantin wrote: > Hi Antoine, > > Le jeu. 15 nov. 2018 à 22:09, Antoine d'Otreppe a > écrit : > >> Hi devs :) >> >> Small pickle here. Can you enlighten

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

2018-11-15 Thread Antoine d'Otreppe
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 specifies type 'long' but the argument has type 'gint64' (aka 'long long')

Re: [Wireshark-dev] GDB / Fuzz test ?

2018-11-12 Thread Antoine d'Otreppe
Hmmm, yeah I saw the "do you want dynamic libs", and then I said no. Guess I was tired... I'll try that! Thanks! ‐‐‐ Original Message ‐‐‐ On Monday, November 12, 2018 10:27 AM, Dario Lombardo wrote: > On Mon, Nov 12, 2018 at 9:40 AM Antoine d'Otreppe > wrote: > >

[Wireshark-dev] GDB / Fuzz test ?

2018-11-12 Thread Antoine d'Otreppe
Hi folks! I'm progressing in the syncthing dissector. Wireshark compiled without hassle on Manjaro (Arch derivative). I love the wireshark codebase, it's refreshing to see a large project that just works... Anyway I have two questions: 1. I'm not familiar with GDB and could not set a

Re: [Wireshark-dev] Anyone working on a Syncthing dissector?

2018-11-09 Thread Antoine d'Otreppe
Maciej Am 09.11.18 um 09:52 schrieb Antoine d'Otreppe: > Hi Peter, hi Anders, > > Thanks for the pointers! I'll look into it and report back here when I have > more information on the topic. > > > Cheers, > Antoine > > > > > ‐‐‐ Original Messa

Re: [Wireshark-dev] Anyone working on a Syncthing dissector?

2018-11-09 Thread Antoine d'Otreppe
gt; > > From: Wireshark-dev wireshark-dev-boun...@wireshark.org On Behalf Of Peter > > Wu > > Sent: den 9 november 2018 00:22 > > To: Antoine d'Otreppe a.dotre...@aspyct.org; Developer support list for > > Wireshark wireshark-dev@wireshark.org > > Subject: Re: [Wiresh

[Wireshark-dev] Anyone working on a Syncthing dissector?

2018-11-08 Thread Antoine d'Otreppe
Hi there, I'm interested in learning more about wireshark in general, and in particular learning how to make my own dissectors. I just happened to find a protocol that doesn't seem to have any dissector for it yet: syncthing. https://syncthing.net/ The local discovery protocol looks easy