[Wireshark-dev] Rough consensus and quiet humming

https://twitter.com/MeghanEMorris/status/1382109954224521216/photo/1 ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe:

Re: [Wireshark-dev] Wireshark 3.4.5 is now available

Congratulations! That's a great achievement! Alex On Wed, Apr 21, 2021, 20:49 Gerald Combs wrote: > I'm proud to announce the release of Wireshark 3.4.5. > > > What is Wireshark? > >Wireshark is the world’s most popular network protocol analyzer. It is >used for troubleshooting,

[Wireshark-dev] some more sample captures

Hello, here are some other captures of the same series than CHARGEN (XINETD series) if you want to add them also. Nothing spectacular at all, at best just educational material. best regards E.A. Le lun. 9 déc. 2019 à 06:40, Jaap Keuter a écrit : > > That was so simple, I’ve already put them on

[Wireshark-dev] Wireshark 3.4.5 is now available

I'm proud to announce the release of Wireshark 3.4.5. What is Wireshark? Wireshark is the world’s most popular network protocol analyzer. It is used for troubleshooting, analysis, development and education. What’s New Bug Fixes The following vulnerabilities have been fixed:

Re: [Wireshark-dev] MR that commes up as "OK to Merge" fails pipline

Le mer. 21 avr. 2021 à 20:12, Gerald Combs a écrit : > On 4/21/21 6:38 AM, Pascal Quantin wrote: > > Hi Anders, > > > > Le mer. 21 avr. 2021 à 15:34, Anders Broman via Wireshark-dev < > wireshark-dev@wireshark.org > a > écrit : > > > > Hi, > > > >

Re: [Wireshark-dev] MR that commes up as "OK to Merge" fails pipline

On 4/21/21 6:38 AM, Pascal Quantin wrote: Hi Anders, Le mer. 21 avr. 2021 à 15:34, Anders Broman via Wireshark-dev mailto:wireshark-dev@wireshark.org>> a écrit : Hi, This MR https://gitlab.com/wireshark/wireshark/-/merge_requests/2178

Re: [Wireshark-dev] Who introduced these failures?

On Wed, Apr 21, 2021 at 10:47 AM Pascal Quantin wrote: > > Hi Richard, > > Le mer. 21 avr. 2021 à 19:43, Richard Sharpe a > écrit : >> >> My latest MR failed with these errors: >> >> - >> C:\builds\wireshark\wireshark\epan\dissectors\packet-componentstatus.c(172,71):

Re: [Wireshark-dev] Who introduced these failures?

Hi Richard, Le mer. 21 avr. 2021 à 19:43, Richard Sharpe a écrit : > My latest MR failed with these errors: > > - > > C:\builds\wireshark\wireshark\epan\dissectors\packet-componentstatus.c(172,71): > error C2220: workload = 100.0 * >

[Wireshark-dev] Who introduced these failures?

My latest MR failed with these errors: - C:\builds\wireshark\wireshark\epan\dissectors\packet-componentstatus.c(172,71): error C2220: workload = 100.0 * CSR_GET_WORKLOAD(tvb_get_ntohs(message_tvb, 284));

Re: [Wireshark-dev] MR that commes up as "OK to Merge" fails pipline

Hi Anders, Le mer. 21 avr. 2021 à 15:34, Anders Broman via Wireshark-dev < wireshark-dev@wireshark.org> a écrit : > Hi, > > This MR https://gitlab.com/wireshark/wireshark/-/merge_requests/2178 passed > check but failed merge at the firsts attempt – the author then amended > > It passed check and

[Wireshark-dev] MR that commes up as "OK to Merge" fails pipline

Hi, This MR https://gitlab.com/wireshark/wireshark/-/merge_requests/2178 passed check but failed merge at the firsts attempt - the author then amended It passed check and came up with a green merge button. It then fails pipeline.

Re: [Wireshark-dev] How to recognize that live capture is running?

Are you looking to copy the state of the Stop Capture button on the main toolbar? https://www.wireshark.org/docs/wsug_html_chunked/ChUseMainToolbarSection.html On Tue, Apr 20, 2021 at 1:39 PM Jirka Novak wrote: > Hi, > > I need to show a button in a dialog just in case that live capture is >

