[Wireshark-dev] extcap tools

Hi All, I am confused by differences in extcap between the CLI and the GUI. By default (in 3.0.0 on both Windows, Macos), extcap tools are presented as interfaces on the capture page. [image: Screen Shot 2019-03-23 at 8.11.37 PM.png] *Questions* 1. In the Wireshark GUI, if you go to About > Plugi

Re: [Wireshark-dev] Statistical Analysis of pcapng files

Hi Paul, It looks like there is a package called crafter to work with pcap files, which fits with extracting/processing. If are you looking for something more you may want to be more detailed in your use case. Cheers, Ross On Wed, Apr 3, 2019 at 8:08 PM -0

Re: [Wireshark-dev] Wireless Timeline?

Better yet, post a link to the capture (google drive/dropbox) so it can be evaluated. On Wed, Apr 3, 2019 at 11:11 PM Simon Barber via Wireshark-dev < wireshark-dev@wireshark.org> wrote: > The timeline will not show up unless hardware timestamps are present for > *all* frames in the capture, and

Re: [Wireshark-dev] Release lifetime and version number changes?

I agree that even/odd is non-standard and confusing. > I’m not sure. How would we label the development branch? It’s currently 3.1.0 or is it 3.1.0rc0? (Version 3.1.0 (v3.1.0rc0-521-gdba02458)) would people understand? > But I’m ok either way. I think the Python developer guide

Re: [Wireshark-dev] CMake Error [CMAKE_MAKE_PROGRAM is not set] while building wireshark from source

Looks like you need to install make as well as ninja. Please verify that both `ninja --version` and `make --version` have valid responses. Ross On Thu, Apr 18, 2019 at 12:16 PM Abhisek Techie wrote: > Hi , > > I am trying to build wiresha

Re: [Wireshark-dev] Release lifetime and version number changes?

, Apr 19, 2019 at 10:19 PM Jaap Keuter wrote: > Does Python release *every* build to the general public, as Wireshark > does? If so, how are these identified? I could only find specific defined > releases, starting from Alpha so-and-so. > > On 12 Apr 2019, at 12:51, Ross Jacobs wro

Re: [Wireshark-dev] Git hooks

Hi Dario, You should take a look at pre-commit , which is another way to enforce code quality. To run the tools in the tools folder, you would add a script hook in a `.pre-commit-config.yaml`. To initialize your repo with hooks, you would use `pre-commit install`. It's al

Re: [Wireshark-dev] Passwordlist in Wireshark - User feedback wanted

My $0.02: > this could lead companies... to deny the use of the program, due to wrongly identifying Wireshark as a hacking tool. Wireshark is already a "hacker tool" de facto, regardless of the fact that it performs passive network analysis. The first two results for "hacker tools" on Google lis

Re: [Wireshark-dev] Calculating CRC5 of 11-bit data

Hi Tomasz, My vote is for table lookup along a one-byte boundary as all of the existing CRC checkers in /wsutil currently use one. Notice how in our CRC16 and CRC32 implementations, we bitshift by 8 and 24 respectively. It should be possible to compute any CRC along a one-byte boundary. This artic

Re: [Wireshark-dev] Two typos is wireshark manual

Hi Nan, Thanks for reaching out to the dev mailing list! Typos in documentation are bugs. Please submit them as such on Wireshark's bugzilla . The category should be `main site - www.wireshark.org` as that is where the document

Re: [Wireshark-dev] Extcap binaries on OSX

It's 'darwin' $ python Python 3.7.2 (v3.7.2:9a3ffc0492, Dec 24 2018, 02:44:43) [Clang 6.0 (clang-600.0.57)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import sys; sys.platform 'darwin' Same on Python2.7. On Fri, Dec 20, 2019 at 3:17 AM Dario Lombardo wr

Re: [Wireshark-dev] Display Filter Folders - a question to vote

Hi Roland, Personally, I would avoid this usage here as I read `&&` as "find the packets where both of these display filters are valid". (If I'm reading you correctly) would it be possible to use `.` like `Proto.HTTP` to mimic the expectation in display filters that right is a component of left?