[Wireshark-bugs] [Bug 15501] Add dissector for FSRVP

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15501

--- Comment #2 from Gerrit Code Review  ---
Change 32018 merged by Anders Broman:
Add FSRVP dissector

https://code.wireshark.org/review/32018

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15426] Add support for ARP Probe and ARP Announcement (RFC 5227)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15426

--- Comment #3 from Gerrit Code Review  ---
Change 32080 merged by Anders Broman:
ARP: Add support for ARP Probe and ARP Announcement (RFC 5227)

https://code.wireshark.org/review/32080

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473

--- Comment #11 from Gerrit Code Review  ---
Change 32081 merged by Anders Broman:
Modbus: Explictly check for request when using byte count in responses

https://code.wireshark.org/review/32081

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15520] New: Conversations > TCP > Follow Stream Broken

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15520

Bug ID: 15520
   Summary: Conversations > TCP > Follow Stream Broken
   Product: Wireshark
   Version: 3.0.0
  Hardware: x86
OS: Windows 10
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Qt UI
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: la...@chappellu.com
  Target Milestone: ---

Created attachment 16923
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16923&action=edit
Image: TCP Stream selected; follow stream error in conversations.

Build Information:
Version 3.1.0rc0-51-g5c445834 (v3.1.0rc0-51-g5c445834) 
Copyright 1998-2019 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later
 This is free software;
see the source for copying conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. 
Compiled (64-bit) with Qt 5.12.1, with WinPcap SDK (WpdPack) 4.1.2, with GLib
2.52.2, with zlib 1.2.11, with SMI 0.4.8, with c-ares 1.14.0, with Lua 5.2.4,
with GnuTLS 3.6.3 and PKCS #11 support, with Gcrypt 1.8.3, with MIT Kerberos,
with MaxMind DB resolver, with nghttp2 1.14.0, with LZ4, with Snappy, with
libxml2 2.9.9, with QtMultimedia, with AirPcap, with SBC, with SpanDSP, with
bcg729. 
Running on 64-bit Windows 10 (1803), build 17134, with Intel(R) Core(TM)
i7-3930K CPU @ 3.20GHz (with SSE4.2), with 16294 MB of physical memory, with
locale English_United States.1252, with Npcap version 0.99-r9, based on libpcap
version 1.8.1, with GnuTLS 3.6.3, with Gcrypt 1.8.3, without AirPcap, binary
plugins supported (11 loaded). Built using Microsoft Visual Studio 2017 (VC++
14.12, build 25835). 
Wireshark is Open Source Software released under the GNU General Public
License. 
Check the man page and http://www.wireshark.org for more information. 
--
Statistics | Conversations | TCP, select conversation and click "Follow
Stream."

Response "Error following stream" and "Please make sure you have a TCP packet
selected." 

See image.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15429] [Proposal] IEEE 802.15.4 TAP Link Type Specification

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15429

James Ko  changed:

   What|Removed |Added

  Attachment #16919|0   |1
is obsolete||

--- Comment #17 from James Ko  ---
Created attachment 16922
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16922&action=edit
IEEE 802.15.4 TAP Link Type Specification

Remove extra "IEEE 802.15.4" before each TLV description.
Fix TOC.
Fix SUN_PHY_INFORMATION TLV naming.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473

--- Comment #10 from Gerrit Code Review  ---
Change 32081 had a related patch set uploaded by Michael Mann:
Modbus: Explictly check for request when using byte count in responses

https://code.wireshark.org/review/32081

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15426] Add support for ARP Probe and ARP Announcement (RFC 5227)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15426

--- Comment #2 from Gerrit Code Review  ---
Change 32080 had a related patch set uploaded by Michael Mann:
ARP: Add support for ARP Probe and ARP Announcement (RFC 5227)

https://code.wireshark.org/review/32080

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473