Re: [Wireshark-dev] still unclear how to build a new ASN.1-based dissector

Wait! I've overlooked the Wireshark documentation of all things. I will check there. https://www.wireshark.org/docs/wsdg_html_chunked/ChapterTests.html and a couple other places might have clues https://github.com/wireshark/happy-shark

Re: [Wireshark-dev] still unclear how to build a new ASN.1-based dissector

Hello, Anders, thank you. I think I've finally got the separate "generate" and "compile" steps clear now. Thank you. What I think remains is regression testing. Yes? No? For a new dissector should there be entry in some file (somewhere) that tells the build tools what to test (if anything)

[Wireshark-dev] How to recognize that live capture is running?

Hi, I need to show a button in a dialog just in case that live capture is running, but I'm not able to find how to get this information. I'm able to get information about change of state during e.g. closing capture, but not get current state. Can anyone advice me, how to get current status?

Re: [Wireshark-dev] Fwd: Tshark feature request

Hi, > I hope you are doing well, We are looking for feature request on Tshark, > > We would like to have mean,avg and max delta values print out, I propose to create change request on https://gitlab.com/wireshark/wireshark/-/issues I propose to clarify which formula you would like to use for

Re: [Wireshark-dev] Writing a wtap module for CommView WLAN Analyzer and Decoder NCFX format files

