https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463
--- Comment #8 from Gerrit Code Review ---
Change 31826 merged by Guy Harris:
Check whether you've hit the end of the packet data before going further.
https://code.wireshark.org/review/31826
--
You are receiving this mail because:
You
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463
--- Comment #7 from Gerrit Code Review ---
Change 31826 had a related patch set uploaded by Guy Harris:
Check whether you've hit the end of the packet data before going further.
https://code.wireshark.org/review/31826
--
You are
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463
--- Comment #6 from Gerrit Code Review ---
Change 31825 merged by Guy Harris:
Check whether you've hit the end of the packet data before going further.
https://code.wireshark.org/review/31825
--
You are receiving this mail because:
You
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463
--- Comment #5 from Gerrit Code Review ---
Change 31825 had a related patch set uploaded by Guy Harris:
Check whether you've hit the end of the packet data before going further.
https://code.wireshark.org/review/31825
--
You are
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463
--- Comment #3 from Gerrit Code Review ---
Change 31824 had a related patch set uploaded by Guy Harris:
Check whether you've hit the end of the packet data before going further.
https://code.wireshark.org/review/31824
--
You are
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463
--- Comment #4 from Gerrit Code Review ---
Change 31824 merged by Guy Harris:
Check whether you've hit the end of the packet data before going further.
https://code.wireshark.org/review/31824
--
You are receiving this mail because:
You
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463
Guy Harris changed:
What|Removed |Added
Hardware|x86-64 |All
OS|Linux
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14101
--- Comment #10 from LorenAmelang ---
(In reply to Christopher Maynard from comment #6)
> > The Npcap Packet Driver (NPCAP) service is not started.
> >
> > More help is available by typing NET HELPMSG 3521.
> >
> > System error 2 has
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15429
--- Comment #7 from James Ko ---
> Added flag for TI CC24xx FCS format.
Upon further examination of the TI CC24xx FCS format, I propose the following
ammendment to 2.2.1 IEEE 802.15.4 Information Header iph_flags
iph_flags -
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14614
Christopher Maynard changed:
What|Removed |Added
OS|Windows 7 |Windows
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14599
Christopher Maynard changed:
What|Removed |Added
Version|unspecified |Git
Hardware|x86
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463
Peter Wu changed:
What|Removed |Added
CC||pe...@lekensteyn.nl
Ever
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15470
--- Comment #1 from Christopher Maynard ---
I don't know if the following information is relevant to this problem or not,
but in case it is, here's another observation:
When Wireshark is started and sparklines are working, Task Manager
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15469
Christopher Maynard changed:
What|Removed |Added
Summary|Wireshark uninstaller fails |Wireshark uninstaller fails
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15429
James Ko changed:
What|Removed |Added
Attachment #16851|0 |1
is obsolete|
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15469
--- Comment #3 from Christopher Maynard ---
(In reply to Pascal Quantin from comment #2)
> This should be handled by the USBPcap installer, not by Wireshark. Please
> report it to https://github.com/desowin/usbpcap/issues
Done. See
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14030
--- Comment #2 from Betty DuBois ---
(In reply to Guy Harris from comment #1)
> (In reply to Betty DuBois from comment #0)
> > Currently I download DNS registrar data from MaxMind which imports into
> > Wireshark beautifully.
>
> Are you
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14549
--- Comment #5 from Christopher Maynard ---
(In reply to Guy Harris from comment #2)
> There's a preference setting under "Capture" for "Update list of packets in
> real time". If you don't specify -S on the command line, the value of
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15469
Pascal Quantin changed:
What|Removed |Added
CC||pascal.quan...@gmail.com
---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15470
Bug ID: 15470
Summary: Sparklines stop working after opening/closing a
capture file or after capturing/stopping.
Product: Wireshark
Version: 2.6.6
Hardware: x86-64
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14101
--- Comment #9 from LorenAmelang ---
(In reply to Christopher Maynard from comment #6)
...
> My company has instituted this insane policy whereby only 1 interface is
> allowed to be active at a time. You're not suffering from a similar
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15469
Christopher Maynard changed:
What|Removed |Added
Summary|Wireshark uninstaller fails |Wireshark uninstaller fails
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15469
Bug ID: 15469
Summary: Wireshark uninstaller fails to remove
styles\qwindowsvistastyle.dll (or USBPcap if also
uninstalling that)
Product: Wireshark
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14537
--- Comment #1 from Christopher Maynard ---
Can you install Wireshark 2.6.5 from https://www.wireshark.org/download/win64/
and then try "Help -> Check for Updates..." to try to have Wireshark updated to
2.6.6 (the current latest stable
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14252
--- Comment #4 from Christopher Maynard ---
(In reply to jonhp from comment #3)
> Not sure I understand how disabling the external resolver produces the same
> visual result as changing the order of “resolution mechanisms”. Can you say
>
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14252
--- Comment #3 from jo...@charter.net ---
Not sure I understand how disabling the external resolver produces the same
visual result as changing the order of “resolution mechanisms”. Can you say
more?
--
You are receiving this mail
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14330
Christopher Maynard changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14327
--- Comment #1 from Christopher Maynard ---
The problem seems to be that the main screen just highlights the first
interface instead of the default interface, so when you start a capture, it
uses that one. Wireshark should
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14307
Christopher Maynard changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14306
--- Comment #7 from Christopher Maynard ---
(In reply to Gerrit Code Review from comment #4)
> Change 31057 had a related patch set uploaded by Michael Mann:
> TimeShiftDialog should be considered an "edit" operation
>
>
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14284
--- Comment #14 from Christopher Maynard ---
(In reply to Alexis La Goutte from comment #13)
> Can you try last 2.9 nighty build ?
Any feedback? Can this bug be closed now?
--
You are receiving this mail because:
You are watching all
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14252
Christopher Maynard changed:
What|Removed |Added
Resolution|--- |NOTABUG
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15468
Christopher Maynard changed:
What|Removed |Added
Summary|MAC addresses are resolved |MAC addresses are resolved
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14252
Christopher Maynard changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15468
Bug ID: 15468
Summary: MAC addresses are resolved to IP addresses/host names
in ARP packets, even if "Use an external network name
resolver" is disabled.
Product:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14101
Pascal Quantin changed:
What|Removed |Added
CC||pascal.quan...@gmail.com
---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14226
--- Comment #2 from Christopher Maynard ---
(In reply to Colin from comment #0)
> It would be very nice to be able to create a Display Filter and also specify
> the desired displayed columns in the Packet List for that display filter.
>
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14101
--- Comment #7 from Christopher Maynard ---
(In reply to Guy Harris from comment #4)
> > Also, I already had an almost current npcap installed by nmap. Maybe
> > Wireshark installs could offer to adopt it if it is already installed?
>
>
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14101
--- Comment #6 from Christopher Maynard ---
(In reply to LorenAmelang from comment #3)
> I checked the files you listed and all were present, but from 2013.
> Wireshark said it was using a WinPcap from August 2018... Uninstalled it
> and
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13881
--- Comment #207 from Gerrit Code Review ---
Change 31817 had a related patch set uploaded by Peter Wu:
QUIC: put coalesced packets in separate trees
https://code.wireshark.org/review/31817
--
You are receiving this mail because:
You
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13891
Christopher Maynard changed:
What|Removed |Added
Severity|Major |Normal
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15467
--- Comment #4 from Christopher Maynard ---
(In reply to Peter Wu from comment #3)
> You are actually seeing this on the 2.6 branch? That's interesting... I
> thought that only master had this issue which might cause sporadic
> Petri-Dish
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15467
--- Comment #3 from Peter Wu ---
You are actually seeing this on the 2.6 branch? That's interesting... I thought
that only master had this issue which might cause sporadic Petri-Dish test
failures.
Perhaps it is caused by Wireshark
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15467
--- Comment #2 from Christopher Maynard ---
(In reply to Christopher Maynard from comment #1)
> > There appears to be one such warning printed for nearly every non-extcap
> > interface. My system has 8 such interfaces and 7 warnings are
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15467
--- Comment #1 from Christopher Maynard ---
> There appears to be one such warning printed for nearly every non-extcap
> interface. My system has 8 such interfaces and 7 warnings are printed.
Apparently I can't count. There are 8
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14215
--- Comment #8 from Christopher Maynard ---
(In reply to Peter Wu from comment #6)
> Can you reliably reproduce this? I have seen this message in some
> sporadically failing tests, it might indicate some bigger problem. If you
> can
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14215
Christopher Maynard changed:
What|Removed |Added
See Also||https://bugs.wireshark.org/
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15467
Christopher Maynard changed:
What|Removed |Added
See Also||https://bugs.wireshark.org/
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15467
Bug ID: 15467
Summary: Some Wireshark command-line options don't work and
generate QWaitCondition warnings.
Product: Wireshark
Version: 2.6.6
Hardware: x86-64
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14215
--- Comment #7 from Christopher Maynard ---
(In reply to Guy Harris from comment #5)
> > Current behavior with Wireshark 2.6.6:
> > 1) "dumpcap -L": Prints the data link types supported by the *first*
> > interface
>
> First of *which*
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15453
--- Comment #9 from Neal Probert ---
(In reply to Anders Broman from comment #8)
> WSA Layer the first octets are 03 8x and the first 4 bits should be version
> according to the ASN1, assuming it's actually 8 bits (0x03) I tried that too
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15453
--- Comment #8 from Anders Broman ---
WSA Layer the first octets are 03 8x and the first 4 bits should be version
according to the ASN1, assuming it's actually 8 bits (0x03) I tried that too
but the decoding breaks down llater on any way.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15453
--- Comment #7 from Neal Probert ---
(In reply to Anders Broman from comment #6)
> (In reply to Neal Probert from comment #5)
> > Created attachment 16880 [details]
> > Sample PCAP with WSA for testing
> >
> > Hope this helps as this is
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15453
--- Comment #6 from Anders Broman ---
(In reply to Neal Probert from comment #5)
> Created attachment 16880 [details]
> Sample PCAP with WSA for testing
>
> Hope this helps as this is sent by the RSU with a WSA.
It looks like the
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15465
Peter Wu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15466
Stig Bjørlykke changed:
What|Removed |Added
Version|Git |2.6.6
--
You are receiving
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15466
--- Comment #1 from Gerrit Code Review ---
Change 31812 had a related patch set uploaded by Stig Bjørlykke:
Qt: Restore column width and visibility when switching profiles
https://code.wireshark.org/review/31812
--
You are receiving
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15466
Bug ID: 15466
Summary: Column width and hidden issues when switching profiles
Product: Wireshark
Version: Git
Hardware: All
OS: All
Status: UNCONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15465
Alexis La Goutte changed:
What|Removed |Added
CC||alexis.lagou...@gmail.com,
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13766
--- Comment #42 from Anders Broman ---
(In reply to Neal Probert from comment #40)
> (In reply to Anders Broman from comment #39)
> > (In reply to Neal Probert from comment #38)
> > > Now that it's working, there's still a bit of work to
60 matches
Mail list logo