--- Comment #9 from Guy Harris  ---
(In reply to Guy Harris from comment #8)
> (In reply to Christopher Maynard from comment #3)
> > ... where (reg_num - 0) is always greater than num_reg because num_reg is 0.
> > A possibly better solution in this case would be to check if num_reg is 0,
> 
> Would an even better solution be to check whether pkt_info->request_found is
> true?

And:

* Should we provide a protocol error expert info for requests with a num_reg of
0, as, in the V1.1b3 spec, the "Quantity Of" fields have values in the range of
1 to {max}?

* If we *do* have the request for a response, should we check whether the
quantity of {coils, inputs, registers} from the request matches the byte count
in the response, and provide a protocol error expert info for the response if
they don't match, or is it valid to provide fewer values than were requested?

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473

--- Comment #8 from Guy Harris  ---
(In reply to Christopher Maynard from comment #3)
> (In reply to bugzilla from comment #0)
> > The other pcap does only include the response, and in this case I was
> > expected wireshark to decode/display the whole 504 bits as it has no access
> > to the request frame and therefore can not known how many bits where
> > requested.
> 
> I think you meant to say, "The other pcap does not include the *request*".

If "only" in "does only include the response" means "only the response, not the
corresponding request", then the two are equivalent.

> ... where (reg_num - 0) is always greater than num_reg because num_reg is 0.
> A possibly better solution in this case would be to check if num_reg is 0,

Would an even better solution be to check whether pkt_info->request_found is
true?

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15454] Dissection of CAN packets based on a DBC specification

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15454

Michael Mann  changed:

   What|Removed |Added

   Severity|Normal  |Enhancement
 Ever confirmed|0   |1
 CC||mman...@netscape.net
 Status|UNCONFIRMED |CONFIRMED

--- Comment #6 from Michael Mann  ---
(In reply to Maksim Salau from comment #4)
> Created attachment 16876 [details]
> Sample J1939 type DBC file

What exactly is this and what other Wireshark constructs would you equate it
to?

Is this similar to ASN.1 definitions where you want a "dbc to dissector" tool
that will generate a C code dissector from the data in the .dbc file? (that in
this case would register handlers for the j1939.pgn dissector table) 

Is this supposed to be dynamically loaded at runtime and the J1939 dissector
would create a "database of hf_ fields" based on the information in the .dbc
file(s)?

Is there a DBC spec that explains the fields in the file?

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15415] Add support for Mist's vendor specific IE (AP Name) in IEEE 802.11 dissector

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15415

Michael Mann  changed:

   What|Removed |Added

 OS|Mac OS X 10.4   |All
   Hardware|x86 |All

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15519] BGP as_path_segment has no value to use

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15519

--- Comment #1 from Gerrit Code Review  ---
Change 32078 had a related patch set uploaded by Jaap Keuter:
BGP: Dissector lacks value for as_path_segment field

https://code.wireshark.org/review/32078

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15415] Add support for Mist's vendor specific IE (AP Name) in IEEE 802.11 dissector

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15415

Michael Mann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15415] Add support for Mist's vendor specific IE (AP Name) in IEEE 802.11 dissector

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15415

--- Comment #1 from Gerrit Code Review  ---
Change 31476 merged by Michael Mann:
ieee80211: Add dissector for Mist vendor specific IE

https://code.wireshark.org/review/31476

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473

Michael Mann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473

--- Comment #7 from Gerrit Code Review  ---
Change 32077 merged by Michael Mann:
Modbus: If response packet is not found, base registers/coils on byte count.

https://code.wireshark.org/review/32077

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15519] New: BGP as_path_segment has no value to use

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15519

Bug ID: 15519
   Summary: BGP as_path_segment has no value to use
   Product: Wireshark
   Version: 2.6.6
  Hardware: x86-64
   URL: https://ask.wireshark.org/question/7303
OS: Debian
Status: IN_PROGRESS
  Severity: Normal
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: jaap.keu...@xs4all.nl
  Target Milestone: ---

Build Information:
Version 2.6.7 (v2.6.7rc0-47-g03c674b2) 
Copyright 1998-2019 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later
 This is free software;