On Apr 19, 2021, at 10:02 AM, Richard Sharpe wrote: > On Sun, Apr 18, 2021 at 9:30 PM Guy Harris wrote: > >> We may want to change the 802.11 pseudo-header to have data rates in units >> of 100 Kb/s rather than 500 Kb/s, to handle NCFX and possibly other files. >> (We might also want to

Re: [Wireshark-dev] Writing a wtap module for CommView WLAN Analyzer and Decoder NCFX format files

On Sun, Apr 18, 2021 at 9:30 PM Guy Harris wrote: > > On Apr 18, 2021, at 2:33 PM, Richard Sharpe > wrote: > > > I am thinking of writing a wtap module to read ComView WLAN Analyzer > > and Decoder NCFS format files. > > > > They are a little like PCAP files with a radiotap header, > > ...and a

[Wireshark-dev] Remote Developer Den, April 2021

Hi everyone, I've scheduled the next remote Developer Den for next Wednesday, April 28. This is remote version of the Developer Den at SharkFest, a room that we set aside for office hours where everyone is welcome to stop in, say hello, ask questions, etc. The link below has a "join from

Re: [Wireshark-dev] still unclear how to build a new ASN.1-based dissector

Hi, Perhaps a misconception here, the generated files are part of the source tree currently so when you change any of the files in the ../asn1/foo directory you need to run make foo and check in the generated .c and optionally .h file. So on the very first round add the directory and files

Re: [Wireshark-dev] ASN.1-based dissector development for Wireshark

Hi Pascal, I sincerely appreciate the code changes you provided. If I applied it correctly, it did not fix the problem for me in my Ubuntu 18.04 VM, so I will try it in my host operating system, Debian 10. I’m slow trying this until I get version control working with git so I can diff the code

Re: [Wireshark-dev] Clearly, someone thought no one should be using CommView after 2038

On Apr 18, 2021, at 10:18 PM, Eugène Adell wrote: > probably the guy writing this considered the "Epochalypse" problem. Or wanted *some* test to help rule out files that are probably not ConnView NCF files (there is no file header, so there's no file magic number, and there's no packet magic

Re: [Wireshark-dev] Clearly, someone thought no one should be using CommView after 2038

Hello, probably the guy writing this considered the "Epochalypse" problem. See https://en.wikipedia.org/wiki/Year_2038_problem if necessary. best regards E.A. Le lun. 19 avr. 2021 à 04:18, Richard Sharpe a écrit : > > Hi folks, > > I just came across this validation check in the commview

Re: [Wireshark-dev] Writing a wtap module for CommView WLAN Analyzer and Decoder NCFX format files

On Apr 18, 2021, at 2:33 PM, Richard Sharpe wrote: > I am thinking of writing a wtap module to read ComView WLAN Analyzer > and Decoder NCFS format files. > > They are a little like PCAP files with a radiotap header, ...and a bit more like CommView NCF files, which we already support. > One

Re: [Wireshark-dev] still unclear how to build a new ASN.1-based dissector

CORRECTION: I omitted the troublesome steps (underlined) when describing the problem: git clone https:// wireshark cd wireshark git checkout wireshark-3.4.4 cd wireshark/epan/dissectors *cp ~/myfoo.tgz . #copy dissector code into wireshark clone* *tar xvf myfoo.tgz #extract the dissector code

[Wireshark-dev] Clearly, someone thought no one should be using CommView after 2038

Hi folks, I just came across this validation check in the commview wiretap code: if (... cv_hdr.year < 1970 || cv_hdr.year >= 2038 || ...) -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者) ___ Sent via:

[Wireshark-dev] still unclear how to build a new ASN.1-based dissector

Hello Wireshark-dev community, Apparently, I still don't have the correct sequence of steps necessary for first time generation of "packet-myfoo.c" and "packet-myfoo.h" for a new ASN.1-based dissector called myfoo. Details follow. I would like to understand (much better than I do) how to add an

[Wireshark-dev] Writing a wtap module for CommView WLAN Analyzer and Decoder NCFX format files

Hi folks, I am thinking of writing a wtap module to read ComView WLAN Analyzer and Decoder NCFS format files. They are a little like PCAP files with a radiotap header, but their format is quite different from the radiotap format. It contains much of the same info but it is in a different format.

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

On Fri, 16 Apr 2021 at 00:08, Vincent Randal wrote: > Hi Graham, > > Thank you for taking the time to help with some potential misconceptions. > I apologize for not replying to your concerns sooner. I can reassure you we > have the same understanding regarding the role of cmake and make in the >

Re: [Wireshark-dev] ASN.1-based dissector development for Wireshark

Hi Vincent, the truncated ASCII bytes pane seems like a Qt UI bug not related to the dissector code itself. It seems like you are suffering from https://gitlab.com/wireshark/wireshark/-/issues/17087 that got fixed in https://gitlab.com/wireshark/wireshark/-/merge_requests/1902 but not backported

Re: [Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

On Thu, Apr 15, 2021 at 1:23 PM Guy Harris wrote: > > On Apr 15, 2021, at 2:03 AM, Graham Bloice > wrote: > > > Wireshark is a complicated project to build. You can follow the tested > > way, as shown in the Developers Guide, which is essentially what our > > Continuous Integration (CI)

Re: [Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

On Apr 15, 2021, at 3:46 PM, Vincent Randal wrote: > I managed to save my terminal window contents. It's over 1MB compressed. $ mkdir build.wireshark $ cd build.wireshark $ cmake .. >cmake.out 2>&1 $ make -j 16 >errs 2>&1 $ ls -lh cmake.out errs

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

Hi Graham, Thank you for taking the time to help with some potential misconceptions. I apologize for not replying to your concerns sooner. I can reassure you we have the same understanding regarding the role of cmake and make in the build process. When I refer to cmake I mean the build method

[Wireshark-dev] packet-dns.c - how to get field value

add_rr_to_tree() add_opt_rr_to_tree() proto_tree_add_item(rr_tree, hf_dns_rr_len, tvb, offset, 2, ENC_BIG_ENDIAN); dissect_dns_answer() case T_PTR: /* Domain Name Pointer (12) */ { const gchar *pname; int pname_len; used_bytes = get_dns_name(tvb, cur_offset,

[Wireshark-dev] Wireshark not dissecting ONC RPC on a different port in build 3.4.4 and an older build but OK on Master?

Hi folks, I am seeing a weird problem. I grabbed a capture today from a CentOS 7.6-based system that contains some SMB2 traffic and some NFS traffic (on a non-standard port). Wireshark 3.4.4 on Windows will not dissect the RPC packets and thus the NFS packets. However, it will dissect a similar

Re: [Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

Hi Pascal, Guy, and numerous others, I managed to save my terminal window contents. It's over 1MB compressed. If I cannot reproduce the problem I will look through that. Thank you, Vincent On Thu, Apr 15, 2021 at 9:10 AM Vincent Randal wrote: > Hi Pascal, > > Where is the build log? I've

Re: [Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

On Thu, 15 Apr 2021 at 21:23, Guy Harris wrote: > On Apr 15, 2021, at 2:03 AM, Graham Bloice > wrote: > > > Wireshark is a complicated project to build. You can follow the tested > way, as shown in the Developers Guide, which is essentially what our > Continuous Integration (CI) systems use

Re: [Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

On Apr 15, 2021, at 2:03 AM, Graham Bloice wrote: > Wireshark is a complicated project to build. You can follow the tested way, > as shown in the Developers Guide, which is essentially what our Continuous > Integration (CI) systems use and most other developers, or you can forge your > own

Re: [Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

On Apr 15, 2021, at 8:10 AM, Vincent Randal wrote: > Where is the build log? In the file to which you redirected the standard output and error of the make command - or the file created by tee, if piped the standard output and error of the make command to "tee errs" so that the errors are

Re: [Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

Hi Pascal, Where is the build log? I've since rebuilt Wireshark successfully in ./build as Graham wisely suggests. This thing is not easy to reproduce. There may be something unstable about my build environment on Ubuntu 18.04 if that even makes sense. What I do have is the build output to the

Re: [Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

Wireshark is a complicated project to build. You can follow the tested way, as shown in the Developers Guide, which is essentially what our Continuous Integration (CI) systems use and most other developers, or you can forge your own path on less travelled routes strewn with rocks, rusty nails and

Re: [Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

Hi Vincent, Le jeu. 15 avr. 2021 à 10:52, Vincent Randal a écrit : > (1) There is no error message other than it fails immediately when > beginning building "qtui" (at about 70% of the way into make for > wireshark-3.4.4) > You should have an error message, please check above in the build log.

Re: [Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

(1) There is no error message other than it fails immediately when beginning building "qtui" (at about 70% of the way into make for wireshark-3.4.4) (2) Good point. Wireshark uses dissectors to provide details of packets, as you point out. So then the dissector source code provides the details of

Re: [Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

On Apr 15, 2021, at 12:55 AM, Vincent Randal wrote: > (1) building Wireshark in build.wireshark fails > The solution here is to use "build" as the name of the build directory and > then make succeeds. Otherwise, if the build directory has some other name > like build.wireshark then make fails

[Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

Hello, (1) building Wireshark in build.wireshark fails The solution here is to use "build" as the name of the build directory and then make succeeds. Otherwise, if the build directory has some other name like build.wireshark then make fails at about 70% when building qtui. Why do I want to name

Re: [Wireshark-dev] Closing issue 15128

Hi Uli, 14 avr. 2021 16:22:14 Uli Heilmeier : > Hi List, > > Would someone who has the necessary rights please be so kind and close issue > 15128 [1]? > I am missing the necessary permission. Done Best regards, Pascal. > > Cheers > Uli > > > [1]

[Wireshark-dev] Closing issue 15128

Hi List, Would someone who has the necessary rights please be so kind and close issue 15128 [1]? I am missing the necessary permission. Cheers Uli [1] https://gitlab.com/wireshark/wireshark/-/issues/15128 ___ Sent via:

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

Thank you, Guy, Pascal, John, Anders, Graham, Richard et al, So that’s what CI Build means. Very nice. https://www.wireshark.org/docs/wsdg_html_chunked/ChIntroAutomated.html Okay. I will not make a very big effort to insert ifdef’s throughout affected source files (relevant to the simple ASN.1

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

On Apr 13, 2021, at 5:36 PM, Vincent Randal wrote: > If it’s important not to break wireshark-2.6.20 It's not. All I'm saying there is that there are different levels of support: for Windows and macOS, we do CI builds, so we know Wireshark builds and runs, and supply binaries;

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

Guy, I want keep my promise to update the Wireshark documentation for the simple ASN.1 UDP-based dissector example so that it more accurately reflects the current build method that starts with cmake. I will do a better job now with input and help I’ve received. If it’s important not to break

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

On Apr 13, 2021, at 9:21 AM, Pascal Quantin wrote: > 13 avr. 2021 17:36:20 John Thacker : > > > Depending on your build system, the other ASN.1 dissectors can be > > regenerated with either > > > > ninja asn1 > > Or > > make asn1 > > > > without starting the full build process. > >

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

On Apr 13, 2021, at 6:03 AM, Vincent Randal wrote: > I'm building Wireshark on Linux. Wireshark documentation refers to it as UNIX > or UNIX-like. Linux is one of the UNIX-like systems we support, yes. We also officially support macOS, and the build process may also work on FreeBSD, NetBSD,

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

With everyone's help I have successfully built the simple ASN.1 UDP-based dissector in Linux (Ubuntu 18.04). And it is available in my Wireshark build for use in the display filter as shown in the screenshot below. I made my changes against wireshark-3.4.4, but I did not use

Re: [Wireshark-dev] Hitting a weird error in a MR pipeline

Le mar. 13 avr. 2021 à 18:49, Pascal Quantin a écrit : > This is because of > https://gitlab.com/wireshark/wireshark/-/merge_requests/2689 > that was merged despite a Windows failure. need to fix it. > Fix attempt here, to be reviewed by Jirka:

Re: [Wireshark-dev] Hitting a weird error in a MR pipeline

This is because of https://gitlab.com/wireshark/wireshark/-/merge_requests/2689 that was merged despite a Windows failure. need to fix it. Pascal. 13 avr. 2021 18:42:29 Richard Sharpe : > Hi folks, > > In my latest MR pipeline: > https://gitlab.com/wireshark/wireshark/-/pipelines/285790755 >

[Wireshark-dev] Hitting a weird error in a MR pipeline

Hi folks, In my latest MR pipeline: https://gitlab.com/wireshark/wireshark/-/pipelines/285790755 I see these errors in the Windows build portion: --- C:\builds\wireshark\wireshark\ui\qt\rtp_player_dialog.cpp(671,22): error C2220: the following warning is treated as an error

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

Keyboard and brain got a little misconnected there. The first 2 sentences of item 3, which are missing some things I meant to fill in, can be replaced with the text from item 5. On Tue, 13 Apr 2021 at 16:45, Graham Bloice wrote: > Just to reset what I think are some misconceptions here: > > >

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

13 avr. 2021 17:36:20 John Thacker : > Depending on your build system, the other ASN.1 dissectors can be regenerated > with either > > ninja asn1 >   Or > make asn1 > > without starting the full build process. Those commands will regenerate all the ASN.1 dissectors. The command I gave allows

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

Just to reset what I think are some misconceptions here: 1. CMake, despite having the verb "Make" in its name, doesn't make the application. CMake makes something (depends on the platform, i.e. a Makefile or ninja build file or Visual Studio solution\project files) that then allows

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

Depending on your build system, the other ASN.1 dissectors can be regenerated with either ninja asn1 Or make asn1 without starting the full build process. I do it all the time, last did it a week ago when developing on Linux and just did it two minutes ago before writing this email to check

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

Before or After running cmake (in Linux) there are no files containing "generate_dissector" in the filename in asn1/foo. And they do not exist anywhere in the source tree. How did the other asn1 dissectors get generated in Linux? When was the last time anyone generated or updated a dissector in

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

Hi Vicent, Le mar. 13 avr. 2021 à 16:53, Vincent Randal a écrit : > I should give that a try. What version of Windows and tools are you using? > I’m beat. I need to do something that works soon. > No need to install Windows; it works the same way on Linux. Go to your build folder and run:

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

I should give that a try. What version of Windows and tools are you using? I’m beat. I need to do something that works soon. On Tue, Apr 13, 2021 at 8:47 AM Anders Broman via Wireshark-dev < wireshark-dev@wireshark.org> wrote: > Hi, > > I don’t think they are generated what will be generated are

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

Hi, I don’t think they are generated what will be generated are the files needed to DO the generation. On windows the next step is to run msbuild /m /p:Configuration=RelWithDebInfo epan\dissectors\asn1\h248\generate_dissector-h248.vcxproj which will the generate the .c and .h files Regards

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

Correct insofar as there are no generated files associated with asn1/foo directory. Namely, packet-foo.c and packet-foo.h did not get generated. But maybe that's not definitive proof that asn1/foo dissector did not get built. How else can I confirm the dissector was or was not built? Open

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

Hi, So you are saying that if you create foo dir like epan/dissectors/asn1/foo/ Rename and update the custom cmake file to set(CUSTOM_ASN1_SRC_DIR foo ) And place your source file and cmake.txt in the foo dir then rerun the cmake process Nothing happens? Try to

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

I tried renaming ./epan/dissectors/asn1/CMakeListsCustom.txt.example to CMakeListsCustom.txt with an entry as follows: # Add a list of your custom asn1 dissectors here set(CUSTOM_ASN1_SRC_DIR foo ) Again, the build did not update any targets even with that change. But this is progress because

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

On Tue, Apr 13, 2021, 8:32 AM Vincent Randal wrote: > Hello everyone, > > I need help building the simple ASN.1 UDP-based dissector example (foo); > specifically, I need help building the generate_dissector-*proto* target > (Step #6 below). I'm certainly missing something here. > > > (c) I

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

I'm building Wireshark on Linux. Wireshark documentation refers to it as UNIX or UNIX-like. At the moment I'm using Ubuntu 18.04 LTS to build wireshark-3.4.4 On Tue, Apr 13, 2021 at 6:38 AM Anders Broman via Wireshark-dev < wireshark-dev@wireshark.org> wrote: > Hi, > > On what OS are you doing

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

Hi, On what OS are you doing this? Regards Anders From: Wireshark-dev On Behalf Of Vincent Randal Sent: den 13 april 2021 14:32 To: Developer support list for Wireshark Subject: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo) Hello everyone, I

[Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

Hello everyone, I need help building the simple ASN.1 UDP-based dissector example (foo); specifically, I need help building the generate_dissector-*proto* target (Step #6 below). I'm certainly missing something here. I'm following the Step by Step instructions (shown below) to create the simple

Re: [Wireshark-dev] ASN.1 dissector Wireshark

Thank you. As for the second part I will post as a new separate question in the morning. On Mon, Apr 12, 2021 at 11:43 PM Guy Harris wrote: > On Apr 12, 2021, at 10:08 PM, Vincent Randal wrote: > > > Thank you (John) for delving into a nice description of the overall > process. I do have a

Re: [Wireshark-dev] ASN.1 dissector Wireshark

On Apr 12, 2021, at 10:08 PM, Vincent Randal wrote: > Thank you (John) for delving into a nice description of the overall process. > I do have a couple more questions for you and the group: > 1. What is the meaning of "work is in progress to at least read all ASN1 > specifications" ??? > I'm

Re: [Wireshark-dev] Fwd: ASN.1 dissector Wireshark

Typo: I wrote usable when I meant unusable in this sentence: "the ASN.1 was usable by ans2wrs()" On Mon, Apr 12, 2021 at 11:08 PM Vincent Randal wrote: > Greetings everyone, > > Thank you (John) for delving into a nice description of the overall > process. I do have a couple more questions for

Re: [Wireshark-dev] Fwd: ASN.1 dissector Wireshark

Greetings everyone, Thank you (John) for delving into a nice description of the overall process. I do have a couple more questions for you and the group: 1. What is the meaning of "work is in progress to at least read all ASN1 specifications" ??? I'm trying to imagine what that implies. Does it

Re: [Wireshark-dev] Proposal: New set of help pages for VoIP dialogs

https://www.wireshark.org/lists/wireshark-dev/202009/msg00045.html "Man pages are updated as part of the stable branch release process." On Sun, Apr 11, 2021 at 12:04 PM Jirka Novak wrote: > Hi Jaap, > > > You could instead think about adding to the user guide, where this stuff > should be in

Re: [Wireshark-dev] Proposal: New set of help pages for VoIP dialogs

Hi Jaap, > You could instead think about adding to the user guide, where this stuff > should be in the first place. I updated user guide, but even it was merged, old pages are shown on: https://www.wireshark.org/docs//wsug_html_chunked/ChTelRTPAnalysis.html Do you know correct procedure to

Re: [Wireshark-dev] Fwd: ASN.1 dissector Wireshark

On Sat, Apr 10, 2021 at 11:15 PM Vincent Randal wrote: > Greetings, everyone. I’ve a question regarding: > > https://www.wireshark.org/docs/wsdg_html_chunked/Asn1DissectorRequirements.html > > I take this to mean Wireshark ASN.1 support might not be up to date going > forward. Is that the

[Wireshark-dev] Fwd: ASN.1 dissector Wireshark

Greetings, everyone. I’ve a question regarding: https://www.wireshark.org/docs/wsdg_html_chunked/Asn1DissectorRequirements.html I take this to mean Wireshark ASN.1 support might not be up to date going forward. Is that the meaning? ASN.1 has a long history. It makes sense periodically to freeze

[Wireshark-dev] Fwd: [nmap/npcap] Release v1.30 - Npcap 1.30

-- Forwarded message - From: Daniel Miller Date: Fri, Apr 9, 2021 at 8:42 PM Subject: [nmap/npcap] Release v1.30 - Npcap 1.30 To: nmap/npcap Cc: Subscribed Npcap 1.30 Repository: nmap/npcap ·

Re: [Wireshark-dev] general inquiry on building dissectors for wireshark-3.4.4

Hi, If the protocol is truly described by asn1 documents there are plenty of examples in epan/dissectors/asn1/ Basically you need the asn1 description a template and a .cnf file. Are you building on Windows or Linux? I’m not familiar with building the asn1 based dissectors on Linux. Are you

[Wireshark-dev] Next steps after submitting a dissector?

Hi, I recently submitted a pull request for a TIFF image dissector (in !2640). It was originally written to help with troubleshooting a proprietary industrial camera protocol, but I fleshed it out and decided to submit it. After reviewing doc/README.dissector, it looks like there are a few things

Re: [Wireshark-dev] general inquiry on building dissectors for wireshark-3.4.4

On Wed, 7 Apr 2021 at 17:28, Vincent Randal wrote: > Hello, > > Where can I find a complete "text based" dissector example that builds > with the current Wireshark cmake build method used in wireshark-3.4.4? Does > that question even make sense? I fear most people reading my question won't >

[Wireshark-dev] general inquiry on building dissectors for wireshark-3.4.4

Hello, Where can I find a complete "text based" dissector example that builds with the current Wireshark cmake build method used in wireshark-3.4.4? Does that question even make sense? I fear most people reading my question won't understand what I'm after. I've watched numerous YouTube videos by

[Wireshark-dev] Gitlab paid tiers

Is anyone using a paid tier with the Wireshark project? With their plan changes, I'm not sure what tier this would fall into: View the history of changes to an issue/mr/epic description (duplicate) ( https://gitlab.com/gitlab-org/gitlab/-/issues/10104) Move description_diffs from Premium to

Re: [Wireshark-dev] Bugzilla -> Gitlab failed migration

On Apr 6, 2021, at 12:11 PM, Uli Heilmeier wrote: > Just discovered that Bugzilla bugs 5379 [1] and 8161 [2] haven't been > migrated successfully to Gitlab issues. > > Both issues have state "opened" and Bugzilla status is "RESOLVED FIXED". > Furthermore Bugzilla comments are missing in > the

[Wireshark-dev] Bugzilla -> Gitlab failed migration

Hi, Just discovered that Bugzilla bugs 5379 [1] and 8161 [2] haven't been migrated successfully to Gitlab issues. Both issues have state "opened" and Bugzilla status is "RESOLVED FIXED". Furthermore Bugzilla comments are missing in the Gitlab issues. A quick search didn't show any additonal

Re: [Wireshark-dev] [Season of Docs] Congratulations on successfully completing your project

Hi folks, I updated the GSoD2020 wiki page with the results and added my fun art under CC BY-SA license. GitLad does not allow uploading big files, so I had to reduce the resolution. Feel free to ask for a better quality if you wanna

Re: [Wireshark-dev] Wiki editor permission request

Done! On 4/3/21 11:21 PM, Alex Nik wrote: Hi, I would like to request the permission to edit the Wireshark wiki. My GitLab username is Alex Nik . Thanks in advance. Alex ___ Sent via:

[Wireshark-dev] Wiki editor permission request

Hi, I would like to request the permission to edit the Wireshark wiki. My GitLab username is Alex Nik . Thanks in advance. Alex ___ Sent via:Wireshark-dev mailing list Archives:

[Wireshark-dev] Support for searching in FT_BYTES or longer bit fields

Hi folks, In one of the fields in 802.11az D3.0 there is a bit field that can be up to 512 bits long, and has padding defined to round it out to the nearest byte. This creates some problems with respect to how to insert it so that users can search on the field. No one wants to have to enter all

Re: [Wireshark-dev] Failed pipeline for nvmeof_getlog_page | wireshark | 3a8e09ef

Gerald, Jo?o: Thank you for provided answers. I think it covers it all. I will fix the warnings. I am not sure how to trigger this pipeline, I hope it will be picked up automatically. If I do not see a build, I will try a manual run. In retrospective, I am curious whether the project needs

Re: [Wireshark-dev] [Season of Docs] Congratulations on successfully completing your project

Thanks, Peter <3 we had a release at work, so I was focusing there.. will continue helping with the docs as I already told you. Will check out info about Wireshark fest as well. luvluv Alex On Wed, Mar 31, 2021, 23:29 Peter Wu wrote: > Hi Alex, > > Thank you for your contributions to the

Re: [Wireshark-dev] [Season of Docs] Congratulations on successfully completing your project

I would really like to see more of Alex's art at SharkFest, maybe on T-shirts or mugs, I think attendees would love it. On Wed, 31 Mar 2021 at 22:29, Peter Wu wrote: > Hi Alex, > > Thank you for your contributions to the documentation! Some components > have been undocumented for a while. You

Re: [Wireshark-dev] Failed pipeline for nvmeof_getlog_page | wireshark | 3a8e09ef

gitlab.com/constg2021/wireshark On 31/03/21 21:00, Gerald Combs wrote: Hi Constantine, You receivied the failure notice because: - You pushed a commit to gitlab.com/constg2021/wireshark. Was this for a merge request for wireshark/wireshark? From GitLab's perspective it dosen't matter.

Re: [Wireshark-dev] [Season of Docs] Congratulations on successfully completing your project

Hi Alex, Thank you for your contributions to the documentation! Some components have been undocumented for a while. You did a good job trying to track down relevant subject matter experts and doing some research on your own, despite not being familiar in the area. The results are visible on

Re: [Wireshark-dev] Failed pipeline for nvmeof_getlog_page | wireshark | 3a8e09ef

Hi Constantine, You receivied the failure notice because: - You pushed a commit to gitlab.com/constg2021/wireshark. Was this for a merge request for wireshark/wireshark? From GitLab's perspective it dosen't matter. constg2021/wireshark is a separate project. - CI/CD is enabled in

Re: [Wireshark-dev] Qt link errors (Q_INIT_RESOURCE)

I was able to replicate this using an opensuse/leap:42.3 docker image with a default build environment, which includes CMake 3.5.2 and Qt 5.6.2. I also installed various CMake versions and got the following results: CMake 3.5.2: CMake succeeded, ninja failed CMake 3.8.2: CMake succeeded, ninja

Re: [Wireshark-dev] Failed pipeline for nvmeof_getlog_page | wireshark | 3a8e09ef

Ronnie: Thank you for taking your time to reply. I think you entirely missed my point. The question was not regarding how to fix but about significance of this build test. I saw my previous merge requests approved and even merged when this test failed. I then saw it post factum, and

[Wireshark-dev] overzealous tcpros_tcp detection

Hi, Yesterday I've spent some time figuring out why the http2_tcp heuristic dissector wasn't working on my particular pcap. Turns out the reason is that tcpros_tcp was claiming the data before http_tcp could get a turn (http2_tcp is registered under http despite the _tcp in the name). In

<    7   8   9   10   11   12   13   14   15   16   >