>> To: Antoine d'Otreppe a.dotre...@aspyct.org; Developer support list for
>>> Wireshark wireshark-dev@wireshark.org
>>> Subject: Re: [Wireshark-dev] Anyone working on a Syncthing dissector?
>>> Hi Antoine!
>>> Based on the specifications for Syncthing, it appea
gt;
> >>
> >> -Original Message-
> >>
> >>> 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...@a
n
> wrote:
>
>>
>> -Original Message-
>>
>>> 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 supp
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
-Original Message-
>From: Wireshark-dev On Behalf Of Peter
>Wu
>Sent: den 9 november 2018 00:22
>To: Antoine d'Otreppe ; Developer support list for
>Wireshark
>Subject: Re: [Wireshark-dev] Anyone working on a Syncthing dissector?
>
>Hi Antoine!
>
&
Hi Antoine!
Based on the specifications for Syncthing, it appears that it uses Protobuf for
defining its messages:
https://docs.syncthing.net/specs/
I am not sure how well protobuf is currently supported on Wireshark, you could
scan the issue tracker and code review site to see if there is any
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
