Re: [Wireshark-dev] Is this a known problem?

Hi Richard, Yes, downgrade to 4.0.x, Windows 2012 is not supported with Qt 6 https://gitlab.com/wireshark/wireshark/-/issues/18476#note_1747847702 Next 4.2 will be check to don't install on Windows 2012 (and 8) On Thu, Feb 1, 2024 at 5:58 AM Richard Sharpe wrote: > Hi folks, > > I installed

Re: [Wireshark-dev] 4.2.0 release schedule

Hi Gerald, Look good for the planned release I hope only to have time to integrate the support of HTTP3 headers (with nghttp3) -> https://gitlab.com/wireshark/wireshark/-/merge_requests/9330 Cheers On Thu, Aug 17, 2023 at 11:04 PM Gerald Combs wrote: > Hi all, > > I'd like to start preparing

Re: [Wireshark-dev] Crash in RDP/EGFX dissector

Hi, Can you try to update the wireshark release ? (using PPA) https://launchpad.net/~wireshark-dev/+archive/ubuntu/stable Cheers On Fri, Jan 13, 2023 at 7:35 PM Cristian Constantin via Wireshark-dev < wireshark-dev@wireshark.org> wrote: > Hi! > > Wireshark crashes while decoding relatively

Re: [Wireshark-dev] Syncthing protocol dissector

Hi Thomas, We don't accept LUA dissector on source code But there is now a protobuff dissector on Wireshark and i think it will not be complicated to add this protocol. Cheers On Sun, Feb 27, 2022 at 5:39 AM Tmore1 wrote: > Hello, > > Several years ago, there was some discussion on this

Re: [Wireshark-dev] MPLS Echo Packet containing FEC stack change Sub-TLV in DDMAP TLV is not decoded by wireshark or https://hpd.gasmi.net/

Hi, Can you open an issue on wireshark gitlab ? With pcap file and link to spec. Cheers Le ven. 3 déc. 2021 à 17:26, max payne.. a écrit : > Hi, > > This is to inform you that we are supporting FEC Stack Change Sub-TLV in > DDMAP TLV. I have Hex Dump, which is correct as per my understanding

Re: [Wireshark-dev] Is there some reasonable way to split up epan/dissectors/packet-ieee80211.c into smaller files?

Hi Richard, yes, ieee802.11 dissector is big... do you have some idea how to split ? Cheers On Fri, Dec 3, 2021 at 12:16 AM Richard Sharpe wrote: > Hi folks, > > The IEEE802.11 dissector is becoming unwieldy. > > It is currently around 50,000+ lines of code! > > I am adding additional lines

Re: [Wireshark-dev] How to generate epan/dissectors/packet-skinny.c?

Hi Jirka, from packet-skinny.c.in # Dependencies: # - python2.x # - cog.py: (pip install cogapp / http://nedbatchelder.com/code/cog/) # - python.xml # - python.xml.sax # Tested on Ubuntu 18.04 (TLS) (with python2) and work for me.. On Sat, Oct 30, 2021 at 4:39 PM Jirka Novak wrote: > Hi, >

Re: [Wireshark-dev] Wireshark dissector does not match spec for IEEE P802.1AS-Rev/D8.0

Hi Ari, Can you open an issue on gitlab wireshark ? with a pcap and link to spec ? Cheers On Wed, Jan 20, 2021 at 5:46 PM Ari Timonen wrote: > Hello, > > The time synchronization protocol IEEE P802.1AS dissector does not parse > TLV flags correctly. > > The specification IEEE

Re: [Wireshark-dev] About i18n Translation

Hi Huang, Inline response. On Thu, Nov 19, 2020 at 2:54 PM qiangxiong.huang wrote: > HI, I have two questions about wireshark i18n: > > 1. Are the files *.po in debian/po only used in debian platform or all > platforms (like windows)? > it is only for debian for the moment (for packaging

Re: [Wireshark-dev] Is there a way to internationalize the text of dissector's preference?

Hi, It is possible, you can push a patch (with WIP status) for looking ? On Fri, Nov 6, 2020 at 2:26 PM qiangxiong.huang wrote: > Hi, Alexis La Goutte > > I just want to internationalize for the title and description of > preference in packet-xxx.c. > Is this possible to u

Re: [Wireshark-dev] Is there a way to internationalize the text of dissector's preference?

Hi Huang, No, there is a actually no way for translate packet-xxx.c files Cheers On Thu, Nov 5, 2020 at 2:31 PM qiangxiong.huang wrote: > It seems that only qt releated code (in .cpp) can be internationalized by > QString::tr(). > Is there a way to internationalize the text of dissector

Re: [Wireshark-dev] Possible bug (Wireshark blocking VPN traffic)

Hi Binarus, it is better to post on Wireshark GitLab BugTracker but in your case, i think it is a capture issue coming from npcap and it will be better to post on npcap github issue (What the release of npcap ?) Cheers On Mon, Oct 5, 2020 at 3:06 PM Binarus wrote: > Dear Wireshark developers,

Re: [Wireshark-dev] Why is conflict check on the buildbot green?

Hi Jaap, It is beacuse all issue are not yet fixed (some coming from generated code... or missing spec info to known what the correct fix). Personally, when review code after Petri dish, I try to look different output log, because I know don’t fail it is juste warning. Le dim. 5 juil. 2020 à

Re: [Wireshark-dev] +BIEV dissection improvements

Hi Damian, I think, it will be better to open a issue on bugtracker with the pcap Cheers On Thu, Jun 4, 2020 at 8:49 PM Damian Stevenson wrote: > Sorry for the duplicate mail, Gmail app is a mess and doesn't allow to > convert to plain text. > > Would to request improvements on HFP

Re: [Wireshark-dev] Regenerating packet-parlay.c

Hi, I have already on the past try to rebuild parlay and remember i don't get the same output... but like Luke say, it will be coming from dict don't sort correctly Luke, can you push your ./idl-regen on CMakeList.txt ? we can (need) to add a step on buildbot for rebuild (all)dissector and check

Re: [Wireshark-dev] Contribute to project

Hi, for update wiki page, you need to create a account on wiki and ask for edit page. For translation, the translation is managed by Transifex, i see your ask to translate Russian, i have valid your account. Cheers On Sat, May 2, 2020 at 5:41 PM Елисеев Дмитрий wrote: > Hello, > > I want to

Re: [Wireshark-dev] Windows uninstaller doesn't remove translations.

Hi Chris, Can you push the fix on Gerrit ? Cheers On Thu, Mar 26, 2020 at 1:27 AM Maynard, Chris via Wireshark-dev < wireshark-dev@wireshark.org> wrote: > I’m building Wireshark on Windows, but I’ve upgraded Qt to 5.12.7. > Everything is fine except when uninstalling Wireshark. It seems that

Re: [Wireshark-dev] Lua Example in Wiki - broken link

Hi Adam, it is good ! On Sun, Feb 16, 2020 at 6:18 PM Adam Baxter wrote: > Hi all, > > https://wiki.wireshark.org/Lua/Examples has a link to > https://wiki.wireshark.org/Lua/Examples?action=AttachFile=get=dissector.lua > which in turn contains a link to >

Re: [Wireshark-dev] I have some captures from Jouni's hwsim for 802.11 with Anti-Clogging tokens

Hi Richard, On bugtracker or wiki... On Sun, Feb 16, 2020 at 6:52 PM Richard Sharpe wrote: > Hi folks, > > How do I get these into the collection? > > -- > Regards, > Richard Sharpe > (何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者) > ___ >

Re: [Wireshark-dev] Wireshark, low MSS and CVE-2019-11477, 11478 and 11479

Hi Chris, I think, it is a good idea and no too complicated to implement ! Cheers On Mon, Feb 10, 2020 at 8:58 PM Maynard, Chris via Wireshark-dev < wireshark-dev@wireshark.org> wrote: > In light of these 3 CVE’s, CVE-2019-11477, 11478 and 11479[3], and the > apparently effective work-around

Re: [Wireshark-dev] Request for a Wireshark Update to support TEAP traffic analysis.

Hi Nikhil, can you create a bug on BugTracker and attach the pcap ? it will look for add TEAP support Cheers On Fri, Feb 7, 2020 at 4:33 PM Nikhil Jadhav wrote: > Hello Developers, > > > > I am working on Cisco ISE and I find the Wireshark tool very beneficial to > analyze different packets.

Re: [Wireshark-dev] Standard defined field names in Wireshark dissectors

Hi, We have already make some big change for Wireless (remove mgmt on display filter) and no really a big issue... About standard for display filter and display filler name, it is complicated... for USB specification, the standard descriptors is not really "name" (bXXXId...) Cheers On Sun, Jan

Re: [Wireshark-dev] Wiki editor request

Hi Tomasz, it is good ! On Thu, Jan 2, 2020 at 11:37 AM Tomasz Moń wrote: > Hello, > > I have just registered at the Wireshark wiki. My username is > TomaszMon. Please add me to the EditorGroup. > > Best Regards, > Tomasz Moń >

Re: [Wireshark-dev] PIM: Support for dissection of PIM Flooding Mechanisme (PFM)

Hi Anders, It is always interressing to include new RFC on Wireshark Please push on upstream (you can look the wiki about help) Cheers On Wed, Dec 25, 2019 at 9:52 PM Anders Reggestad wrote: > Hi, > > I have as part of a study of the RFC8364, written a dissection of the PFM > message from

Re: [Wireshark-dev] Wireshark 3.1.0 No filter available, try another column

Hi Richard, What the type of this field ? On Thu, Nov 7, 2019 at 9:17 AM Richard Sharpe wrote: > Hi folks, > > With 3.1.0, I see the message displayed in yellow any time I try Right > Click on a field, then Apply as Filter->Selected. > > Is that functionality broken in 3.1.0? > > The version

Re: [Wireshark-dev] Plugin question : proto_tree_add_oid() is not exported

Hi Koji, I think, it is a bug (or the author only forget to export) You can push a patch on gerrit and it will be available on next major release Cheers On Thu, Nov 7, 2019 at 3:30 PM kyossi wrote: > Hi, > > I'm developing custom plugin dll which dissect snmp-like >

Re: [Wireshark-dev] IEEE 802.15.4e support

Hi Devan, i think, it is better solution 2, if the 2 patch are on the same branch, Gerrit will be say, there is some related change Cheers On Wed, Oct 2, 2019 at 3:12 AM Devan Ming-Kin Lai < dev...@davisinstruments.com> wrote: > Hi, > > > > I’ve been working with a device that uses IEEE

Re: [Wireshark-dev] issue: SMB2: The value of "Fixed Part Length" seems wrong

Hi Zhai, Can you open a issue on bug tracker and a pcap ? https://bugs.wireshark.org You can also push a fix directly on Gerrit https://code.wireshark.org/review and look for help https://wiki.wireshark.org/Development/SubmittingPatches Cheers On Tue, Sep 24, 2019 at 1:06 PM Xuan k wrote: >

Re: [Wireshark-dev] Field with flags dissected

Hi Look proto_tree_add_bitmask_with_flags and there is a flag for don't append the top Cheers On Sat, Aug 10, 2019 at 12:48 AM Crawford, Anthony R < anthony.r.crawf...@charter.com> wrote: > Hi all, > > I need some help dissecting a field with its flags. I am trying to present > the dissection

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

Hi, i like the idea and for me it is not a problem (and yes it will be better to use credential and not password...) For example, there is tools like NetworkMiner and it is not a hacking tools... Cheers On Fri, Jun 14, 2019 at 10:26 PM Roland Knall wrote: > Hi > > There is a patch currently

Re: [Wireshark-dev] Getting an error in code I did not touch ...

Clang builder with Extra warning is not happy too simple_dialog.cpp:54:68: warning: extra ';' after member function definition [-Wextra-semi] it will be fix on https://code.wireshark.org/review/33283 On Mon, May 20, 2019 at 7:08 PM Richard Sharpe wrote: > Hi folks, > > I am getting the

Re: [Wireshark-dev] Duplicate fields

Hi Dario, it is supported. It is only not recommanded (not supported ?) to have a same display field for 2 fields with different Frame Type (there is a check on Petri Dish...) On Thu, May 2, 2019 at 11:19 AM Dario Lombardo wrote: > Hi > I'm working on bug 15719 (duplicate fields in

Re: [Wireshark-dev] IKEv2/ESP decryption preference inconsistency

Hi Michael, i think coming from 2 differents implementors... Cheers On Fri, Apr 12, 2019 at 1:35 AM Michael Lum wrote: > Hi, > > we just started trying to decrypt IKE/ESP packages and have it working > successfully but > found that the preference settings appear to be inconsistent. > > The

Re: [Wireshark-dev] Covery Scan for Windows Wireshark builds

Hi Tomasz, There is actually no Coverity Scan for Windows... but can be a good idea to add this ! Cheers On Sun, Apr 14, 2019 at 9:49 AM Tomasz Moń wrote: > Hello, > > I checked the Wireshark Coverity Scan defects and noticed that they > all seem to be from Linux build. > > If above

Re: [Wireshark-dev] IEEE 802.11 WPA3 decryption support

Hi Mikael, Good idea ! (if remember dot11crypt coming from time where it is AirPcap stuff... with offloading decryption...) On Mon, Mar 25, 2019 at 10:33 AM Kanstrup, Mikael wrote: > Hi, > > I started working on WPA3 decryption support. Some parts of it has already > been merged. While

Re: [Wireshark-dev] Exposing ieee802.11 reason codes outside of dissect-ieee80211.c

There is no a packet-ieee80211.h ? for extern ? On Fri, Mar 8, 2019 at 8:11 AM Jaap Keuter wrote: > Hi Richard, > > It’s not ideal, but not unheard of, so I don’t see why it can’t be done > here. > > Thanks, > Jaap > > > On 8 Mar 2019, at 04:32, Richard Sharpe > wrote: > > > > Hi folks, > > >

Re: [Wireshark-dev] Npcap 0.9-r9 causing WiFi disconnect?

Hi, No issue for me too (with Windows 10 1803 x64). What the user enable for npcap installation ? (because there is some specific WiFi parameter settings...) Cheers On Wed, Mar 6, 2019 at 10:08 AM Pascal Quantin wrote: > Hi Anders, > > I do not face such issue with my Windows 10 1809 x64

Re: [Wireshark-dev] What flags do I need to cmake to get the build to show me warnings etc in the changes?

Hi Richard, You need to add -DENABLE_EXTRA_COMPILER_WARNINGS=on to your cmake. Cheers On Sun, Mar 3, 2019 at 6:18 PM Richard Sharpe wrote: > Hi folks, > > I want to find more of the problems before I send them in for review. > > What flags do I need on cmake or whatever to show me more

Re: [Wireshark-dev] The 802.11 dissector is a big hairy ball of wax that needs to be refactored in some way

Hi Richard, Yes, ieee80211 is a big dissector.. I think, it will be may be possible to split some code between multiple file.. May be need to add more comment with the list of supported attribut (or a wiki page with info about the dissector) On Thu, Jan 3, 2019 at 6:07 PM Richard Sharpe

Re: [Wireshark-dev] 2.9.0 and 3.0.0 release schedule

Wednesday, December 12, 2018 12:40 PM > > > To: Developer support list for Wireshark < > wireshark-dev@wireshark.org > > <mailto:wireshark-dev@wireshark.org>> > > > Subject: Re: [Wireshark-dev] 2.9.0 and 3.0.0 release schedule > > > >

Re: [Wireshark-dev] 2.9.0 and 3.0.0 release schedule

+1 for delayed the 3.0 release Always kept a 2.9 for this week and only branch after some feature (like Profile Manager...) merged (For middle of Junary ?) Cheers On Wed, Dec 12, 2018 at 2:50 PM Roland Knall wrote: > I would also like to get at least the Profile Manager in 3.0, which would >

Re: [Wireshark-dev] Latest transifex update

Hi Uli, Yes, i have see too... There is a issue with sync translation with master-2.6 (i have push some patch last week but don't work better...) On Sun, Dec 9, 2018 at 12:01 PM Uli Heilmeier wrote: > Hi, > > with today's automated Transifex update the master-2.6 branch lists 2880 >

Re: [Wireshark-dev] Annoying deviances from the 802.11-2016 spec in the names of cipher suites

Hi Richard, See inline, On Thu, Nov 29, 2018 at 4:49 PM Richard Sharpe wrote: > Hi folks, > > I notice that the names used in the code for the 802.11 dissector > deviate in annoying ways from IEEE 802.11-2016. > > For example: > > static const value_string ieee80211_rsn_cipher_vals[] = { >

Re: [Wireshark-dev] More Lua tests needed

Hi Richard, May be a good idea to open a issue on bugtracker for don't forget... On Wed, Oct 17, 2018 at 12:00 AM Richard Sharpe wrote: > Hi folks, > > During testing of my changes to add support for Range Strings to the > Lua support I found that there was a serious bug in the support for >

Re: [Wireshark-dev] While there is a val64_string structure and functions, there is no ran64_string

On Tue, Oct 16, 2018 at 9:28 PM Richard Sharpe wrote: > Hi folks, > > I see that there is a val64_structure and various functions using it > there seems to be no ran64_string (the 64-bit version of > range_strings). > > Is that because no one has needed it until now? > I think, it is because no

Re: [Wireshark-dev] Editor group permission request

Hi Alex, It is good ! Cheers On Mon, Oct 8, 2018 at 7:14 PM Alex Hammer wrote: > Hi, I've used the content in the Wireshark wiki for a while now and I'd > like to be able to help fix errors that I run across or supplement the > content. I created the username AlexHammer - would you please

Re: [Wireshark-dev] tools/check[hf|APIs|filtername].pl need updating?

Thanks Jakub for historic I think a good idea is revert to use "standard" API or write a tools for convert old dissector to new API... Cheers On Tue, Sep 18, 2018 at 6:05 PM Jakub Zawadzki wrote: > Hi, > > W dniu 2018-09-18 16:56, Maynard, Chris napisał(a): > > While investigating the

Re: [Wireshark-dev] Cannot push patch to Gerrit - Found WIP commit

Hi, You need to replace the username by your gerrit username... Cheers On Wed, Sep 5, 2018 at 5:39 PM Andrii Vladyka wrote: > I am trying to push a patch (single commit on top of the latest master > branch) with the following syntax: > > git push

Re: [Wireshark-dev] Why is my petri-dish build failing?

On Thu, Aug 2, 2018 at 7:14 AM Maynard, Chris wrote: > > -Original Message- > > From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On > > Behalf Of Richard Sharpe > > Sent: Thursday, August 2, 2018 12:22 AM > > To: Developer support list for Wireshark > > Subject:

Re: [Wireshark-dev] Lua update?

On Thu, Jul 12, 2018 at 8:48 PM Pascal Quantin wrote: > > > Le jeu. 12 juil. 2018 à 20:44, Pascal Quantin > a écrit : > >> Hi Chris, >> >> Le jeu. 12 juil. 2018 à 20:30, Maynard, Chris < >> christopher.mayn...@igt.com> a écrit : >> >>> Is there any particular reason why Wireshark for Windows

Re: [Wireshark-dev] Support for WLAN SSID Parameter

Hi, Please open a bug with pcap on the bugtracker ( https://bugs.wireshark.org ) Cheers On Mon, Jun 18, 2018 at 4:24 PM James Zoll wrote: > To whom it may concern, > Wireshark told me to contact you for support on this: > Dessector for 802.11 IE Tag (SSID Parameter set) code not implemented,

Re: [Wireshark-dev] UTF-8 SSIDs in 802.11

Hi Richard, i will not be a bad idea i think. Cheers On Thu, Mar 8, 2018 at 4:50 AM, Richard Sharpe wrote: > Hi folks, > > Someone has suggested that perhaps this is not appropriate: > > gchar *ssid; /* The SSID may consist of arbitrary bytes */ > > because if

Re: [Wireshark-dev] donation to menagerie?

Hi Ed, You can * Add pcap on wiki * Create a new issue on bugtracker and attach your pcap... Both case, will be include on menagerie.. On Tue, Mar 6, 2018 at 9:12 PM, Ed Beroset wrote: > I submitted a tiny patch to address a particular need I saw recently. ( >

Re: [Wireshark-dev] Seeing these errors with packet-quic.c because I don't have certain libraries ...

On Thu, Mar 1, 2018 at 5:27 PM, Richard Sharpe wrote: > Hi folks, > > Seeing this. Maybe need some _U_ on those parameters? Looks like the > ifdef is causing it because I don't have the latest libraries. > > packet-quic.c: In function 'dissect_quic_initial': >

Re: [Wireshark-dev] Should I be creating review requests for 2.5.x for the 802.11ax code changes?

Hi Richard, There is not yet a 2.5 dedicated branch (it is always master branch) and the next branch(ing) will be for 2.6 (master-2.6) on next month ! On Sun, Feb 25, 2018 at 11:42 PM, Richard Sharpe < realrichardsha...@gmail.com> wrote: > Hi folks, > > Now that 2.5 appears to have branched,

Re: [Wireshark-dev] Why does Gerritt sometimes allow a merge but other times want a cherry-pick?

Hi Richard, it is because it is not possible to merge without (manual) modification. You need to make a manual cherry-pick go on master-2.4 branch git checkout master-2.4 and cherry-pick change git cherry-pick -x commitid Cheers On Fri, Feb 23, 2018 at 11:18 PM, Richard Sharpe <

Re: [Wireshark-dev] APT clang

Fixed for me too :-) On Fri, Feb 23, 2018 at 4:54 PM, Graham Bloice wrote: > > > On 23 February 2018 at 15:32, Dario Lombardo > wrote: > >> I've contacted the mantainer of the repo, and he confirmed some network >> issue. They're

Re: [Wireshark-dev] Regenerate asn dissector

use make on asn1 folder ? On Mon, Feb 19, 2018 at 1:55 PM, Dario Lombardo wrote: > Hi > I've modified epan/dissectors/asn1/snmp/packet-snmp-template.c and I want > to regenerate the corresponding dissector. > I've found the cmake target

Re: [Wireshark-dev] report from the bleeding edge (VS 2017)

On Thu, Feb 15, 2018 at 2:15 AM, Gerald Combs wrote: > On 2/14/18 2:27 AM, Pascal Quantin wrote: > > > > > > 2018-02-14 11:24 GMT+01:00 Graham Bloice > >: > > > > > > > > On 14 February 2018 at 06:24,

Re: [Wireshark-dev] Names longer than 8 characters in manuf file

Hi Justin, it is a known issue and it is fixed on next release (2.5.x) https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3666 Cheers On Tue, Feb 13, 2018 at 7:52 PM, M. Justin wrote: > I was looking through the Wireshark manufacturer database manuf >

Re: [Wireshark-dev] QCustomPlot 2.0.0

r 3.0 >>> >>> cheers >>> Roland >>> >>> On Sat, Feb 10, 2018 at 11:23 AM, Martin Mathieson via Wireshark-dev < >>> wireshark-dev@wireshark.org> wrote: >>> >>>> Thanks Alexis, I had not seen your earlier draft..

Re: [Wireshark-dev] QCustomPlot 2.0.0

Hi, I have already try on 2016 (when there is qcustomplot 2.0 beta) (published my old draft > https://code.wireshark.org/review/#/c/17980/ ) But there is some issue (some change on function and need to reapply some wireshark patch if i remenber..) But qcustomsplot 2.0 is compatible with Qt 4.8

Re: [Wireshark-dev] 2.5.0, 2.6, and 3.0 release planning

On Fri, Feb 2, 2018 at 11:45 PM, Gerald Combs wrote: > I think we've fixed the major issues identified by Stig, Jim, and others > so I'd like to release 2.5.0 on February 6. This would let us release 2.6.0 > this spring, followed by 3.0.0 in the fall: > > > March: Create

Re: [Wireshark-dev] Outstanding changes I would like to get in ...

Hi Richard, the 2.5.0 is dev release (pre-beta or RC...) it will be possible to merge enhance and fix for final release (2.6) on May/June. Cheers On Fri, Jan 19, 2018 at 7:18 PM, Richard Sharpe wrote: > Hi folks, > > I have the 802.11ax stuff that would be good

Re: [Wireshark-dev] 2.5.0 release on January 16

On Wed, Jan 17, 2018 at 1:39 PM, Anders Broman wrote: > > > -Original Message- > From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On > Behalf Of Gerald Combs > Sent: den 17 januari 2018 02:05 > To: Developer support list for Wireshark

Re: [Wireshark-dev] Handling weight for PRIORITY and HEADERS frames for HTTP2 with lua

Hi Alexander, No problem, you can push a fix with this enhance ! Cheers On Fri, Dec 22, 2017 at 1:19 AM, Alexander Gryanko wrote: > Hello, > > When I try to dissect HTTP2 messages, I found one confusing thing. Here is > a definition of fields: > > { _http2_weight, > {

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] Making oui_base_custom available more generally

On Sat, Aug 19, 2017 at 2:19 PM, Michael Mann via Wireshark-dev < wireshark-dev@wireshark.org> wrote: > If you're talking about oui_base_custom(), I think the better idea would > be to create a field type (FT_OUI) for it. > Yes it is a idea but a BASE_OUI with VALS() (and use FT_UINT24) will be

Re: [Wireshark-dev] Vendor-specific dissectors for 802.11

On Sun, Aug 13, 2017 at 8:14 PM, Richard Sharpe wrote: > On Sun, Aug 13, 2017 at 11:04 AM, Michael Mann via Wireshark-dev > wrote: > > See https://code.wireshark.org/review/23065 > > > > It could probably use some review for "naming".

Re: [Wireshark-dev] Hierarchy of fields & offsets again, more potential offenders

On Wed, Aug 9, 2017 at 7:05 PM, Pascal Quantin wrote: > Hi Stig (and Sake), > > 2017-08-02 22:24 GMT+02:00 Stig Bjørlykke : > >> On Wed, Aug 2, 2017 at 10:03 PM, Sultan, Hassan via Wireshark-dev >> wrote: >> > Regarding

Re: [Wireshark-dev] Hierarchy of fields & offsets again, more potential offenders

On Tue, Aug 8, 2017 at 12:29 AM, Sultan, Hassan via Wireshark-dev < wireshark-dev@wireshark.org> wrote: Hi Hasan, Can you share your tools ? i can be add to wireshark for found some violation/error... Coming back on this and how to solve it, here's a suggestion I have, let me > know what you

Re: [Wireshark-dev] Wireshark 2.5.0 ws.css errors in docbook\developer_guide_chm.vcxproj

Hi, Please, it is a better to open a bug on bugtracker (for don't forget...) Cheers On Tue, Jul 25, 2017 at 10:07 PM, Jay Turner wrote: > ws.css has errors on lines 107 (body pre) and 116 (tt.literal, > code.literal where color 333 is written, but color code 333 is not

Re: [Wireshark-dev] Wireshark support for Qt4.8

On Mon, Jul 24, 2017 at 3:34 PM, Roland Knall wrote: > Hi > > Wireshark master currently does not build with Qt 4.8. The reason for > that, can be seen in > > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13909 > > These issues should be fixed in the near future. But it

Re: [Wireshark-dev] Problem while compiling wireshark master

On Mon, Jul 24, 2017 at 9:48 AM, Roland Knall wrote: > Hi > > This is not an issue with wireshark code, but rather with the version of > flex used by the compiler. See https://github.com/westes/flex/commit/ > 8c098febc9a599397921e9b6938b7fb85e38cc7e for a commit fixing this

Re: [Wireshark-dev] docker image

There is a docker wsbuilder image from Roland https://www.wireshark.org/lists/wireshark-dev/201610/msg7.html On Tue, Jul 18, 2017 at 11:50 AM, Graham Bloice wrote: > > > On 18 July 2017 at 10:30, Anders Broman > wrote: > >> >> >>

Re: [Wireshark-dev] Diameter SH-Interface User Data (AVP 702) is not decoded stiil in the latest version

Hi, Please open a bug ( https://bugs.wireshark.org ) with a pcap sample it is the better solution to get a fix Cheers On Mon, Jul 10, 2017 at 9:49 AM, Ariel Burbaickij < ariel.burbaic...@gmail.com> wrote: > Hello mailing list, > > somehow my previous e-mail in April 2017 did not get through to

Re: [Wireshark-dev] Alternatives to atoi and tolower

On Fri, Jul 7, 2017 at 10:52 AM, Roland Knall wrote: > More generic answer, please always take a look in wsutil and glib > documentation for things like that. Those functions are usually accepted > (with a few exceptions in glib I think). > May be we can add a chapter on

Re: [Wireshark-dev] Problem while compiling wireshark master

On Tue, Jul 4, 2017 at 2:19 PM, Pascal Quantin wrote: > Guy, do you remember because of which libnl version you moved net/if.h > inclusion after libnl ones in 592a0fcf04c3f7f9f23476525877763303a1a87d? > Should we include net/if.h first when compiling with libnl3 to cope

[Wireshark-dev] Rename QUIC dissector

Hi, I want (need) to rename the actual QUIC dissector to GQUIC Because there is a new QUIC(-IETF) protocol with some big change... (not the same packet header..., endian type...) I already start to talk with Peter of this subject and it think, it will be a good idea to include this change in

Re: [Wireshark-dev] Switch master and master-2.4 to Visual Studio 2015?

On Wed, Jun 7, 2017 at 1:11 AM, Gerald Combs wrote: > We currently build all of our Windows packages using Visual Studio 2013. > Unless anyone has any objections I'd like to switch the master and > master-2.4 builders to Visual Studio 2015 Update 3 ahead of the 2.4 release.

Re: [Wireshark-dev] Compilation issue on Mac OS

Hi, Do you have try with cmake ? On Thu, Apr 20, 2017 at 10:33 PM, ajay saxena wrote: > Hi, > > I am trying to compile wireshark from source that I took from github. I > have libgcrypt on my system and the configure script was able to find it. > However when I actually

Re: [Wireshark-dev] The build broke on the recent X11 changes

Hi Jaap, What release of gcc do you are using ? (i think a recent release...) On Tue, Apr 18, 2017 at 6:34 PM, Jaap Keuter wrote: > Hi, > > I get this building Wireshark: > > make[6]: Entering directory '/home/jaap/src/wireshark/ > master/epan/dissectors' > CC

Re: [Wireshark-dev] Change in wireshark[master]: Add support for BASE_VALS_NO_UNKNOWN

On Tue, Apr 11, 2017 at 12:19 AM, Guy Harris wrote: > On Apr 10, 2017, at 1:31 PM, Michael Mann (Code Review) < > code-review-do-not-re...@wireshark.org> wrote: > > > Michael Mann has submitted this change and it was merged. > > > > Change subject: Add support for

Re: [Wireshark-dev] attribution/copyright

On Fri, Apr 7, 2017 at 10:22 AM, Dario Lombardo wrote: > If I'm not mistaken, the authors list is generated by the commit log. > Yes, I confirm but for start of file (with list of dissectors...), we need to manual update ! > > On Fri, Apr 7, 2017 at 12:12 AM,

Re: [Wireshark-dev] Adding libxml2 as optional Wireshark dependency

Hi, There is some dissector using XML ? (diameter...) May be see to convert (or using actual XML code) Cheers On Wed, Apr 5, 2017 at 3:48 PM, Pascal Quantin wrote: > Hi Ahmad and Graham, > > 2017-04-05 15:38 GMT+02:00 Graham Bloice : > >>

Re: [Wireshark-dev] dissectors update: create a branch or not?

Hi Nicolas There is no really branch with Gerrit... You need to push direclty on master (and after fix it is bug fix, i will be backport to other branch) Cheers On Fri, Mar 31, 2017 at 5:43 PM, Bertin Nicolas < nicolas.ber...@al-enterprise.com> wrote: > Hi, > > > I'm updating the dissectors

Re: [Wireshark-dev] RTP player - a suggestion

On Mon, Mar 27, 2017 at 9:33 PM, Jirka Novak wrote: > Hi, > > >> I disagree. Right now, the GTK RTP player is the only one that I > consider usable. By comparison, the Qt RTP player only barely works, and > is unusable if you're dealing with more than one stream. If

Re: [Wireshark-dev] Default snaplen in man page

Hi Martin, Yes, there is a bug on man (forget to update after last update... https://code.wireshark.org/review/2658 ) You can open a bug or push directly on fix. Cheers On Mon, Mar 27, 2017 at 9:46 AM, Martin Sehnoutka wrote: > Hello, > > I'm investigating why Wireshark

Re: [Wireshark-dev] Ubuntu PPAs

Nice works Thanks Balint ! On Tue, Mar 14, 2017 at 12:29 AM, Bálint Réczey wrote: > Hi, > > I have created a separate PPA for backported dependencies of Wireshark: > https://launchpad.net/~wireshark-dev/+archive/ubuntu/wireshark-deps > > This would help people running

Re: [Wireshark-dev] HP ERM

Hi Gene, On Mon, Feb 20, 2017 at 2:05 PM, Gene Cumm wrote: > First, thanks for WireShark and granting my access request. > Welcome :-) > > Second, I've found out more about the HP ERM format. The most > significant bit of hp_erm.unknown3 indicates if the frame was

Re: [Wireshark-dev] EditorGroup request - geneC

Hi Gene, It is good. Cheers On Sat, Feb 18, 2017 at 7:19 PM, Gene Cumm wrote: > I'd like to create a page for the HPERM (Hewlett-Packard Encapsulated > Remote Mirroring) protocol and this requires membership to the > EditorGroup. Could I get access from wiki account

Re: [Wireshark-dev] Release package for Mac

On Sun, Feb 12, 2017 at 7:18 PM, Jaap Keuter wrote: > > > On 10 Feb 2017, at 21:07, Simon Barber wrote: > > > > How do I build an installer for Mac? > > > > make package generates something weird, and make dmg_package requires > PackageMaker > > >

Re: [Wireshark-dev] Preferences dialog width - GTK interface

On Mon, Feb 6, 2017 at 7:43 AM, Jaap Keuter <jaap.keu...@xs4all.nl> wrote: > > > On 6 Feb 2017, at 00:08, Peter Wu <pe...@lekensteyn.nl> wrote: > > > > On Sun, Feb 05, 2017 at 10:42:32PM +0100, Jaap Keuter wrote: > >> On 05-02-17 21:28, Alexis La Gou

Re: [Wireshark-dev] Preferences dialog width - GTK interface

On Sun, Feb 5, 2017 at 7:52 PM, Jaap Keuter wrote: > Hi, > > Does anyone else get ridiculous wide (as in over 2000 px wide) preference > dialog > on GTK development build? > It seems that the new 'title only' preferences, of RDP, DAP, SAP, etc, are > long > lines, which

Re: [Wireshark-dev] Bugzilla SSL Issue?

Need a update of Cloudflare configuration... On Fri, Jan 20, 2017 at 4:06 PM, Graham Bloice wrote: > On 20 January 2017 at 15:04, Pascal Quantin > wrote: > >> >> >> 2017-01-20 15:59 GMT+01:00 João Valverde >

Re: [Wireshark-dev] please add wiki account PaulWise to EditorGroup

Hi Paul, I will be good. Cheers On Thu, Jan 19, 2017 at 9:24 AM, Paul Wise wrote: > Hi all, > > Please add my wiki account (PaulWise) to the EditorGroup so that I can > modify the Git page to link to the protocol documentation. > > -- > bye, > pabs > >

Re: [Wireshark-dev] git-review fails with an SSL error

and also under linux if you don't have Change-Id, there is warning about this... On Wed, Jan 18, 2017 at 4:09 PM, Paul Offord wrote: > OK - I think I must have missed the git review -s step. I thought I'd > followed the instructions to the letter but I must admit that

Re: [Wireshark-dev] Packet sample repository/library?

Hi, No see a Pull Request for the moment... On Sat, Jan 14, 2017 at 3:14 PM, Jirka Novak wrote: > Hello, > > did anyone reviewed my proposed changes in happy-shark? > > Sincerely yours, > >

Re: [Wireshark-dev] Allowing --with-release to take hex strings ...

Hi Richard, I think it is not a problem... Please push your fix on Gerrit On Wed, Jan 11, 2017 at 10:29 PM, Richard Sharpe < realrichardsha...@gmail.com> wrote: > Hi folks, > > Does anyone have a problem with a change like this: > > diff --git a/configure.ac b/configure.ac > index

Re: [Wireshark-dev] Remote Control Plugin - Can I submit to the Wireshark project

Hi Paul (and others) for disable when code will be review, we can help you to add this "feature" About sharkd for me, it is different because sharkd is for a web wireshark (like CloudShark) Cheers On Sun, Jan 8, 2017 at 12:03 PM, Paul Offord wrote: > Hi Dario, > > >

  1   2   3   4   5   6   >