https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #11 from clarkw ---
(In reply to Pascal Quantin from comment #10)
> We got similar reports in the past due to WinPcap preventing dumpcap from
> stopping.
> One possible solution (worth trying) is to remove WinPcap and instead
>
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #13 from clarkw ---
(In reply to Pascal Quantin from comment #10)
> One possible solution (worth trying) is to remove WinPcap and instead
> install Npcap and see if you reproduce the issue.
Just tried and WinPcap can be uninsta
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #12 from Pascal Quantin ---
This bug is about Wireshark not stopping its child process dumpcap when it
crashes, not about the fact that dumpcap cannot be stopped.
Please try with Npcap. If it still fails, please open a dedicated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #14 from Pascal Quantin ---
Dumpcap uses system calls provided by WinPcap / Npcap to do the capture.
So please reboot your machine before uninstalling WinPcap as a locked dumpcap
could prevent a proper uninstallation.
--
You a
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #15 from clarkw ---
(In reply to Pascal Quantin from comment #12)
> This bug is about Wireshark not stopping its child process dumpcap when it
> crashes, not about the fact that dumpcap cannot be stopped.
I hit the bug when I w
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #16 from clarkw ---
(In reply to Pascal Quantin from comment #14)
> Dumpcap uses system calls provided by WinPcap / Npcap to do the capture.
> So please reboot your machine before uninstalling WinPcap as a locked
> dumpcap could
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #17 from Pascal Quantin ---
Again please try to understand the difference between both cases. In the
initial issue there is no problem killing dumpcap manually. In your case, it's
dumpcap hanging that prevents Wireshark to prope
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14527
Bug ID: 14527
Summary: dumpcap processes cannot be killed after forcibly
killing wireshark
Product: Wireshark
Version: 2.4.5
Hardware: x86-64
OS: Win
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14527
clarkw changed:
What|Removed |Added
Component|GTK+ UI |Qt UI
--
You are receiving this mail be
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14527
Pascal Quantin changed:
What|Removed |Added
CC||pascal.quan...@gmail.com
--- Com
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14527
--- Comment #2 from clarkw ---
(In reply to Pascal Quantin from comment #1)
> Unfortunately WinPcap is no longer maintained.
> [...]
> Note that Wireshark favors WinPcap over Npcap. You can check which driver is
> used in the about info.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14527
--- Comment #3 from Pascal Quantin ---
(In reply to clarkw from comment #2)
> (In reply to Pascal Quantin from comment #1)
> > Unfortunately WinPcap is no longer maintained.
> > [...]
> > Note that Wireshark favors WinPcap over Npcap. You
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14528
Bug ID: 14528
Summary: Typo error in enumeration value of speech version
identifier
Product: Wireshark
Version: 2.4.5
Hardware: All
OS: All
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14528
--- Comment #1 from Gerrit Code Review ---
Change 26458 had a related patch set uploaded by Pascal Quantin:
GSM BSSMAP: fix a typo in in speech version range_string
https://code.wireshark.org/review/26458
--
You are receiving this mail
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14528
Pascal Quantin changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14529
Bug ID: 14529
Summary: Buildbot crash output: fuzz-2018-03-09-27328.pcap
Product: Wireshark
Version: unspecified
Hardware: x86-64
OS: Ubuntu
Status: CONFIRME
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14528
--- Comment #3 from Gerrit Code Review ---
Change 26458 merged by Pascal Quantin:
GSM BSSMAP: fix a typo in in speech version range_string
https://code.wireshark.org/review/26458
--
You are receiving this mail because:
You are watching
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14528
--- Comment #5 from Gerrit Code Review ---
Change 26459 merged by Pascal Quantin:
GSM BSSMAP: fix a typo in in speech version range_string
https://code.wireshark.org/review/26459
--
You are receiving this mail because:
You are watching
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14528
--- Comment #4 from Gerrit Code Review ---
Change 26459 had a related patch set uploaded by Pascal Quantin:
GSM BSSMAP: fix a typo in in speech version range_string
https://code.wireshark.org/review/26459
--
You are receiving this mail
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14528
--- Comment #6 from Gerrit Code Review ---
Change 26460 had a related patch set uploaded by Pascal Quantin:
GSM BSSMAP: fix a typo in in speech version range_string
https://code.wireshark.org/review/26460
--
You are receiving this mail
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14528
--- Comment #7 from Gerrit Code Review ---
Change 26460 merged by Pascal Quantin:
GSM BSSMAP: fix a typo in in speech version range_string
https://code.wireshark.org/review/26460
--
You are receiving this mail because:
You are watching
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14528
Pascal Quantin changed:
What|Removed |Added
Resolution|--- |FIXED
Status|IN_PROG
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14529
--- Comment #1 from Guy Harris ---
And the part the bug filer left out:
./tools/fuzz-test.sh: line 207: 24677 CPU time limit exceeded (core dumped)
"$RUNNER" $COMMON_ARGS $ARGS $TMP_DIR/$TMP_FILE > /dev/null 2>>
$TMP_DIR/$ERR_FILE.$SUBSHE
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14506
--- Comment #2 from christian.rohm...@inovex.de ---
Hey Alex,
thanks for the lightning quick reply.
I will get you some sample PCAPs of TCP traffic containing PROXY protocol v2
traffic.
In the meantime, may I point your to
1) https:/
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #18 from Christopher Maynard ---
(In reply to clarkw from comment #8)
> See also: http://support.moonpoint.com/os/windows/processes/unkillable/
The link to
https://blogs.technet.microsoft.com/markrussinovich/2005/08/17/unkillab
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #19 from Gerald Combs ---
The original issue should be fixed in
https://code.wireshark.org/review/#/c/26448/. It assigns dumpcap to a job
object[1] which terminates it when Wireshark, TShark, etc close. Job objects
won't magical
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #20 from Gerrit Code Review ---
Change 26448 merged by Anders Broman:
Windows: Always assign newly-created processes to our job.
https://code.wireshark.org/review/26448
--
You are receiving this mail because:
You are watching
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14506
--- Comment #3 from christian.rohm...@inovex.de ---
Created attachment 16212
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16212&action=edit
PCAP of MQTT CONNECT behind HAProxy using send-proxy-v2
--
You are receiving this m
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14506
--- Comment #4 from christian.rohm...@inovex.de ---
Created attachment 16213
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16213&action=edit
PCAP of MQTT CONNECT behind HAProxy using send-proxy-v2-ssl
--
You are receiving th
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14506
--- Comment #5 from christian.rohm...@inovex.de ---
Created attachment 16214
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16214&action=edit
PCAP of MQTT CONNECT behind HAProxy using send-proxy-v2-ssl-cn
--
You are receiving
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14506
--- Comment #6 from christian.rohm...@inovex.de ---
I attached three PCAP files. Each file contains an MQTT CONNECT done over a
HAProxy instance.
1) The first "send-proxy-v2" is without any SSL.
2) Then "send-proxy-v2-ssl" with TLV contain
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14506
--- Comment #7 from Alexis La Goutte ---
Thanks, i will look !
--
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bu
32 matches
Mail list logo
