https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14355
Kenneth Soerensen changed:
What|Removed |Added
CC||Jewgenij.Bytschkow@t-system
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14721
Kenneth Soerensen changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|-
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14722
Peter Wu changed:
What|Removed |Added
See Also||https://bugs.wireshark.org/
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14622
Peter Wu changed:
What|Removed |Added
See Also||https://bugs.wireshark.org/
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14700
--- Comment #18 from Eduardo Montoya Marín ---
Well, I can't agree that the re-assembly is not incorrect. Those
00:00:00:ff:fe:00:04:01 and 00:00:00:ff:fe:00:00:00 don't look like something
very right to be shown as source and destination
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14720
--- Comment #1 from Gerrit Code Review ---
Change 27775 had a related patch set uploaded by Peter Wu:
wslua: fix NSTime:__tostring for negative values
https://code.wireshark.org/review/27775
--
You are receiving this mail because:
You a
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14720
Peter Wu changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14700
--- Comment #19 from sau...@locoslab.com ---
Ah, I've missed that. But I don't think that is an issue of 'wrong'
re-assembly. It seems for all frames that are fragments but have not been
re-assembled, e.g., retransmissions, the context for
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14724
Bug ID: 14724
Summary: extcap interfaces missing due to empty extcap path
Product: Wireshark
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14724
Mikael Kanstrup changed:
What|Removed |Added
CC||lom...@gmail.com
--
You are re
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14725
Bug ID: 14725
Summary: Created and collected snoops but when I go to open
them with Wireshark (v2.4.2) I get message that files
are corrupt (netscreen too much hex-data)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12722
Anders Broman changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIR
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14700
--- Comment #20 from Gerrit Code Review ---
Change 27761 merged by Anders Broman:
6lowpan: fix reassembly for forwarded packets
https://code.wireshark.org/review/27761
--
You are receiving this mail because:
You are watching all bug cha
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14700
--- Comment #21 from Gerrit Code Review ---
Change 2 had a related patch set uploaded by Peter Wu:
6lowpan: fix reassembly for forwarded packets
https://code.wireshark.org/review/2
--
You are receiving this mail because:
You are
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14700
--- Comment #22 from Gerrit Code Review ---
Change 2 merged by Peter Wu:
6lowpan: fix reassembly for forwarded packets
https://code.wireshark.org/review/2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14700
Peter Wu changed:
What|Removed |Added
Status|IN_PROGRESS |RESOLVED
Resolution|---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14724
Mikael Kanstrup changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONF
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14701
--- Comment #19 from Christopher Maynard ---
A bit more information - I sorted the capture files in the public menagerie by
size and tested all those greater than 1.5MB.
The following is the list of files that failed to load with Wireshar
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14710
Peter Wu changed:
What|Removed |Added
Resolution|--- |NOTABUG
Status|CONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14670
Peter Wu changed:
What|Removed |Added
CC||pe...@lekensteyn.nl
--- Comment #1 fro
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14670
Peter Wu changed:
What|Removed |Added
CC||s...@bjorlykke.org
--- Comment #2 from
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14637
Peter Wu changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
CC|
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14611
Peter Wu changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRM
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14620
Peter Wu changed:
What|Removed |Added
CC||we...@locoslab.com
--- Comment #7 from
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14726
Bug ID: 14726
Summary: Wireshark-win64-2.6.1 can't load on Windows 7
Professional 64-bit Operating system even with adimn
authorization.
Product: Wireshark
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14654
Peter Wu changed:
What|Removed |Added
CC||pe...@lekensteyn.nl
--- Comment #1 fro
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14727
Bug ID: 14727
Summary: The recent change for DMG Capabilities dissection
breaks dissection of many existing captures
Product: Wireshark
Version: Git
Hardware: x86
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14726
Alexis La Goutte changed:
What|Removed |Added
CC||alexis.lagou...@gmail.com
---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14727
Richard Sharpe changed:
What|Removed |Added
CC||chaitanya.m...@gmail.com
--
You
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14727
Alexis La Goutte changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRM
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14727
--- Comment #2 from Richard Sharpe ---
Created attachment 16367
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16367&action=edit
An example of the issue
--
You are receiving this mail because:
You are watching all bug change
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14726
--- Comment #2 from william ---
Thanks, Alexis.
The installation process is normal,
and the installed folder seems normal as well.
Or you mean other "check process"?
--
You are receiving this mail because:
You are watching all bug chan
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14726
--- Comment #3 from Gerald Combs ---
Can you try running "c:\Program Files\Wireshark\tshark" and "c:\Program
Files\Wireshark\wireshark" from a command prompt?
--
You are receiving this mail because:
You are watching all bug changes._
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14587
Peter Wu changed:
What|Removed |Added
CC||pe...@lekensteyn.nl
--- Comment #5 fro
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14587
--- Comment #6 from Pascal Quantin ---
Due to comment #3
--
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mai
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14698
Peter Wu changed:
What|Removed |Added
CC||anders.bro...@ericsson.com,
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11630
--- Comment #39 from jewgenij.bytsch...@t-systems.com ---
Can you please identify the cause why the old fixed issue occurs again?
Can you also estimate and post a comment with a forecast in which future
Wireshark release the old fix for Bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14728
Bug ID: 14728
Summary: DCERPC dissector bug: failed assertion
Product: Wireshark
Version: Git
Hardware: x86-64
OS: Windows 10
Status: UNCONFIRMED
S
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14587
--- Comment #7 from Peter Wu ---
The data over endpoints associated with a data class interface has no fixed
protocol as far as I can see:
> 3.4.2 Data Class Interface
> The Data Class defines a data interface as an interface with a class
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14587
--- Comment #8 from Pascal Quantin ---
That was my point: I do not know how to link the communication class with the
data class (or at least did not find a way to achieve it the last time I looked
at it, but this is not fresh in my memory)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14637
--- Comment #2 from Gerrit Code Review ---
Change 27783 had a related patch set uploaded by Alexis La Goutte:
Makefile (ui/cli): fix duplicat entry for tap-endpoints.
https://code.wireshark.org/review/27783
--
You are receiving this mai
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14587
--- Comment #9 from James Murray ---
It's just raw data. There's no "protocol" here.
--
You are receiving this mail because:
You are watching all bug changes.___
Sen
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14637
--- Comment #3 from Gerrit Code Review ---
Change 27783 merged by Anders Broman:
Makefile (ui/cli): fix duplicat entry for tap-endpoints.
https://code.wireshark.org/review/27783
--
You are receiving this mail because:
You are watching a
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14727
--- Comment #3 from Gerrit Code Review ---
Change 27782 merged by Alexis La Goutte:
ieee80211: Make DMG Capabilities dissection handle earlier formats
https://code.wireshark.org/review/27782
--
You are receiving this mail because:
You a
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14637
--- Comment #4 from Peter Wu ---
The duplicate was added in v2.3.0rc0-1599-g20c57cb298. Are duplicates causing
issues that warrant a backport to master-2.4?
--
You are receiving this mail because:
You are watching all bug changes.___
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14587
--- Comment #10 from Peter Wu ---
My understanding of the spec is that the two interfaces are unrelated:
Endpoints following the interface descriptor of class "Communications and CDC
Control" (IF_CLASS_COMMUNICATIONS) with the ECM subclas
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
Greg Wesson changed:
What|Removed |Added
CC||greg.wes...@gmail.com
--
You are r
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11630
--- Comment #40 from Gerrit Code Review ---
Change 27786 had a related patch set uploaded by Alexis La Goutte:
radius: fix dissection of Ascend-Data-Filter
https://code.wireshark.org/review/27786
--
You are receiving this mail because:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14729
Bug ID: 14729
Summary: media_type "application/octet-stream" registered for
both Thread and UASIP
Product: Wireshark
Version: 2.6.1
Hardware: All
OS:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14729
--- Comment #1 from Gerrit Code Review ---
Change 27789 had a related patch set uploaded by Stig Bjørlykke:
media_type: Default decode application/octet-stream as data
https://code.wireshark.org/review/27789
--
You are receiving this ma
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14726
--- Comment #4 from william ---
Created attachment 16368
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16368&action=edit
tshark log
--
You are receiving this mail because:
You are watching all bug changes.__
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14726
--- Comment #6 from william ---
Thanks, Gerald.
Pls see attached tshark & wireshark logs.
--
You are receiving this mail because:
You are watching all bug changes._
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14726
--- Comment #5 from william ---
Created attachment 16369
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16369&action=edit
wireshark log
--
You are receiving this mail because:
You are watching all bug changes.___
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14637
--- Comment #5 from Christopher Maynard ---
(In reply to Peter Wu from comment #4)
> The duplicate was added in v2.3.0rc0-1599-g20c57cb298. Are duplicates
> causing issues that warrant a backport to master-2.4?
The duplicate entry wasn't
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14725
--- Comment #1 from Jaap Keuter ---
After line 113 the capture file is corrupted
00 00 00 00 02 22 00 00 01 b5 d4 d8 e2 e3 d9 40 ..8 @@..
There's too much data for a frame declared to have: 'len=669'
Compare e.g. the
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14726
--- Comment #7 from Gerald Combs ---
(In reply to william from comment #6)
> Thanks, Gerald.
>
> Pls see attached tshark & wireshark logs.
According to the logs TShark runs fine and is able to capture data, which means
that the various l
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14725
Guy Harris changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14726
--- Comment #8 from william ---
I once installed some old version(sorry I can't remember which version)
wireshark on this Windows 7,
and it once worked fine,
after kept updating to newer version,
the newer version wireshark can't launch.
A
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14722
Eric Hall changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14722
Guy Harris changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|FIXED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14662
Peter Wu changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14662
--- Comment #2 from Gerrit Code Review ---
Change 27794 had a related patch set uploaded by Peter Wu:
smb: fix wrong exported smb2 object due to hash collision
https://code.wireshark.org/review/27794
--
You are receiving this mail becau
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14726
--- Comment #9 from william ---
I installed some old version of Wireshark-win64-2.2.5,
it works.
Thanks you guys for the help.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14662
--- Comment #3 from Peter Wu ---
Created attachment 16370
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16370&action=edit
Problematic capture (frame.number in {9457..10881 328..336})
The attached capture was extracted from t
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14478
Peter Wu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14447
Peter Wu changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14602
Peter Wu changed:
What|Removed |Added
See Also||https://bugs.wireshark.org/
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14396
Peter Wu changed:
What|Removed |Added
See Also||https://bugs.wireshark.org/
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14447
Guy Harris changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--
You are receiving this
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11630
João Valverde changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14729
--- Comment #2 from Guy Harris ---
So Thread doesn't have a media type assigned to it for CoAP? And *nothing
else* transported over CoAP uses application/octet-stream? They couldn't even
bother to register for application/vnd.google.thre
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14729
--- Comment #3 from Gerrit Code Review ---
Change 27789 merged by Guy Harris:
media_type: Default decode application/octet-stream as data
https://code.wireshark.org/review/27789
--
You are receiving this mail because:
You are watching a
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14725
--- Comment #2 from Guy Harris ---
Yes, the packet header indicates that the total packet length is 669 bytes and
the IP total length is 655 bytes (655+14 = 669, so that makes sense), and
looking at the packet data, the IP total length fie
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14662
--- Comment #4 from Gerrit Code Review ---
Change 27794 merged by Anders Broman:
smb: fix wrong exported smb2 object due to hash collision
https://code.wireshark.org/review/27794
--
You are receiving this mail because:
You are watching
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14729
--- Comment #4 from Gerrit Code Review ---
Change 27798 had a related patch set uploaded by Stig Bjørlykke:
media_type: Default decode application/octet-stream as data
https://code.wireshark.org/review/27798
--
You are receiving this ma
75 matches
Mail list logo