see the source for copying conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. 
Compiled (64-bit) with Qt 5.11.3, with libpcap, with POSIX capabilities
(Linux), with libnl 3, with GLib 2.58.3, with zlib 1.2.11, with SMI 0.4.8, with
c-ares 1.14.0, with Lua 5.2.4, with GnuTLS 3.6.6, with Gcrypt 1.8.4, with MIT
Kerberos, with MaxMind DB resolver, without nghttp2, without LZ4, without
Snappy, with libxml2 2.9.4, with QtMultimedia, without SBC, with SpanDSP,
without bcg729. 
Running on Linux 4.19.0-1-amd64, with Intel(R) Core(TM)2 Duo CPU E6850 @
3.00GHz, with 3946 MB of physical memory, with locale LC_CTYPE=en_US.UTF-8,
LC_NUMERIC=nl_NL.UTF-8, LC_TIME=nl_NL.UTF-8, LC_COLLATE=nl_NL.UTF-8,
LC_MONETARY=nl_NL.UTF-8, LC_MESSAGES=en_US.UTF-8, LC_PAPER=en_US.UTF-8,
LC_NAME=en_US.UTF-8, LC_ADDRESS=en_US.UTF-8, LC_TELEPHONE=en_US.UTF-8,
LC_MEASUREMENT=nl_NL.UTF-8, LC_IDENTIFICATION=en_US.UTF-8, with libpcap version
1.8.1, with GnuTLS 3.6.6, with Gcrypt 1.8.4, with zlib 1.2.11, binary plugins
supported (14 loaded). Built using gcc 8.2.0.
--
>From the referenced question it became apparent you can't get the field value
for bgp.update.path_attribute.as_path_segment as the AS's are added as strings
to the protocol item after is was created without a value. This provides no
usable value when using tshark -T fields or when copying the value from the
GUI.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15518] New: Symbol not found: _clock_gettime in libgnutls.30.dylib

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15518

Bug ID: 15518
   Summary: Symbol not found: _clock_gettime in libgnutls.30.dylib
   Product: Wireshark
   Version: 3.0.0
  Hardware: x86
OS: OS X 10.11
Status: UNCONFIRMED
  Severity: Blocker
  Priority: Low
 Component: Qt UI
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: s...@bjorlykke.org
  Target Milestone: ---

Build Information:
Process:   Wireshark [1101]
Path:  /Applications/Wireshark.app/Contents/MacOS/Wireshark
Identifier:org.wireshark.Wireshark
Version:   3.0.0rc1-9-gfd6476fe (3.0.0rc1-9-gfd6476fe)
Code Type: X86-64 (Native)
Parent Process:??? [1]
Responsible:   Wireshark [1101]
User ID:   501

Date/Time: 2019-02-17 20:07:49.708 +0100
OS Version:Mac OS X 10.11.6 (15G22010)
Report Version:11
Anonymous UUID:D00074BC-470E-7863-9DA4-A128277EB845


Time Awake Since Boot: 670 seconds

System Integrity Protection: enabled

Crashed Thread:0  Dispatch queue: com.apple.main-thread

Exception Type:EXC_BREAKPOINT (SIGTRAP)
Exception Codes:   0x0002, 0x
Exception Note:EXC_CORPSE_NOTIFY

Application Specific Information:
/Applications/Wireshark.app/Contents/MacOS/../Frameworks/libgnutls.30.dylib

Dyld Error Message:
  Symbol not found: _clock_gettime
  Referenced from:
/Applications/Wireshark.app/Contents/MacOS/../Frameworks/libgnutls.30.dylib
  Expected in: /usr/lib/libSystem.B.dylib

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   dyld0x7fff638f8075 dyld_fatal_error + 1
1   dyld0x7fff638fb094
dyld::fastBindLazySymbol(ImageLoader**, unsigned long) + 139
2   libdyld.dylib   0x7fff94370262 dyld_stub_binder +
282
3   ??? 0x000110444008 0 + 4567875592
4   libgnutls.30.dylib  0x0001104302b5 wrap_nettle_rnd_init
+ 149 (rnd.c:232)
5   libgnutls.30.dylib  0x00011038c7b0 _gnutls_rnd_init +
32 (random.c:49)
6   libgnutls.30.dylib  0x00011037ea0c gnutls_global_init +
572 (gnutls_global.c:296)
7   libgnutls.30.dylib  0x00011037edb2 lib_init + 50
(gnutls_global.c:484)
8   dyld0x7fff6390a10b
ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 265
9   dyld0x7fff6390a284
ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40
10  dyld0x7fff639068bd
ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned
int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 305
11  dyld0x7fff63906852
ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned
int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 198
12  dyld0x7fff63906852
ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned
int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 198
13  dyld0x7fff63906852
ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned
int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 198
14  dyld0x7fff63906743
ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int,
ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 127
15  dyld0x7fff639069b3
ImageLoader::runInitializers(ImageLoader::LinkContext const&,
ImageLoader::InitializerTimingList&) + 75
16  dyld0x7fff638f90f1
dyld::initializeMainExecutable() + 208
17  dyld0x7fff638fcd98
dyld::_main(macho_header const*, unsigned long, int, char const**, char
const**, char const**, unsigned long*) + 3596
18  dyld0x7fff638f8276
dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header
const*, unsigned long*) + 512
19  dyld0x7fff638f8036 _dyld_start + 54

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x7fff63931290  rbx: 0x7f9de8d19020  rcx: 0x 
rdx: 0x
  rdi: 0x7fff63931400  rsi: 0x  rbp: 0x7fff56e17010 
