Re: [Wireshark-dev] Announcing: A Wireshark Dissector Generator

2018-08-06 Thread Richard Sharpe
On Mon, Aug 6, 2018 at 2:10 PM, Guy Harris wrote: > On Aug 6, 2018, at 7:54 AM, Richard Sharpe > wrote: > >> Since about last November I have been developing a Wireshark Dissector >> Generator. > > How does its description language compare to that of > > http://wsgd.free.fr > > in its

Re: [Wireshark-dev] Announcing: A Wireshark Dissector Generator

2018-08-06 Thread Guy Harris
On Aug 6, 2018, at 7:54 AM, Richard Sharpe wrote: > Since about last November I have been developing a Wireshark Dissector > Generator. How does its description language compare to that of http://wsgd.free.fr in its capabilities?

Re: [Wireshark-dev] For some reason Version 2.6.2 (v2.6.2-0-g1b3cedbc) will no longer decode as ...

2018-08-06 Thread Richard Sharpe
On Fri, Aug 3, 2018 at 6:46 PM, Richard Sharpe wrote: > On Fri, Aug 3, 2018 at 6:22 PM, Guy Harris wrote: >> On Aug 3, 2018, at 3:12 PM, Richard Sharpe >> wrote: >> >>> Has anyone else seen this? >>> >>> For some reason Decode As no longer seems to work for me. >>> >>> We run NFS on port 20491

Re: [Wireshark-dev] Announcing: A Wireshark Dissector Generator

2018-08-06 Thread Kennedy, Smith (Wireless & Standards Architect)
Hi Richard, Your project sounds interesting, but I get a 404 when I visit the link you listed below. I've never done anything with "GitLab" - do you have to make it "public"? It doesn't show up on your personal page either. Smith > On Aug 6, 2018, at 8:54 AM, Richard Sharpe > wrote: > >

Re: [Wireshark-dev] Intallation (e.g. NSIS) build instructions not correct

2018-08-06 Thread Gerald Combs
Have you run CMake? We don't keep build system files (Ninja, MSBuild, Make, etc.) files in Git. We instead depend on CMake to generate them. It generates part of our NSIS configuration files as well, including config.nsh. On 8/6/18 5:47 AM, herbfal...@gmail.com wrote: > More information, the

Re: [Wireshark-dev] Intallation (e.g. NSIS) build instructions not correct

2018-08-06 Thread herbfalkmi
More information, the nsis*.*proj files are missing as is config.nsh? From: herbfal...@gmail.com Sent: Monday, August 6, 2018 7:38 AM To: wireshark-dev@wireshark.org Subject: Intallation (e.g. NSIS) build instructions not correct I followed the instructions to install NSIS, however none

[Wireshark-dev] Intallation (e.g. NSIS) build instructions not correct

2018-08-06 Thread herbfalkmi
I followed the instructions to install NSIS, however none of the project files were installed by "Choco" only an executable. The NSIS directory, downloaded from Git, as part of wireshark is also empty. Can anybody advise?

Re: [Wireshark-dev] Display more digits for NTP packet's root dispersion

2018-08-06 Thread Dario Lombardo
On Mon, Aug 6, 2018 at 1:20 PM Martin Burnicki wrote: > > I think to do this would be easy for someone who is a bit familiar with > the wireshark source code. However, I'm new to this stuff so I can > potentially get it wrong unless I'm doing quite a bit of investigation > first. ;-) > > Don't

Re: [Wireshark-dev] Display more digits for NTP packet's root dispersion

2018-08-06 Thread Martin Burnicki
Hi Dario, Dario Lombardo wrote: > Hi Martin > If you can code the patch, feel free to push it to gerrit for code > review. I think to do this would be easy for someone who is a bit familiar with the wireshark source code. However, I'm new to this stuff so I can potentially get it wrong unless

Re: [Wireshark-dev] Display more digits for NTP packet's root dispersion

2018-08-06 Thread Dario Lombardo
Hi Martin If you can code the patch, feel free to push it to gerrit for code review. Otherwise, your best bet is bugzilla. Which login issues are you experiencing? On Mon, Aug 6, 2018 at 11:20 AM Martin Burnicki wrote: > Hi all, > > actually the root dispersion field from an NTP packet is only

[Wireshark-dev] Display more digits for NTP packet's root dispersion

2018-08-06 Thread Martin Burnicki
Hi all, actually the root dispersion field from an NTP packet is only displayed with 4 digits after the decimal point, i.e. 0.1 ms resolution. However, modern NTP servers may provide a better root dispersion. E.g., if only the LSB in the scaled integer of an NTP packet is set then this means ~15