Re: [Wireshark-dev] Description of Wireshark User's Guide 4.3.0
Hi Machiko, it seems this Guide did not always evolve at the same pace than the implementation for this part. I confirm that in fact a Spurious Retrans cannot be SYN or FIN flagged as it is an ordinary data packet for which Wireshark has already seen an acknowledgement ( = that ACK was either lost, ignored by the its receiver, or received too late ). The whole interpretation is built on what's in the capture obviously, but also on what could be missing (from sequence or ack gaps), hence some difficulties maybe to document with only 2-3 conditions what triggers such packet marks. regards E.A. Le lun. 6 nov. 2023 à 17:31, Machiko Ichihashi a écrit : > > To whom it may concern, > > > > My name is Machiko Ichihashi, and I work as an engineer in Japan. > > I use Wireshark for my work, and I want to express my gratitude for its > usefulness. > > > > I would like to ask for an explanation of the specifications described in > Wireshark User's Guide 4.3.0. > > TCP Spurious Retransmission > > https://www.wireshark.org/docs/wsug_html_chunked/ChAdvTCPAnalysis.html > > I would like to request a clarification regarding a specification mentioned > in the Wireshark User's Guide 4.3.0. > > > > In this section, the first condition states, > > "The SYN or FIN flag is set." > > Is this condition really necessary? > > It seems that these packets should be required to be data packets, so I don’t > think the SYN or FIN flags are necessary. > > > > Could you please confirm this? > > > > Regards, > > Machiko Ichihashi/TOYO Corporation > > > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] DBUILD_logray=ON breaks linking
*"When linking with DBUILD_logray=ON, there won't be a WiresharkMainWindow,
will there?"*
Both are built.
Finally, as both logray and wireshark have the same parent class, I could
move the implementation and just call the parent and all is now working.
Le mar. 27 sept. 2022 à 16:38, chuck c a écrit :
>
> https://gitlab.com/wireshark/wireshark/-/blob/19b04bf5ed906a1c03854595d424ad1e13f17df9/ui/qt/protocol_preferences_menu.cpp
> WiresharkMainWindow* ptest;
> ptest = new WiresharkMainWindow(
> QApplication::topLevelAt(parentWidget()->mapToGlobal(QPoint())) );
> ptest->removeAdditionalToolbar(QString("test compil"));
> delete ptest;
>
> When linking with DBUILD_logray=ON, there won't be a WiresharkMainWindow,
> will there?
>
> It should be LograyMainWindow?
>
> https://gitlab.com/wireshark/wireshark/-/blob/master/ui/logray/logray_main_window.h
>
>
>
> On Tue, Sep 27, 2022 at 9:04 AM Eugène Adell
> wrote:
>
>> Yes Chuck, I did that multiple times, and just before pushing my latest
>> code.
>>
>> Le mar. 27 sept. 2022 à 15:57, chuck c a écrit :
>> >
>> > Since you have been working on it for a while, have you updated your
>> master and rebased the MR branch?
>> >
>> > On Tue, Sep 27, 2022 at 7:06 AM Eugène Adell
>> wrote:
>> >>
>> >> Hi all,
>> >>
>> >> I've been working on MR !2445 for a while and almost finished this
>> >> work, things were going rather well until DBUILD_logray=ON was added
>> >> on the "Job Code Checks + Clang Warnings" job. It's still compiling
>> >> and linking on my dev environment, but adding DBUILD_logray=ON is
>> >> reproducing the same error there, which indeed is mentionning logray :
>> >>
>> >> /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:296:
>> >> undefined reference to
>> >> `WiresharkMainWindow::WiresharkMainWindow(QWidget*)'
>> >> /usr/bin/ld:
>> /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:303:
>> >> undefined reference to `typeinfo for WiresharkMainWindow'
>> >> /usr/bin/ld:
>> /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:307:
>> >> undefined reference to `WiresharkMainWindow::frameDataForRow(int)
>> >> const'
>> >> /usr/bin/ld:
>> ui/logray/CMakeFiles/ui_logray.dir/__/qt/protocol_preferences_menu.cpp.o:
>> >> in function
>> `ProtocolPreferencesMenu::enumCustomTCPOverridePreferenceTriggered()':
>> >> /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:417:
>> >> undefined reference to `typeinfo for WiresharkMainWindow'
>> >> /usr/bin/ld:
>> /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:418:
>> >> undefined reference to `WiresharkMainWindow::frameDataForRow(int)
>> >> const'
>> >>
>> >> The failed pipeline is online :
>> >> https://gitlab.com/eugene.adell/wireshark/-/pipelines/650129481
>> >>
>> >> I haven't found anything in the mailing list archive, and searching in
>> >> the pipelines logs with a keyword isn't enabled, as a consequence I am
>> >> not able to find any support from similar previous experiences if so
>> >> happened for anyone.
>> >>
>> >> Any idea why this compiling flag is breaking and what to do then ?
>> >>
>> >> best regards
>> >> E.A.
>> >>
>> ___
>> >> Sent via:Wireshark-dev mailing list
>> >> Archives:https://www.wireshark.org/lists/wireshark-dev
>> >> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>> >> mailto:wireshark-dev-requ...@wireshark.org
>> ?subject=unsubscribe
>> >
>> >
>> ___
>> > Sent via:Wireshark-dev mailing list
>> > Archives:https://www.wireshark.org/lists/wireshark-dev
>> > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>> > mailto:wireshark-dev-requ...@wireshark.org
>> ?subject=unsubscribe
>>
>> ___
>> Sent via:Wireshark-dev mailing list
>> Archives:https://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>> mailto:wireshark-dev-requ...@wireshark.org
>> ?subject=unsubscribe
>>
> ___
> Sent via:Wireshark-dev mailing list
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org
> ?subject=unsubscribe
>
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] CARES to old for CentOS8?
Hello, did you try compiling c-ares from source code, then adding the generated lib to the system ( by adding a file /etc/ld.so.conf.d/ and updating the links with ldconfig -v ) ? I'm getting this when checking the above compilation/update, which finds the newly installed lib : # ldd /bin/wireshark | grep ares libcares.so.2 => /usr/local/c-ares_depl/lib/libcares.so.2 (0x7f3c55392000) Le mer. 28 sept. 2022 à 16:47, Anders Broman a écrit : > > Hi, > Is there a workaround for > CMake Error at > /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message): > Could NOT find CARES: Found unsuitable version "1.13.0", but required is at > least "1.14.0" (found /usr/lib64/libcares.so)? > I would like to build for CentOS8... > > Best regards > Anders > > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] DBUILD_logray=ON breaks linking
Yes Chuck, I did that multiple times, and just before pushing my latest code. Le mar. 27 sept. 2022 à 15:57, chuck c a écrit : > > Since you have been working on it for a while, have you updated your master > and rebased the MR branch? > > On Tue, Sep 27, 2022 at 7:06 AM Eugène Adell wrote: >> >> Hi all, >> >> I've been working on MR !2445 for a while and almost finished this >> work, things were going rather well until DBUILD_logray=ON was added >> on the "Job Code Checks + Clang Warnings" job. It's still compiling >> and linking on my dev environment, but adding DBUILD_logray=ON is >> reproducing the same error there, which indeed is mentionning logray : >> >> /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:296: >> undefined reference to >> `WiresharkMainWindow::WiresharkMainWindow(QWidget*)' >> /usr/bin/ld: /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:303: >> undefined reference to `typeinfo for WiresharkMainWindow' >> /usr/bin/ld: /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:307: >> undefined reference to `WiresharkMainWindow::frameDataForRow(int) >> const' >> /usr/bin/ld: >> ui/logray/CMakeFiles/ui_logray.dir/__/qt/protocol_preferences_menu.cpp.o: >> in function >> `ProtocolPreferencesMenu::enumCustomTCPOverridePreferenceTriggered()': >> /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:417: >> undefined reference to `typeinfo for WiresharkMainWindow' >> /usr/bin/ld: /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:418: >> undefined reference to `WiresharkMainWindow::frameDataForRow(int) >> const' >> >> The failed pipeline is online : >> https://gitlab.com/eugene.adell/wireshark/-/pipelines/650129481 >> >> I haven't found anything in the mailing list archive, and searching in >> the pipelines logs with a keyword isn't enabled, as a consequence I am >> not able to find any support from similar previous experiences if so >> happened for anyone. >> >> Any idea why this compiling flag is breaking and what to do then ? >> >> best regards >> E.A. >> ___ >> Sent via:Wireshark-dev mailing list >> Archives:https://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev >> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] DBUILD_logray=ON breaks linking
Hi all, I've been working on MR !2445 for a while and almost finished this work, things were going rather well until DBUILD_logray=ON was added on the "Job Code Checks + Clang Warnings" job. It's still compiling and linking on my dev environment, but adding DBUILD_logray=ON is reproducing the same error there, which indeed is mentionning logray : /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:296: undefined reference to `WiresharkMainWindow::WiresharkMainWindow(QWidget*)' /usr/bin/ld: /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:303: undefined reference to `typeinfo for WiresharkMainWindow' /usr/bin/ld: /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:307: undefined reference to `WiresharkMainWindow::frameDataForRow(int) const' /usr/bin/ld: ui/logray/CMakeFiles/ui_logray.dir/__/qt/protocol_preferences_menu.cpp.o: in function `ProtocolPreferencesMenu::enumCustomTCPOverridePreferenceTriggered()': /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:417: undefined reference to `typeinfo for WiresharkMainWindow' /usr/bin/ld: /home/eugene/wireshark/ui/qt/protocol_preferences_menu.cpp:418: undefined reference to `WiresharkMainWindow::frameDataForRow(int) const' The failed pipeline is online : https://gitlab.com/eugene.adell/wireshark/-/pipelines/650129481 I haven't found anything in the mailing list archive, and searching in the pipelines logs with a keyword isn't enabled, as a consequence I am not able to find any support from similar previous experiences if so happened for anyone. Any idea why this compiling flag is breaking and what to do then ? best regards E.A. ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] please close issue 12805
Hello, anyone with sufficient rights please close : https://gitlab.com/wireshark/wireshark/-/issues/12805 I didn't pay attention but it's in fact the very same than 16919 that was solved some time ago (cause : SRC < DST leading to a wrong identification of the conversation initiator). best regards E.A. ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] please close issue 12800
Hello, anyone with sufficient rights please close : https://gitlab.com/wireshark/wireshark/-/issues/12800 ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Status label for issues
Hello, "Furthermore a normal user is not allowed to set labels at the moment." That's true. How to request a "close issue" in the proper way ? Unluckily commenting is not always enough to get attention. For example, please anyone have a look at https://gitlab.com/wireshark/wireshark/-/issues/7580 and close it. About old issues, I hope they won't be closed too "fast" as they are one of my playgrounds ( https://gitlab.com/wireshark/wireshark/-/issues/6683 for example ). I understand you are speaking about issues needing requester information, and hopefully it won't catch legitimate ones. E.A. Le lun. 26 avr. 2021 à 21:17, Uli Heilmeier a écrit : > > > > Am 26.04.21 um 11:49 schrieb Roland Knall: > > > > I suggest we create a wiki page for that discussion first, and if we can > > figure that out create the labels. > > > > I've created > https://gitlab.com/wireshark/wireshark/-/wikis/Discussion-Issues-Labels to > discuss labels for issues. > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[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 the SampleCaptures page. > > Thanks for your contribution, > Jaap > > > On 8 Dec 2019, at 16:41, Eugène Adell wrote: > > > > Hi guys, > > > > I would like to add some captures on the dedicated wiki page. My > > username : EugeneAdell > > > > Or if you prefer to edit yourself, the captures are attached to this > > email (the old CHARGEN protocol, which has some educational value > > since it's a very simple one) > > > > best regards > > E.A. > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe daytime-tcp.pcap Description: Binary data time-udp.pcap Description: Binary data daytime-udp.pcap Description: Binary data echo-udp.pcap Description: Binary data time-tcp.pcap Description: Binary data echo-tcp.pcap Description: Binary data ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
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 wiretap code: > > if (... cv_hdr.year < 1970 || cv_hdr.year >= 2038 || ...) > > -- > Regards, > Richard Sharpe > (何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者) > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Season of Docs - Announcements] The 2021 Season of Docs application for organizations is open!
Hello, I don't see any mention to the doc/README.* files in this wiki, which are essential but sometimes a bit harsh. For example README.dissector is almost 4000 lines long without any Table of Content (but there's a numerotation for the paragraphs which could help building it), one doesn't always know how to deal with it. best regards E.A. Le ven. 19 févr. 2021 à 08:27, Alex Nik a écrit : > > Hi Moshe. > > I found some information for GSoD 2020 on the Wireshark wiki - there are more > ideas what to document on this page. It could be a good idea to apply for > GSoD 2021. > > Regards, > Alex > > On 11 Feb 2021, at 02:45, RAGE wrote: > > Hi Moshe. > > It is. For now I can see the wiki has outdated info or not has a description > at all for some technologies and tools the Wireshark project accumulates.. my > after project time I would still want to help with it's improvement if I can. > But if you want to become a participant of gsod either as an organization or > writer - go for it! It definitely worth it! <3 > I'm open to discuss the details in IRC or other communication channels. Feel > free to ping me. > > Regards, > > Alex > > > On Wed, Feb 10, 2021, 19:29 Moshe Kaplan wrote: >> >> Is this worth participating in again? >> >> Moshe >> >> -- Forwarded message - >> From: Season of Docs - Announce >> Date: Tue, Feb 9, 2021 at 1:09 PM >> Subject: [Season of Docs - Announcements] The 2021 Season of Docs >> application for organizations is open! >> To: Season of Docs - Announce >> >> >> We’re delighted to announce Season of Docs 2021! >> >> In 2021 the Season of Docs program will continue to support better >> documentation in open source and provide opportunities for skilled technical >> writers to gain open source experience. In addition, building on what we’ve >> learned from the successful 2019 and 2021 projects, we’re expanding our >> focus to include learning about effective metrics for evaluating open source >> documentation. >> >> What are the 2021 program changes? >> >> Season of Docs 2021 will allow open source organizations to apply for a >> grant, based on their documentation needs. If selected, open source >> organizations will use their grant to hire a technical writer directly to >> complete their documentation project. Organizations will have up to six >> months to complete their documentation project. Keep reading for more >> information about the organization application or visit the Season of Docs >> site. >> >> Technical writers interested in working with accepted open source >> organizations will be able to share their contact information via the Season >> of Docs GitHub repository, or submit proposals directly to the >> organizations, and will not need to submit a formal application through >> Season of Docs. >> >> Participating organizations will help broaden our understanding of effective >> documentation practices and metrics in open source by submitting a final >> case study upon completion of the program. The project case study will >> outline the problem the documentation project was intended to solve, what >> metrics were used to judge the effectiveness of the documentation, and what >> the organization learned for the future. All the project case studies will >> be published on the Season of Docs site at the end of the program. >> >> Organization Applications >> >> Organization applications are now open! The deadline to apply is March 26, >> 2021 at 18:00 UTC. >> >> To apply, first read the guidelines for creating an organization application >> on the Season of Docs website. >> >> Take a look at the examples of project ideas, then create a project proposal >> based on your open source project’s actual documentation needs. Your goal is >> to attract technical writers to your organization, making them feel >> comfortable about approaching the organization and excited about what they >> can achieve. >> >> Organizations can submit their applications here: http://goo.gle/3qVxArQ. >> Organization applications close on March 26 at 18:00 UTC. >> >> Technical writers interested in participating in the 2021 Season of Docs >> should read our guide for technical writers on the Season of Docs website. >> >> Please do tweet and blog about Season of Docs if you’d like to share the >> news. We want as many people to know about it as possible. We’ve provided >> logos that you can download and some example content on the press page. >> >> If you have any questions about the program, please email us at >> season-of-d...@google.com. >> >> We’re looking forward to another productive year of the Season of Docs >> program! >> >> Best regards, >> >> Kassandra Dhillon, Erin McKean, and the Season of Docs team >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Season of Docs - Announce" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to
Re: [Wireshark-dev] pipeline failed at the Restore Cache step
hi guys, is anything missing on my branch or are we just waiting for a code review ? thanks and good week-end Eugene Le jeu. 10 sept. 2020 à 14:28, Eugène Adell a écrit : > > Thanks Dario, it's now fixed (it seems some switch/case blocks allow > empty lines but not others ?) > > > E.A. > > Le jeu. 10 sept. 2020 à 10:11, Dario Lombardo a écrit : > > > > Your CI failed for trailing whitespaces. > > > > $ bash ./tools/pre-commit 'HEAD^1' > > epan/dissectors/packet-tcp.c:1351: trailing whitespace. > > + > > epan/dissectors/packet-tcp.c:1356: trailing whitespace. > > + > > epan/dissectors/packet-tcp.c:1362: trailing whitespace. > > + > > epan/dissectors/packet-tcp.c:1369: trailing whitespace. > > + > > epan/dissectors/packet-tcp.c:1388: trailing whitespace. > > + > > epan/dissectors/packet-tcp.c:1404: trailing whitespace. > > > > Fix them, amend your commit, rebase on master, push force and the CI will > > start again. > > > > On Thu, Sep 10, 2020 at 9:57 AM Eugène Adell wrote: > >> > >> Hi guys, > >> > >> My pipeline is in error ( branch 16716 Pipeline #188182176 ) and I > >> don't know what to do. > >> > >> My branch which was first on Gerrit, I followed what is said in the > >> doc to move it as a Merge Request and finally it asked for a Rebase, > >> which I ran this morning and ended with this error. > >> > >> The error details : > >> Restoring cache > >> Checking cache for merge-request:ubuntu-dpkg-master... > >> FATAL: file does not exist > >> Failed to extract cache > >> > >> Did I miss anything ? > >> Thanks for helping. > >> > >> Eugene > >> ___ > >> Sent via:Wireshark-dev mailing list > >> Archives:https://www.wireshark.org/lists/wireshark-dev > >> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > >> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > > > > > > > > -- > > > > Naima is online. > > > > ___ > > Sent via:Wireshark-dev mailing list > > Archives:https://www.wireshark.org/lists/wireshark-dev > > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] pipeline failed at the Restore Cache step
Thanks Dario, it's now fixed (it seems some switch/case blocks allow empty lines but not others ?) E.A. Le jeu. 10 sept. 2020 à 10:11, Dario Lombardo a écrit : > > Your CI failed for trailing whitespaces. > > $ bash ./tools/pre-commit 'HEAD^1' > epan/dissectors/packet-tcp.c:1351: trailing whitespace. > + > epan/dissectors/packet-tcp.c:1356: trailing whitespace. > + > epan/dissectors/packet-tcp.c:1362: trailing whitespace. > + > epan/dissectors/packet-tcp.c:1369: trailing whitespace. > + > epan/dissectors/packet-tcp.c:1388: trailing whitespace. > + > epan/dissectors/packet-tcp.c:1404: trailing whitespace. > > Fix them, amend your commit, rebase on master, push force and the CI will > start again. > > On Thu, Sep 10, 2020 at 9:57 AM Eugène Adell wrote: >> >> Hi guys, >> >> My pipeline is in error ( branch 16716 Pipeline #188182176 ) and I >> don't know what to do. >> >> My branch which was first on Gerrit, I followed what is said in the >> doc to move it as a Merge Request and finally it asked for a Rebase, >> which I ran this morning and ended with this error. >> >> The error details : >> Restoring cache >> Checking cache for merge-request:ubuntu-dpkg-master... >> FATAL: file does not exist >> Failed to extract cache >> >> Did I miss anything ? >> Thanks for helping. >> >> Eugene >> ___ >> Sent via:Wireshark-dev mailing list >> Archives:https://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev >> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > > > > -- > > Naima is online. > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] pipeline failed at the Restore Cache step
Hi guys, My pipeline is in error ( branch 16716 Pipeline #188182176 ) and I don't know what to do. My branch which was first on Gerrit, I followed what is said in the doc to move it as a Merge Request and finally it asked for a Rebase, which I ran this morning and ended with this error. The error details : Restoring cache Checking cache for merge-request:ubuntu-dpkg-master... FATAL: file does not exist Failed to extract cache Did I miss anything ? Thanks for helping. Eugene ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Gitlab doesn't show all epan/dissectors/ files.
Hello, I have the very same behavior, my browser being Firefox 80.0 (64 bits) Le mer. 9 sept. 2020 à 20:44, Maynard, Chris via Wireshark-dev a écrit : > > It doesn’t seem to be possible to list all dissectors in a web browser > anymore, and those that are listed are populated very slowly. > Compare the loading of > https://gitlab.com/wireshark/wireshark/-/tree/master/epan/dissectors with > that of > https://code.wireshark.org/review/gitweb?p=wireshark.git;a=tree;f=epan/dissectors;h=18070dacc9b477c446503e46b68b3c128d1ae984;hb=HEAD. > > I was interested in looking at packet-ntp.c, but that file never gets listed, > even after clicking “Show more”. The last file listed for me is > packet-newmail.c. Tested with Firefox 80.0.1 (64-bit) and Chrome Version > 85.0.4183.102 (Official Build) (64-bit). Of course if you know the filename, > you can click on another file then manually edit the URL with the file you’re > actually interested in looking at, but this isn’t an ideal solution. > > Is anyone else experiencing this problem? And more importantly, is there > anything that can be done to remedy this? > Thanks. > - Chris > > > > > > > > > > > > CONFIDENTIALITY NOTICE: This message is the property of International Game > Technology PLC and/or its subsidiaries and may contain proprietary, > confidential or trade secret information. This message is intended solely for > the use of the addressee. If you are not the intended recipient and have > received this message in error, please delete this message from your system. > Any unauthorized reading, distribution, copying, or other use of this message > or its attachments is strictly prohibited. > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] wiki edition request
Hi guys, I would like to add some captures on the dedicated wiki page. My username : EugeneAdell Or if you prefer to edit yourself, the captures are attached to this email (the old CHARGEN protocol, which has some educational value since it's a very simple one) best regards E.A. chargen-udp.pcap Description: Binary data chargen-tcp.pcap Description: Binary data ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Dissector for a custom protocol which starts as HTTP
Hello, in the Wireshark GUI did you try the "Decode As" functionality ? You get it in the right-clic on a packet (or in Analyze menu). You also can have a look at Analyze -> Enabled protocols. see : https://www.wireshark.org/docs/wsug_html_chunked/ChUseAnalyzeMenuSection.html Eugene Le mar. 16 avr. 2019 à 23:22, David Ameiss a écrit : > > I've developed a dissector for a custom protocol used by my company. The > protocol starts out as HTTP, as in an HTTP GET, but after that uses the > "custom" part - not HTTP at all. > > The problem I'm running into is that, once a conversation is identified > by the HTTP dissector as being HTTP (due to the first message, which IS > HTTP), it stays that way. My dissector isn't called. I've added my > dissector as a heuristic dissector for HTTP, but that doesn't seem to > help. And unfortunately (since subsequent packets are not HTTP) I don't > have Content-Type to steer the packets my way. > > Subsequent packets appear as HTTP Continuation, BTW. > > Is there some way to tell HTTP not to treat following packets for that > conversation as HTTP, and to pass them to my dissector? Or a way to call > the HTTP dissector (from my dissector) for the first packet WITHOUT it > being "marked" as HTTP forever and ever? > > -- > David Ameiss > netsh...@ameissnet.com > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] compilation hangs on Ubuntu
Submitted and validated by Guy Harris. All's fine now.
2018-05-14 20:29 GMT+02:00 Dario Lombardo <lom...@gmail.com>:
> Can you submit a change on Gerrit for it?
>
> On Mon, May 14, 2018, 19:58 Eugène Adell <eugene.ad...@gmail.com> wrote:
>
>>
>> Thanks all for the help and Darius for finding out this conflict with
>> ninja. Building with an ordinary user works.
>>
>>
>> By the way, I have another small request. Could you please change the
>> AUTHORS file to keep my personal address (my email at D2-SI didn't survive
>> after I left, and I contributed twice, the first time with D2-SI and later
>> under my personal address). Thanks.
>>
>> kind regards
>> Eugène
>>
>>
>>
>>
>> 2018-05-14 17:11 GMT+02:00 Darius Davis <dar...@vmware.com>:
>>
>>> Hi Eugène,
>>>
>>>
>>>
>>> The strace log shows that your Ubuntu 16.04 system has the "ninja"
>>> package installed, which is "a privilege escalation detection and
>>> prevention system for GNU/Linux hosts" (https://packages.ubuntu.com/
>>> xenial/admin/ninja). It installs into /usr/sbin/ninja. Your build
>>> problem is caused by the presence of that "ninja" package on your system --
>>> and the fact that you appear to be building wireshark as "root".
>>>
>>>
>>>
>>> While running as "root", your PATH contains /usr/sbin, and that entry
>>> appears before /usr/bin, so instead of cmake launching the ninja build tool
>>> (/usr/bin/ninja), it launches the ninja privilege escalation detection tool
>>> (/usr/sbin/ninja), which busily monitors your /proc directory for evidence
>>> of system intrusion... but does not build Wireshark.
>>>
>>>
>>>
>>> 1900 access("/usr/sbin/ninja", R_OK) = 0
>>>
>>> 1900 stat("/usr/sbin/ninja", {st_mode=S_IFREG|0755, st_size=22872,
>>> ...}) = 0
>>>
>>> [...]
>>>
>>> 1901 execve("/usr/sbin/ninja", ["/usr/sbin/ninja", "--version"], [/* 22
>>> vars */]
>>>
>>>
>>>
>>> You should be able to resolve the issue by building Wireshark as a
>>> non-root user -- I don't think there is any need or reason to build as
>>> "root". As a regular user, your PATH should not contain /usr/sbin, and the
>>> ninja intrusion-detection program will be ignored. cmake should then find
>>> and launch the ninja build tool correctly.
>>>
>>>
>>>
>>> If you are not going to use the "ninja" privilege escalation detection
>>> program (for example, if it was installed by accident while you were
>>> looking for the "ninja-build" package), you can uninstall it by running
>>> "sudo apt-get remove ninja", and that would resolve the build problem too.
>>> (Regardless, I would really advise not building as "root" unless you have a
>>> very good reason to do so!)
>>>
>>>
>>>
>>> Cheers,
>>>
>>> --
>>>
>>> Darius
>>>
>>>
>>>
>>> *From: *Wireshark-dev <wireshark-dev-boun...@wireshark.org> on behalf
>>> of Eugène Adell <eugene.ad...@gmail.com>
>>> *Reply-To: *Developer support list for Wireshark <
>>> wireshark-dev@wireshark.org>
>>> *Date: *Tuesday, 15 May 2018 at 12:25 am
>>> *To: *Developer support list for Wireshark <wireshark-dev@wireshark.org>
>>> *Subject: *Re: [Wireshark-dev] compilation hangs on Ubuntu
>>>
>>>
>>>
>>> It doesn't hang, it returns :
>>>
>>> 2;7;12
>>>
>>> As requested, the strace is attached.
>>>
>>>
>>>
>>>
>>>
>>> 2018-05-13 22:29 GMT+02:00 Jakub Zawadzki <darkjames...@darkjames.pl>:
>>>
>>> Hello,
>>>
>>> W dniu 2018-05-13 17:15, Eugène Adell napisał(a):
>>>
>>> I'm facing a problem on my development server (Ubuntu 16.04 hosted on
>>> VMWARE) when trying to compile Wireshark. It was working with older
>>> versions (2.0 for example), but now it's like the compilation will never
>>> end.
>>> I installed/updated all the required packages, since version 2.6 seems
>>> quite different.
>>>
>>> I'm doing an strace -f -o to find out what could be wrong, but no clue.
>>> The
>>> strace log being too big, here is ho
Re: [Wireshark-dev] compilation hangs on Ubuntu
Thanks all for the help and Darius for finding out this conflict with
ninja. Building with an ordinary user works.
By the way, I have another small request. Could you please change the
AUTHORS file to keep my personal address (my email at D2-SI didn't survive
after I left, and I contributed twice, the first time with D2-SI and later
under my personal address). Thanks.
kind regards
Eugène
2018-05-14 17:11 GMT+02:00 Darius Davis <dar...@vmware.com>:
> Hi Eugène,
>
>
>
> The strace log shows that your Ubuntu 16.04 system has the "ninja" package
> installed, which is "a privilege escalation detection and prevention system
> for GNU/Linux hosts" (https://packages.ubuntu.com/xenial/admin/ninja).
> It installs into /usr/sbin/ninja. Your build problem is caused by the
> presence of that "ninja" package on your system -- and the fact that you
> appear to be building wireshark as "root".
>
>
>
> While running as "root", your PATH contains /usr/sbin, and that entry
> appears before /usr/bin, so instead of cmake launching the ninja build tool
> (/usr/bin/ninja), it launches the ninja privilege escalation detection tool
> (/usr/sbin/ninja), which busily monitors your /proc directory for evidence
> of system intrusion... but does not build Wireshark.
>
>
>
> 1900 access("/usr/sbin/ninja", R_OK) = 0
>
> 1900 stat("/usr/sbin/ninja", {st_mode=S_IFREG|0755, st_size=22872, ...})
> = 0
>
> [...]
>
> 1901 execve("/usr/sbin/ninja", ["/usr/sbin/ninja", "--version"], [/* 22
> vars */]
>
>
>
> You should be able to resolve the issue by building Wireshark as a
> non-root user -- I don't think there is any need or reason to build as
> "root". As a regular user, your PATH should not contain /usr/sbin, and the
> ninja intrusion-detection program will be ignored. cmake should then find
> and launch the ninja build tool correctly.
>
>
>
> If you are not going to use the "ninja" privilege escalation detection
> program (for example, if it was installed by accident while you were
> looking for the "ninja-build" package), you can uninstall it by running
> "sudo apt-get remove ninja", and that would resolve the build problem too.
> (Regardless, I would really advise not building as "root" unless you have a
> very good reason to do so!)
>
>
>
> Cheers,
>
> --
>
> Darius
>
>
>
> *From: *Wireshark-dev <wireshark-dev-boun...@wireshark.org> on behalf of
> Eugène Adell <eugene.ad...@gmail.com>
> *Reply-To: *Developer support list for Wireshark <
> wireshark-dev@wireshark.org>
> *Date: *Tuesday, 15 May 2018 at 12:25 am
> *To: *Developer support list for Wireshark <wireshark-dev@wireshark.org>
> *Subject: *Re: [Wireshark-dev] compilation hangs on Ubuntu
>
>
>
> It doesn't hang, it returns :
>
> 2;7;12
>
> As requested, the strace is attached.
>
>
>
>
>
> 2018-05-13 22:29 GMT+02:00 Jakub Zawadzki <darkjames...@darkjames.pl>:
>
> Hello,
>
> W dniu 2018-05-13 17:15, Eugène Adell napisał(a):
>
> I'm facing a problem on my development server (Ubuntu 16.04 hosted on
> VMWARE) when trying to compile Wireshark. It was working with older
> versions (2.0 for example), but now it's like the compilation will never
> end.
> I installed/updated all the required packages, since version 2.6 seems
> quite different.
>
> I'm doing an strace -f -o to find out what could be wrong, but no clue. The
> strace log being too big, here is how it looks like :
>
> 1900 execve("/usr/bin/cmake", ["cmake", "-LH", "../wireshark"], [/*
> 22 vars */]) = 0
> [cut]
>
>
>
> thousands of lines such as :
>
> 1901 open("/proc/537/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/538/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/539/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/540/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/541/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/542/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/543/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/544/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
>
>
> then thousands and thousands of lines such as the following, and it seems
> it will never end :
>
> 1901 open("/pr
[Wireshark-dev] compilation hangs on Ubuntu
Hello,
I'm facing a problem on my development server (Ubuntu 16.04 hosted on
VMWARE) when trying to compile Wireshark. It was working with older
versions (2.0 for example), but now it's like the compilation will never
end.
I installed/updated all the required packages, since version 2.6 seems
quite different.
I'm doing an strace -f -o to find out what could be wrong, but no clue. The
strace log being too big, here is how it looks like :
1900 execve("/usr/bin/cmake", ["cmake", "-LH", "../wireshark"], [/*
22 vars */]) = 0
1900 brk(NULL) = 0x2225000
1900 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
1900 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
1900 open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
1900 fstat(3, {st_mode=S_IFREG|0644, st_size=105981, ...}) = 0
...
thousands of lines such as :
1901 open("/proc/537/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/538/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/539/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/540/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/541/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/542/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/543/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/544/status", O_RDONLY) = -1 ENOENT (No such file or directory)
then thousands and thousands of lines such as the following, and it seems
it will never end :
1901 open("/proc/882/status", O_RDONLY) = 3
1901 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
1901 read(3, "Name:\tvmhgfs-fuse\nUmask:\t\nSt"..., 1024) = 1024
1901 read(3, ",,,,"..., 1024) = 263
1901 read(3, "", 1024) = 0
1901 close(3) = 0
1901 open("/proc/965/status", O_RDONLY) = 3
1901 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
1901 read(3, "Name:\tsystemd-logind\nUmask:\t0022"..., 1024) = 1024
1901 read(3, "000,,,00"..., 1024) = 269
1901 read(3, "", 1024) = 0
1901 close(3) = 0
1901 open("/proc/968/status", O_RDONLY) = 3
1901 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
1901 read(3, "Name:\tdbus-daemon\nUmask:\t0022\nSt"..., 1024) = 1024
1901 read(3, "00,,,,00"..., 1024) = 283
1901 read(3, "", 1024) = 0
1901 close(3) = 0
How can I resolve this ?
Thanks
E.A.
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] status of ATH dissector
Hello I would like to know the status of this dissector that I have submitted : https://code.wireshark.org/review/#/c/7807/ best regards ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