rsp: 0x7fff56e16ff8
   r8: 0x7fff6391a04c   r9: 0x  r10: 0x7fff6391d462 
r11: 0x7fff63931400
  r12: 0x0001104447c8  r13: 0x7fff639305c8  r14: 0x7fff63931400 
r15: 0x
  rip: 0x7fff638f8075  rfl: 0x0

[Wireshark-bugs] [Bug 15515] SocketCAN dissector doesn't decode error frames

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15515

Michael Mann  changed:

   What|Removed |Added

   Severity|Major   |Enhancement
 OS|Linux   |All
   Hardware|x86 |All

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15499] 802.11 Authenticated mesh peering exchange (AMPE) frames not correctly parsed

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15499

Michael Mann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15499] 802.11 Authenticated mesh peering exchange (AMPE) frames not correctly parsed

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15499

--- Comment #6 from Gerrit Code Review  ---
Change 32025 merged by Michael Mann:
ieee80211: Fix parsing of Mesh Peering Management element

https://code.wireshark.org/review/32025

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15499] 802.11 Authenticated mesh peering exchange (AMPE) frames not correctly parsed

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15499

--- Comment #5 from Gerrit Code Review  ---
Change 32027 merged by Michael Mann:
ieee80211: Stop element parsing after MIC element

https://code.wireshark.org/review/32027

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15499] 802.11 Authenticated mesh peering exchange (AMPE) frames not correctly parsed

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15499

--- Comment #4 from Gerrit Code Review  ---
Change 32026 merged by Michael Mann:
ieee80211: Add parsing for MIC element

https://code.wireshark.org/review/32026

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473

--- Comment #6 from Gerrit Code Review  ---
Change 32077 had a related patch set uploaded by Michael Mann:
Modbus: If response packet is not found, base registers/coils on byte count.

https://code.wireshark.org/review/32077

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15517] New: Change ID links don't work

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15517

Bug ID: 15517
   Summary: Change ID links don't work
   Product: Web sites
   Version: N/A
  Hardware: ARM
OS: macOS 10.13
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Code review - code.wireshark.org
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: g...@alum.mit.edu
  Target Milestone: ---

Build Information:
Safari Version 12.0.3 (13606.4.5.3.1)
--
Links for "Ixx" change IDs don't work.  See, for example,
https://code.wireshark.org/review/c/32073/, where the link in the "Change-Id:"
line of the commit message takes you to
https://code.wireshark.org/q/Ie71520d1de70c5bdc9f664ff397930e277979b59, which
just says

Not Found

The requested URL /q/Ie71520d1de70c5bdc9f664ff397930e277979b59 was not found on
this server.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15344] Feature request - HTTP, add the field "request URI" to response

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15344

Guy Harris  changed:

   What|Removed |Added

   Hardware|x86 |All
 OS|Windows 10  |All

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15516] Expert Infos Incorrectly Displays Info Column instead of comment

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15516

--- Comment #2 from Guy Harris  ---
*And* it picks the contents of the *first* comment to be the text over *all*
the comments - it doesn't even give each comment its own section so that you
get to see the contents of each comment in the summary line.

I'm not sure whether changing *that* would be useful or not.  It would have the
advantage that you could see each comment's text (or, at least, the first line
of each comment's text), and *would* let users use the same comment (or, at
least, the same first line of comments) to arrange that all frames with the
same comment show up together.  I'm not sure that latter mechanism would count
as a useful feature, e.g. having a user tag all frames with some common
characteristic with comments the first line of which describes the
characteristic, with the rest of the comment possibly being different, giving
per-packet details.

But it seems *completely* bogus to use the first comment's first line there. 
If users would find it more useful to have a single entry for *all* frame
comments, the top-level item for the comments should be blank, not some
arbitrarily-chosen comment's first line.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15516] Expert Infos Incorrectly Displays Info Column instead of comment

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15516

Guy Harris  changed:

   What|Removed |Added

 OS|Windows 10  |All
   Hardware|x86 |All

--- Comment #1 from Guy Harris  ---
The code is probably treating PI_COMMENT the same way it treats other expert
infos.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe