Re: [Wireshark-dev] asn2wrs: autodetection for 64 bits X constrained integers

Hi Pascal, thank You for fast response and proposal review. Best Regards, Pavel From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Pascal Quantin Sent: Wednesday, October 25, 2017 12:30 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev]

Re: [Wireshark-dev] Duplicate dissectors (anonymous) and (anonymous) for protocol xxx

On Oct 25, 2017, at 1:44 PM, John Dill wrote: > I just happened to turn on console printing to troubleshoot a different > problem and I'm getting a couple of interesting messages when I change my > protocol preferences. > > Duplicate dissectors (anonymous) and

Re: [Wireshark-dev] Duplicate dissectors (anonymous) and (anonymous) for protocol xxx

If you create separate dissector handles with a protocol, how is a user using "Decode As" functionality supposed to know which dissection function will be picked? That's why the check was added. You can have the same protocol ID between TCP and UDP, but you can't have the same one twice in

[Wireshark-dev] Duplicate dissectors (anonymous) and (anonymous) for protocol xxx

I just happened to turn on console printing to troubleshoot a different problem and I'm getting a couple of interesting messages when I change my protocol preferences. Duplicate dissectors (anonymous) and (anonymous) for protocol xxx in dissector table tcp.port Protocol is already

Re: [Wireshark-dev] Info column with multiple PDUs in one frame

Hi Thomas, 2017-10-25 21:02 GMT+02:00 Thomas Wiens : > On 25.10.2017 18:36, Jeff Morriss wrote: > > > Typically how multiple PDUs are handled is by setting a "fence" in the > INFO > > column. Calling col_clear() only clears as far back as the fence; this > > allows upper-layer

Re: [Wireshark-dev] Info column with multiple PDUs in one frame

On 25.10.2017 18:36, Jeff Morriss wrote: > Typically how multiple PDUs are handled is by setting a "fence" in the INFO > column. Calling col_clear() only clears as far back as the fence; this > allows upper-layer dissectors to clear what the lower-layer dissector(s) > put in the INFO column--but

Re: [Wireshark-dev] Wireshark configure issue

Hi, You need libgcrypt-devel (and not only libgcrypt) Cheers On Wed, Oct 25, 2017 at 4:54 PM, Manik Khandelwal < manik123khandel...@gmail.com> wrote: > Hello all, > While building wireshark on Ubuntu 16.04, I successfully generated > configure file. Unfortunately encountered the following

Re: [Wireshark-dev] Info column with multiple PDUs in one frame

On Wed, Oct 25, 2017 at 12:08 PM, Thomas Wiens wrote: > Hi, > > is there a common way or best practice of how to add information to the > info column, when there are multiple independent PDUs inside a frame > possible? > > Currently I'm first cleaning out the info column with: >

Re: [Wireshark-dev] Wireshark configure issue

Hi Manik, 2017-10-25 16:54 GMT+02:00 Manik Khandelwal : > Hello all, > While building wireshark on Ubuntu 16.04, I successfully generated > configure file. Unfortunately encountered the following error: > > *checking for LIBGCRYPT - version >= 1.4.2... no* > >

[Wireshark-dev] Wireshark configure issue

Hello all, While building wireshark on Ubuntu 16.04, I successfully generated configure file. Unfortunately encountered the following error: *checking for LIBGCRYPT - version >= 1.4.2... no* *configure: error: libgcrypt not found; install libgcrypt-devel package for your system* I do however

Re: [Wireshark-dev] asn2wrs: autodetection for 64 bits X constrained integers

Hi Pavel, 2017-10-25 8:34 GMT+02:00 Pavel Strnad : > Hi list, > can we improve auto detection for 64b variant of constrained integers? > In the master branch we handle the cases of integers over/under +/- 2^32 > but > what about MIX.. and ..MAX constants? > There are such

[Wireshark-dev] asn2wrs: autodetection for 64 bits X constrained integers

Hi list, can we improve auto detection for 64b variant of constrained integers? In the master branch we handle the cases of integers over/under +/- 2^32 but what about MIX.. and ..MAX constants? There are such dissectors in our current source tree: h245, t125, x509,.. that should use 64b instead