On Sat, Jun 26, 2021 at 9:41 PM Guy Harris wrote:
> So this isn't really a Wireshark dissector question, it's a protocol
> design and encoding question.
>
I'd like it not to be an encoding question beyond this: Given I'm using
ASN.1 to generate dissectors (for the protocols I am designing),
build step "make asn1"
On Tue, Jun 22, 2021 at 7:44 PM Guy Harris wrote:
> On Jun 22, 2021, at 6:33 PM, Vincent Randal wrote:
>
> > We are using PER per the foo example (Simple ASN.1-based dissector).
> Wow, I never about all these different encodings.
> >
> &g
PM Guy Harris wrote:
> On Jun 21, 2021, at 11:54 PM, Vincent Randal wrote:
>
> > The primary question in this email (but I think it requires some
> explanation below): How does one write an ASN.1-based dissector such that
> the generated code (per "make asn1") does i
quot;make asn1") does
indeed decode the first octet as the message type using C-style switch/case
construct? Is there an example that I can look at?
Thanks for reading to the end of my long and winding request for help.
Sinc
On Sat, May 22, 2021 at 3:51 AM Guy Harris wrote:
> On May 21, 2021, at 8:03 PM, Vincent Randal wrote:
>
> > I've plans to use Lua to control tshark behavior in scripts, IF ... I
> can get Wireshark to build with support for Lua in Ubuntu 20.4, ... But so
> far I am not having
Graham, thank you for helping. I've replied in red below with a couple of
follow questions if you don't mind.
Thanks, Vincent Randal.
On Sat, May 22, 2021 at 3:25 AM Graham Bloice
wrote:
> Some answers in-line
>
> On Sat, 22 May 2021 at 04:03, Vincent Randal wrote:
>
>&
Hello everyone,
I've plans to use Lua to control tshark behavior in scripts, IF ... I can
get Wireshark to build with support for Lua in Ubuntu 20.4, ... But so far
I am not having any luck. I found this piece of documentation that says ...
"Wireshark contains an embedded Lua 5.2 interpreter ..."
-a-wireshark-dissector-using-tshark.html
On Tue, Apr 20, 2021 at 2:47 PM Vincent Randal wrote:
> 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.
to test (if anything) regarding a new dissector in the asn1 directory?
I've been digging around a bit in the source files and I have not yet made
sense of how regression testing (or any testing) is done, or even if it
applies to dissectors let alone a new dissector.
Vincent Randal
On Mon, Apr 19, 202
uld remove the call to the data dissector after the ASN.1 PDU
> dissection (that happens because the FOO dissector does not indicate to have
> consumed
>
> Best regards,
> Pascal.
>
>
> Le jeu. 15 avr. 2021 à 23:59, Vincent Randal a
> écrit :
>
>> Hi Anders (and
(details in previous email)*
cd ../../..
mkdir build
cd build
cmake ../wireshark #this step worked previously but not on a fresh
wireshark clone now
make asn1 #with relevant entries in two CMakeListsCustom files
make
On Sun, Apr 18, 2021 at 8:15 PM Vincent Randal wrote:
> Hello Wireshark-
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
on this mailing list have indulged my need for guidance for which I am
sincerely grateful. It's my intention to reciprocate by helping when and
where I can in due time.
Thank you,
Vincent Randal
On Tue, Apr 13, 2021 at 9:46 AM Graham Bloice
wrote:
> Just to reset what I think are some misconcep
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
or target 'all' failed
> make: *** [all] Error
> 2*vtrandal@envy1vm6*:*~/Downloads/wireshark/build.wireshark*$ cd ..
>
>
On Thu, Apr 15, 2021 at 3:02 AM Pascal Quantin wrote:
> Hi Vincent,
>
> Le jeu. 15 avr. 2021 à 10:52, Vincent Randal a
> écrit :
>
>> (1)
he details of
the dissector.
On Thu, Apr 15, 2021 at 2:26 AM Guy Harris wrote:
> 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 directo
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
UDP-based dissector) in
support of 2..6.20 builds. I will do what I can to get involved:
https://www.wireshark.org/develop.html
Thank you.
Vincent
On Tue, Apr 13, 2021 at 11:16 PM Guy Harris wrote:
> On Apr 13, 2021, at 5:36 PM, Vincent Randal wrote:
>
> > If it’s important
development? It’s been awhile since I used either. Also, I
wonder if there are issues with Qt vs XQuartz.
I sincerely appreciate the help I received today from many people.
Vincent Randal
On Tue, Apr 13, 2021 at 5:40 PM Guy Harris wrote:
> On Apr 13, 2021, at 9:21 AM, Pascal Quantin wrote:
>
>
g]
Thank you! I have not yet figured out how to edit the various
CMakeListsCustom.txt files so that it builds the .o file in addition to
packet-foo.[ch]. If anyone has ideas how to edit the relevant
CMakeListsCustom.txt file(s), I'm eager to help test the ideas.
Vincent Randal
On Tue, Apr 13, 20
dissector in epan/dissectors/asn1 using
Linux? Maybe this step has been broken for a while in Linux (assuming it
works in Windows).
On Tue, Apr 13, 2021 at 9:03 AM Pascal Quantin wrote:
> Hi Vicent,
>
> Le mar. 13 avr. 2021 à 16:53, Vincent Randal a
> écrit :
>
>> I shoul
ards
>
> Anders
>
>
>
> *From:* Wireshark-dev *On Behalf Of
> *Vincent Randal
> *Sent:* den 13 april 2021 16:40
> *To:* Developer support list for Wireshark
> *Subject:* Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based
> dissector example (foo)
>
>
>
efore rerunning cmake again?
>
> I’m not sure on linux if the generate cmake file ends up under the build
> dir or in the source dir.
>
>
>
> Regards
>
> Anders
>
> *From:* Wireshark-dev *On Behalf Of
> *Vincent Randal
> *Sent:* den 13 april 2021 15:32
>
that underscores the Step by Step instructions need to
be updated to something that works. Any more ideas?
On Tue, Apr 13, 2021 at 7:12 AM John Thacker wrote:
> On Tue, Apr 13, 2021, 8:32 AM Vincent Randal wrote:
>
>> Hello everyone,
>>
>> I need help building th
S 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
> dis
ireshare (using
cmake), but no build targets get updated.
If the solution to this problem belongs in the Wireshark documentation, I
would be glad to help update the documentation. Namely, I don't understand
the usage of the 5 (five) CMakeListsCustom.txt.example files inWireshark
source code.
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
> pro
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
be built like those in ./epan/dissectors/asn1 (i.e. not a
plugin).
I've tried adding "foo" in the list of directories in the parent
CMakeLists.txt (but that does not affect build).
By the way: The first thing I did was build wireshark-3.4.4 from source
using cmake and that works.
Vincent
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
how to do that (yet).
Vincent Randal
Longmont, CO
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wir
31 matches
Mail list logo
