[Wireshark-bugs] [Bug 13985] Wireshark does not completely decode 802.11v BSS Transition Management Requests

[bugzilla-daemon]

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

Alexis La Goutte  changed:

   What|Removed |Added

 CC||alexis.lagou...@gmail.com

-- 
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 10922] wireshark QT could not jump to right time stamp in packet list pane upon clicking a point on IO graph if Time of day is selected.

[bugzilla-daemon]

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

Travis  changed:

   What|Removed |Added

 CC||kyfe...@gmail.com
   Priority|Low |Medium

--- Comment #1 from Travis  ---
I also see this issue. I'm using this version:


Version 2.2.8 (v2.2.8-0-ga9ebe59292)

Copyright 1998-2017 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.6.2, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows 10, build 14393, with locale English_United
States.1252, with WinPcap version 4.1.3 (packet.dll version 0.93), based on
libpcap version 1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with
Gcrypt
1.6.2, without AirPcap.
Intel(R) Core(TM) i7-6650U CPU @ 2.20GHz (with SSE4.2), with 8117MB of physical
memory.

-- 
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 13957] I cannot create an account due to broken recaptcha on form.

[bugzilla-daemon]

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

--- Comment #5 from Gerald Combs  ---
(In reply to James Eck from comment #4)
> Unable to create an account. I couldn't find a register link at all, but
> when I tried to connect my wordpress I got the following message: "New user
> registrations are disabled. New users cannot be registered at this time.
> Please sign in if you already have an account."

Can you try again?

-- 
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 13957] I cannot create an account due to broken recaptcha on form.

[bugzilla-daemon]

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

--- Comment #4 from James Eck  ---
Unable to create an account. I couldn't find a register link at all, but when I
tried to connect my wordpress I got the following message: "New user
registrations are disabled. New users cannot be registered at this time. Please
sign in if you already have an account."

-- 
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 13985] New: Wireshark does not completely decode 802.11v BSS Transition Management Requests

[bugzilla-daemon]

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

Bug ID: 13985
   Summary: Wireshark does not completely decode 802.11v BSS
Transition Management Requests
   Product: Wireshark
   Version: 2.2.6
  Hardware: x86
OS: Windows 7
Status: UNCONFIRMED
  Severity: Enhancement
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: giantsn...@gmail.com
  Target Milestone: ---

Created attachment 15783
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15783=edit
Some BSS Transition Management Request frames

Build Information:
Version 2.2.6 (v2.2.6-0-g32dac6a)

Copyright 1998-2017 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.6.1, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale
English_United States.1252, with WinPcap version 4.1.3 (packet.dll version
4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with
GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz (with SSE4.2), with 8072MB of physical
memory.


Built using Microsoft Visual C++ 12.0 build 40629

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
The candidate list entries in an 802.11v BSS Transition Management Request are
not decoded by Wireshark. The specific field name is 

wlan_mgt.fixed.bss_transition_candidate_list_entries

The entries in the data are in the same format as the 802.11k Neighbor Report
frame (wlan_mgt.tag.number = 0x34), and the elements should match all
dissectors under wwlan_mgt.nreport.

I'm attaching capture with a BSS Transition Management Request frame that has a
candidate list (with one candidate). It is in Peekremote format so you might
have to decode UDP  to Peekremote.

Thank you

-- 
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 13984] "tshark -G ?" doesn't provide expected help

[bugzilla-daemon]

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

--- Comment #8 from Guy Harris  ---
How about "-G help"?  We probably won't have any registry for help, and if we
do we can call it "protocolhelp" or whatever, and "help" contains no wildcards
and thus won't give unpredictable behavior.

-- 
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 13984] "tshark -G ?" doesn't provide expected help

[bugzilla-daemon]

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

--- Comment #7 from Gerald Combs  ---
(In reply to Pascal Quantin from comment #6)
> As we also support the '-G -?' syntax, should we suggest it in the help
> instead?

I know it's not very likely, but it's possible to break "-?":


$ touch ./-a
$ tshark -G -?
tshark: Invalid "-a" option for -G flag, enter -G ? for more help.


-- 
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 13984] "tshark -G ?" doesn't provide expected help

[bugzilla-daemon]

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

--- Comment #6 from Pascal Quantin  ---
As we also support the '-G -?' syntax, should we suggest it in the help
instead?

-- 
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 13984] "tshark -G ?" doesn't provide expected help

[bugzilla-daemon]

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

--- Comment #5 from Gerald Combs  ---
Given that ? is a globbing character in most shells, the output of `tshark -G
?` depends on having any single-character filenames in your directory.

For example, bash on macOS prints the usage summary when no single-character
file is present and an error message if one is:


$ ls ?
ls: ?: No such file or directory

$ tshark -G ? | head -5
TShark (Wireshark) 2.5.0 (v2.5.0rc0-648-gfe0e6e3)

Usage: tshark -G [report]

Glossary table reports:

$ touch a

$ ./cmbuild/run/tshark -G ? | head -5
tshark: Invalid "a" option for -G flag, enter -G ? for more help.


cmd.exe on Windows 7 prints the default glossary if no single-character file is
present and the usage summary if one is:


c:\test>dir ?
 Volume in drive C has no label.
 Volume Serial Number is 68EB-7490

 Directory of c:\test

08/16/2017  01:59 PM  .
08/16/2017  01:59 PM  ..
   0 File(s)  0 bytes
   2 Dir(s)   3,862,257,664 bytes free

c:\test>tshark -G ? | head -5
P   Short Frame _ws.short
P   Malformed Packet_ws.malformed
P   Unreassembled Fragmented Packet _ws.unreassembled
F   Expert Info _ws.malformed.dissector_bug FT_NONE
_ws.malformed0x0
Dissector bug
F   Expert Info _ws.malformed.reassemblyFT_NONE
_ws.malformed0x0
Reassembly error

c:\test>touch a

c:\test>tshark -G ? | head -5
TShark (Wireshark) 2.5.0 (v2.5.0rc0-705-ge7284adcdf)

Usage: tshark -G [report]

Glossary table reports:


Would it make sense to print a usage summary when the length of the argument
passed to "-G" is 1?

-- 
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 13984] "tshark -G ?" doesn't provide expected help

[bugzilla-daemon]

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

--- Comment #4 from Pascal Quantin  ---
1/ My Linux is using glibc 2.24-9ubuntu2.2
2/ don't know
3/ maybe
4/ I can reproduce the issue on Windows 7 x64 and Windows 10 x64 using cmd.exe
(on Linux I use bash indeed).

-- 
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 13984] "tshark -G ?" doesn't provide expected help

[bugzilla-daemon]

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

--- Comment #3 from Guy Harris  ---
(In reply to Pascal Quantin from comment #2)
> Please ignore comment 1, 'G' is stored in optopt, not optarg. Instead it
> looks like getopt_long on Windows acts like this:

The version of getopt_long.c we use on Windows begins with:

/*
   Copied from glibc-2.15 modified to compile on Windows.

so it's a little surprising that it'd behave differently on Linux, given that
the majority of Linux distributions use glibc, as far as I know.

So either 1) that's an older version of glibc than the one on your Linux box,
2) your Linux distribution doesn't use the glibc getopt_long(), 3) we're
building it in a way that causes it to behave differently, or 4) it's due to a
difference in behavior between whatever Windows command line Christopher's
using and whatever UN*X command line (probably bash) you're using.

-- 
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 13984] "tshark -G ?" doesn't provide expected help

[bugzilla-daemon]

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

--- Comment #2 from Pascal Quantin  ---
Please ignore comment 1, 'G' is stored in optopt, not optarg. Instead it looks
like getopt_long on Windows acts like this:

If getopt() does not recognize an option character, it prints an error message
to stderr, stores the character in optopt, and returns '?'. The calling program
may prevent the error message by setting opterr to 0.

-- 
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 13984] "tshark -G ?" doesn't provide expected help

[bugzilla-daemon]

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

Pascal Quantin  changed:

   What|Removed |Added

 CC||pascal.quan...@gmail.com
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Pascal Quantin  ---
The problem is specific to Windows: the command works fine on Linux.

It appears that the version of getopt_long() we use on Windows extracts treats
the command 'tshark -G ?' as being an option '?' with an associated 'G'
optional parameter instead of being an option 'G' with an associated '?'
parameter.

'tshark -G -?' works fine.

-- 
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 13984] New: "tshark -G ?" doesn't provide expected help

[bugzilla-daemon]

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

Bug ID: 13984
   Summary: "tshark -G ?" doesn't provide expected help
   Product: Wireshark
   Version: 2.4.0
  Hardware: x86-64
OS: Windows 10
Status: UNCONFIRMED
  Severity: Normal
  Priority: Low
 Component: TShark
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: christopher.mayn...@igt.com
  Target Milestone: ---

Build Information:
TShark (Wireshark) 2.4.0 (v2.4.0-0-g9be0fa500d)

Compiled (64-bit) with WinPcap (4_1_3), with GLib 2.42.0, with zlib 1.2.8, with
SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS 3.4.11, with Gcrypt
1.7.6, with MIT Kerberos, with GeoIP, with nghttp2 1.14.0, with LZ4, with
Snappy, with libxml2 2.9.4.

Running on 64-bit Windows 10, build 14393, with AMD A10-6700 APU with
Radeon(tm)

HD Graphics(with SSE4.2), with 7368 MB of physical memory, with locale
English_United States.1252, with WinPcap version 4.1.3 (packet.dll version
4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with
GnuTLS 3.4.11, with Gcrypt 1.7.6.

Built using Microsoft Visual C++ 14.0 build 24215
--
Running "tshark -G ?" should provide help about the various report types.  It
does not.  Instead, it just dumps all field information.

tshark.exe -G foo
tshark: Invalid "foo" option for -G flag, enter -G ? for more help.

tshark.exe -G ?
P   Short Frame _ws.short
P   Malformed Packet_ws.malformed
P   Unreassembled Fragmented Packet _ws.unreassembled
F   Expert Info _ws.malformed.dissector_bug FT_NONE _ws.malformed
0x0 Dissector bug
F   Expert Info _ws.malformed.reassemblyFT_NONE _ws.malformed
0x0 Reassembly error
F   Expert Info _ws.malformed.expertFT_NONE _ws.malformed
0x0 Malformed Packet (Exception occurred)
P   Type Length Mismatch_ws.type_length

...

-- 
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 13024] Wireshark crash when end capturing with "Update list of packets in real-time" option off

[bugzilla-daemon]

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

--- Comment #3 from Gerrit Code Review  ---
Change 23095 had a related patch set uploaded by Erik de Jong:
Fix: Segfault when "Update list of packets in real time" is unchecked

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

-- 
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 13983] QuickBooks Payroll Support 18003496921 Number QuickBooks Payroll Tech Support Number

[bugzilla-daemon]

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

jamesdelvin  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

-- 
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 13983] New: QuickBooks Payroll Support 18003496921 Number QuickBooks Payroll Tech Support Number

[bugzilla-daemon]

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

Bug ID: 13983
   Summary: QuickBooks Payroll Support 18003496921 Number
QuickBooks Payroll Tech Support Number
   Product: Wireshark
   Version: 2.2.6
  Hardware: x86
OS: Windows 7
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Build process
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: jamesdelv...@gmail.com
  Target Milestone: ---

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
QuickBooks Payroll Support 18003496921 Number QuickBooks Payroll Tech Support
Number
QuickBooks Payroll Support 18003496921 Number QuickBooks Payroll Tech Support
Number
QuickBooks Payroll Support 18003496921 Number QuickBooks Payroll Tech Support
Number
QuickBooks Payroll Support 18003496921 Number QuickBooks Payroll Tech Support
Number
QuickBooks Payroll Support 18003496921 Number QuickBooks Payroll Tech Support
Number
QuickBooks Payroll Support 18003496921 Number QuickBooks Payroll Tech Support
Number
QuickBooks Payroll Support 18003496921 Number QuickBooks Payroll Tech Support
Number
@#$@@#$@@#$@@#$1.800<349<6921=@= @ Quickbooks Payroll Technical Support phONE
NumBER! 1-800-349-6921 #$@@#$ @ #$Quickbooks Payroll Technical Support Tech
support 1-800-349-6921 @ Quickbooks Payroll Technical Support phONE NumbER
USA!JEETôßPppu? 1 800 349 6921 @ Quickbooks Payroll Technical Support
phONENumbER..,O»G??ô US 1-800-349-6921 @ Quickbooks Payroll Technical
Support help TELEPhoNE Number..,, ??ô@ Quickbooks Payroll Technical Support
help Number..,, ??ô@ Quickbooks Payroll Technical Support Tech support
Number..,, @ Quickbooks Payroll Technical Support Number..,, @ Quickbooks
Payroll Technical Support PhoNE Number..,, @ Quickbooks Payroll Technical
Support TELEPHonE NumbER.. 1-800-349-6921 ,, @ Quickbooks Payroll Technical
Support 24 hourNumber.Quickbooks Payroll Technical Support customer SuPpoRT
Number..,, @ Quickbooks Payroll Technical Support phONE NumbER, Intuit @
Quickbooks Payroll Technical Support phONE Number, @ Quickbooks Payroll
Technical Support Help Desk PhoNE Number, @ Quickbooks Payroll Technical
Support Tech supportnumber, @ Quickbooks Payroll Technical Support phONE
NumbER, @ Quickbooks Payroll Technical Support Enterprise1-800-349-6921 PHonE
NumbER, @ Quickbooks Payroll Technical Support 1-800-349-6921 SuPpoRT number, @
Quickbooks Payroll Technical Support TEchnical support number -1-800-349-6921-
PHonENumbER. It is very popular toll free number which vide by @ Quickbooks
Payroll Technical Support Tech support, @ Quickbooks Payroll Technical Support
Customer PhoNE Number, @ Quickbooks Payroll Technical Support CustomerNumber,
1-800-349-6921 @ Quickbooks Payroll Technical Support Customer SuPpoRT
PhoNENumber, @ Quickbooks Payroll Technical Support Customer SuPpoRT Number,@
Quickbooks Payroll Technical Support Customer Number, @ Quickbooks Payroll
Technical Support Customer Number, @ Quickbooks Payroll Technical Support Tech
support team PhoNEnumber. Call, @ Quickbooks Payroll Technical Support TEch
SuPpoRTPHonE NumbER, Intuit @ Quickbooks Payroll Technical Support TEchSuPpoRT
1-800-349-6921 PhoNENumber, @ Quickbooks Payroll Technical Support Help Desk
PhoNE Number, @ Quickbooks Payroll Technical Support TEch SuPpoRT number, @
Quickbooks Payroll Technical Support phONE NumbER, @ Quickbooks Payroll
Technical Support EnterprisePhoNE number, @ Quickbooks Payroll Technical
Support Tech support number, @ Quickbooks Payroll Technical Support
phONENumbER, @ Quickbooks Payroll Technical Support Tech support, @ Quickbooks
Payroll Technical Support Customer PhoNE Number, @ Quickbooks Payroll Technical
Support CustomerNumber, @ Quickbooks Payroll Technical Support Customer SuPpoRT
PhoNE Number, @ Quickbooks Payroll Technical Support Customer SuPpoRT Number, @
Quickbooks Payroll Technical Support Customer Number, @ Quickbooks Payroll
Technical Support Customer Number, @ Quickbooks Payroll Technical Support
EnterpriseSuPpoRT team PhoNE number, @ Quickbooks Payroll Technical Support
help number-@ Quickbooks Payroll Technical Support Number; @ Quickbooks Payroll
Technical Support help PHonENumbER, @ Quickbooks Payroll Technical Support
Number, @ Quickbooks Payroll Technical Support TEch SuPpoRT Toll freeNumber, @
Quickbooks Payroll Technical Support Tech support TELEPhoNE Number, @
Quickbooks Payroll Technical Support TEch SuPpoRT TELEPhoNE number, @
Quickbooks Payroll Technical Support TEch SuPpoRT number, @ Quickbooks Payroll
Technical Support Tech supportnumber, @ Quickbooks Payroll Technical Support
Tech support number, @ Quickbooks Payroll Technical Support 24/7 SuPpoRTPhoNE
number,@ Quickbooks Payroll Technical Support TELEPhoNE number @ Quickbooks
Payroll Technical Support Customer Service Helpline?for SuPpoRT? all 1800

[Wireshark-bugs] [Bug 13982] New: USA 1800-349-6921 QuickBooks Payroll Error Technical Support Phone Number

[bugzilla-daemon]

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

Bug ID: 13982
   Summary: USA 1800-349-6921 QuickBooks Payroll Error Technical
Support Phone Number
   Product: Wireshark
   Version: 2.2.6
  Hardware: x86
OS: Windows 7
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Build process
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: jamesdelv...@gmail.com
  Target Milestone: ---

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
USA 1800-349-6921 QuickBooks Payroll Error Technical Support Phone Number
USA 1800-349-6921 QuickBooks Payroll Error Technical Support Phone Number
USA 1800-349-6921 QuickBooks Payroll Error Technical Support Phone Number
USA 1800-349-6921 QuickBooks Payroll Error Technical Support Phone Number
USA 1800-349-6921 QuickBooks Payroll Error Technical Support Phone Number
USA 1800-349-6921 QuickBooks Payroll Error Technical Support Phone Number
USA 1800-349-6921 QuickBooks Payroll Error Technical Support Phone Number
@#$@@#$@@#$@@#$1.800<349<6921=@= @ Quickbooks Payroll Technical Support phONE
NumBER! 1-800-349-6921 #$@@#$ @ #$Quickbooks Payroll Technical Support Tech
support 1-800-349-6921 @ Quickbooks Payroll Technical Support phONE NumbER
USA!JEETôßPppu? 1 800 349 6921 @ Quickbooks Payroll Technical Support
phONENumbER..,O»G??ô US 1-800-349-6921 @ Quickbooks Payroll Technical
Support help TELEPhoNE Number..,, ??ô@ Quickbooks Payroll Technical Support
help Number..,, ??ô@ Quickbooks Payroll Technical Support Tech support
Number..,, @ Quickbooks Payroll Technical Support Number..,, @ Quickbooks
Payroll Technical Support PhoNE Number..,, @ Quickbooks Payroll Technical
Support TELEPHonE NumbER.. 1-800-349-6921 ,, @ Quickbooks Payroll Technical
Support 24 hourNumber.Quickbooks Payroll Technical Support customer SuPpoRT
Number..,, @ Quickbooks Payroll Technical Support phONE NumbER, Intuit @
Quickbooks Payroll Technical Support phONE Number, @ Quickbooks Payroll
Technical Support Help Desk PhoNE Number, @ Quickbooks Payroll Technical
Support Tech supportnumber, @ Quickbooks Payroll Technical Support phONE
NumbER, @ Quickbooks Payroll Technical Support Enterprise1-800-349-6921 PHonE
NumbER, @ Quickbooks Payroll Technical Support 1-800-349-6921 SuPpoRT number, @
Quickbooks Payroll Technical Support TEchnical support number -1-800-349-6921-
PHonENumbER. It is very popular toll free number which vide by @ Quickbooks
Payroll Technical Support Tech support, @ Quickbooks Payroll Technical Support
Customer PhoNE Number, @ Quickbooks Payroll Technical Support CustomerNumber,
1-800-349-6921 @ Quickbooks Payroll Technical Support Customer SuPpoRT
PhoNENumber, @ Quickbooks Payroll Technical Support Customer SuPpoRT Number,@
Quickbooks Payroll Technical Support Customer Number, @ Quickbooks Payroll
Technical Support Customer Number, @ Quickbooks Payroll Technical Support Tech
support team PhoNEnumber. Call, @ Quickbooks Payroll Technical Support TEch
SuPpoRTPHonE NumbER, Intuit @ Quickbooks Payroll Technical Support TEchSuPpoRT
1-800-349-6921 PhoNENumber, @ Quickbooks Payroll Technical Support Help Desk
PhoNE Number, @ Quickbooks Payroll Technical Support TEch SuPpoRT number, @
Quickbooks Payroll Technical Support phONE NumbER, @ Quickbooks Payroll
Technical Support EnterprisePhoNE number, @ Quickbooks Payroll Technical
Support Tech support number, @ Quickbooks Payroll Technical Support
phONENumbER, @ Quickbooks Payroll Technical Support Tech support, @ Quickbooks
Payroll Technical Support Customer PhoNE Number, @ Quickbooks Payroll Technical
Support CustomerNumber, @ Quickbooks Payroll Technical Support Customer SuPpoRT
PhoNE Number, @ Quickbooks Payroll Technical Support Customer SuPpoRT Number, @
Quickbooks Payroll Technical Support Customer Number, @ Quickbooks Payroll
Technical Support Customer Number, @ Quickbooks Payroll Technical Support
EnterpriseSuPpoRT team PhoNE number, @ Quickbooks Payroll Technical Support
help number-@ Quickbooks Payroll Technical Support Number; @ Quickbooks Payroll
Technical Support help PHonENumbER, @ Quickbooks Payroll Technical Support
Number, @ Quickbooks Payroll Technical Support TEch SuPpoRT Toll freeNumber, @
Quickbooks Payroll Technical Support Tech support TELEPhoNE Number, @
Quickbooks Payroll Technical Support TEch SuPpoRT TELEPhoNE number, @
Quickbooks Payroll Technical Support TEch SuPpoRT number, @ Quickbooks Payroll
Technical Support Tech supportnumber, @ Quickbooks Payroll Technical Support
Tech support number, @ Quickbooks Payroll Technical Support 24/7 SuPpoRTPhoNE
number,@ Quickbooks Payroll Technical Support TELEPhoNE number @ Quickbooks
Payroll Technical Support Customer Service Helpline?for SuPpoRT? all 1800
-349-6921/ NumberQuickbooks Payroll Technical Support Customer Care Number, @
Quickbooks 

[Wireshark-bugs] [Bug 13980] Spam

[bugzilla-daemon]

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

Anders Broman  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Severity|Major   |Trivial
Summary|18003-496921 Quickbooks Pos |Spam
   |Technical Support phONE |
   |NuMbER QuickBooks POS Tech  |
   |SupPort NuMber  |
 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 13981] New: CANADA 1800-349-6921 QuickBooks 2017 Technical Support Phone Number ! QuickBooks Support Number

[bugzilla-daemon]

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

Bug ID: 13981
   Summary: CANADA 1800-349-6921 QuickBooks 2017 Technical Support
Phone Number ! QuickBooks Support Number
   Product: Wireshark
   Version: 2.5.x (Experimental)
  Hardware: x86
OS: Windows 7
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: jamesdelv...@gmail.com
  Target Milestone: ---

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
CANADA 1800-349-6921 QuickBooks 2017 Technical Support Phone Number !
QuickBooks Support Number
CANADA 1800-349-6921 QuickBooks 2017 Technical Support Phone Number !
QuickBooks Support Number
CANADA 1800-349-6921 QuickBooks 2017 Technical Support Phone Number !
QuickBooks Support Number
@#$@@#$@@#$@@#$1.800<349<6921=@= @ Quickbooks POS Technical Support phONE
NumBER! 1-800-349-6921 #$@@#$ @ #$Quickbooks POS Technical Support Tech
support 1-800-349-6921 @ Quickbooks POS Technical Support phONE NumbER
USA!JEETôßPppu? 1 800 349 6921 @ Quickbooks POS Technical Support
phONENumbER..,O»G??ô US 1-800-349-6921 @ Quickbooks POS Technical Support
help TELEPhoNE Number..,, ??ô@ Quickbooks POS Technical Support help
Number..,, ??ô@ Quickbooks POS Technical Support Tech support Number..,, @
Quickbooks POS Technical Support Number..,, @ Quickbooks POS Technical Support
PhoNE Number..,, @ Quickbooks POS Technical Support TELEPHonE NumbER..
1-800-349-6921 ,, @ Quickbooks POS Technical Support 24 hourNumber.Quickbooks
POS Technical Support customer SuPpoRT Number..,, @ Quickbooks POS Technical
Support phONE NumbER, Intuit @ Quickbooks POS Technical Support phONE Number, @
Quickbooks POS Technical Support Help Desk PhoNE Number, @ Quickbooks POS
Technical Support Tech supportnumber, @ Quickbooks POS Technical Support phONE
NumbER, @ Quickbooks POS Technical Support Enterprise1-800-349-6921 PHonE
NumbER, @ Quickbooks POS Technical Support 1-800-349-6921 SuPpoRT number, @
Quickbooks POS Technical Support TEchnical support number -1-800-349-6921-
PHonENumbER. It is very popular toll free number which vide by @ Quickbooks POS
Technical Support Tech support, @ Quickbooks POS Technical Support Customer
PhoNE Number, @ Quickbooks POS Technical Support CustomerNumber, 1-800-349-6921
@ Quickbooks POS Technical Support Customer SuPpoRT PhoNENumber, @ Quickbooks
POS Technical Support Customer SuPpoRT Number,@ Quickbooks POS Technical
Support Customer Number, @ Quickbooks POS Technical Support Customer Number, @
Quickbooks POS Technical Support Tech support team PhoNEnumber. Call, @
Quickbooks POS Technical Support TEch SuPpoRTPHonE NumbER, Intuit @ Quickbooks
POS Technical Support TEchSuPpoRT 1-800-349-6921 PhoNENumber, @ Quickbooks POS
Technical Support Help Desk PhoNE Number, @ Quickbooks POS Technical Support
TEch SuPpoRT number, @ Quickbooks POS Technical Support phONE NumbER, @
Quickbooks POS Technical Support EnterprisePhoNE number, @ Quickbooks POS
Technical Support Tech support number, @ Quickbooks POS Technical Support
phONENumbER, @ Quickbooks POS Technical Support Tech support, @ Quickbooks POS
Technical Support Customer PhoNE Number, @ Quickbooks POS Technical Support
CustomerNumber, @ Quickbooks POS Technical Support Customer SuPpoRT PhoNE
Number, @ Quickbooks POS Technical Support Customer SuPpoRT Number, @
Quickbooks POS Technical Support Customer Number, @ Quickbooks POS Technical
Support Customer Number, @ Quickbooks POS Technical Support EnterpriseSuPpoRT
team PhoNE number, @ Quickbooks POS Technical Support help number-@ Quickbooks
POS Technical Support Number; @ Quickbooks POS Technical Support help
PHonENumbER, @ Quickbooks POS Technical Support Number, @ Quickbooks POS
Technical Support TEch SuPpoRT Toll freeNumber, @ Quickbooks POS Technical
Support Tech support TELEPhoNE Number, @ Quickbooks POS Technical Support TEch
SuPpoRT TELEPhoNE number, @ Quickbooks POS Technical Support TEch SuPpoRT
number, @ Quickbooks POS Technical Support Tech supportnumber, @ Quickbooks POS
Technical Support Tech support number, @ Quickbooks POS Technical Support 24/7
SuPpoRTPhoNE number,@ Quickbooks POS Technical Support TELEPhoNE number @
Quickbooks POS Technical Support Customer Service Helpline?for SuPpoRT? all
1800 -349-6921/ NumberQuickbooks POS Technical Support Customer Care Number, @
Quickbooks POS Technical Support Tech support team PhoNE number@ Quickbooks POS
Technical Support PhoNE, number, @ Quickbooks POS Technical Support
TEchnical SuPpoRT number, @ Quickbooks POS Technical Support phONE NumbER, @
Quickbooks POS Technical Support TEchnical SuPpoRT, @ Quickbooks POS Technical
Support Customer Service PhoNE Number, @ Quickbooks POS Technical Support
Customer ServiceNumber, @ Quickbooks POS 

[Wireshark-bugs] [Bug 13980] New: 18003-496921 Quickbooks Pos Technical Support phONE NuMbER QuickBooks POS Tech SupPort NuMber

[bugzilla-daemon]

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

Bug ID: 13980
   Summary: 18003-496921 Quickbooks Pos Technical Support phONE
NuMbER QuickBooks POS Tech SupPort NuMber
   Product: Wireshark
   Version: 2.5.x (Experimental)
  Hardware: x86
OS: Windows 7
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Capture file support (libwiretap)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: jamesdelv...@gmail.com
  Target Milestone: ---

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
18003-496921 Quickbooks Pos Technical Support phONE NuMbER QuickBooks POS Tech
SupPort NuMber
18003-496921 Quickbooks Pos Technical Support phONE NuMbER QuickBooks POS Tech
SupPort NuMber
18003-496921 Quickbooks Pos Technical Support phONE NuMbER QuickBooks POS Tech
SupPort NuMber
@#$@@#$@@#$@@#$1.800<349<6921=@= @ Quickbooks POS Technical Support phONE
NumBER! 1-800-349-6921 #$@@#$ @ #$Quickbooks POS Technical Support Tech
support 1-800-349-6921 @ Quickbooks POS Technical Support phONE NumbER
USA!JEETôßPppu? 1 800 349 6921 @ Quickbooks POS Technical Support
phONENumbER..,O»G??ô US 1-800-349-6921 @ Quickbooks POS Technical Support
help TELEPhoNE Number..,, ??ô@ Quickbooks POS Technical Support help
Number..,, ??ô@ Quickbooks POS Technical Support Tech support Number..,, @
Quickbooks POS Technical Support Number..,, @ Quickbooks POS Technical Support
PhoNE Number..,, @ Quickbooks POS Technical Support TELEPHonE NumbER..
1-800-349-6921 ,, @ Quickbooks POS Technical Support 24 hourNumber.Quickbooks
POS Technical Support customer SuPpoRT Number..,, @ Quickbooks POS Technical
Support phONE NumbER, Intuit @ Quickbooks POS Technical Support phONE Number, @
Quickbooks POS Technical Support Help Desk PhoNE Number, @ Quickbooks POS
Technical Support Tech supportnumber, @ Quickbooks POS Technical Support phONE
NumbER, @ Quickbooks POS Technical Support Enterprise1-800-349-6921 PHonE
NumbER, @ Quickbooks POS Technical Support 1-800-349-6921 SuPpoRT number, @
Quickbooks POS Technical Support TEchnical support number -1-800-349-6921-
PHonENumbER. It is very popular toll free number which vide by @ Quickbooks POS
Technical Support Tech support, @ Quickbooks POS Technical Support Customer
PhoNE Number, @ Quickbooks POS Technical Support CustomerNumber, 1-800-349-6921
@ Quickbooks POS Technical Support Customer SuPpoRT PhoNENumber, @ Quickbooks
POS Technical Support Customer SuPpoRT Number,@ Quickbooks POS Technical
Support Customer Number, @ Quickbooks POS Technical Support Customer Number, @
Quickbooks POS Technical Support Tech support team PhoNEnumber. Call, @
Quickbooks POS Technical Support TEch SuPpoRTPHonE NumbER, Intuit @ Quickbooks
POS Technical Support TEchSuPpoRT 1-800-349-6921 PhoNENumber, @ Quickbooks POS
Technical Support Help Desk PhoNE Number, @ Quickbooks POS Technical Support
TEch SuPpoRT number, @ Quickbooks POS Technical Support phONE NumbER, @
Quickbooks POS Technical Support EnterprisePhoNE number, @ Quickbooks POS
Technical Support Tech support number, @ Quickbooks POS Technical Support
phONENumbER, @ Quickbooks POS Technical Support Tech support, @ Quickbooks POS
Technical Support Customer PhoNE Number, @ Quickbooks POS Technical Support
CustomerNumber, @ Quickbooks POS Technical Support Customer SuPpoRT PhoNE
Number, @ Quickbooks POS Technical Support Customer SuPpoRT Number, @
Quickbooks POS Technical Support Customer Number, @ Quickbooks POS Technical
Support Customer Number, @ Quickbooks POS Technical Support EnterpriseSuPpoRT
team PhoNE number, @ Quickbooks POS Technical Support help number-@ Quickbooks
POS Technical Support Number; @ Quickbooks POS Technical Support help
PHonENumbER, @ Quickbooks POS Technical Support Number, @ Quickbooks POS
Technical Support TEch SuPpoRT Toll freeNumber, @ Quickbooks POS Technical
Support Tech support TELEPhoNE Number, @ Quickbooks POS Technical Support TEch
SuPpoRT TELEPhoNE number, @ Quickbooks POS Technical Support TEch SuPpoRT
number, @ Quickbooks POS Technical Support Tech supportnumber, @ Quickbooks POS
Technical Support Tech support number, @ Quickbooks POS Technical Support 24/7
SuPpoRTPhoNE number,@ Quickbooks POS Technical Support TELEPhoNE number @
Quickbooks POS Technical Support Customer Service Helpline?for SuPpoRT? all
1800 -349-6921/ NumberQuickbooks POS Technical Support Customer Care Number, @
Quickbooks POS Technical Support Tech support team PhoNE number@ Quickbooks POS
Technical Support PhoNE, number, @ Quickbooks POS Technical Support
TEchnical SuPpoRT number, @ Quickbooks POS Technical Support phONE NumbER, @
Quickbooks POS Technical Support TEchnical SuPpoRT, @ Quickbooks POS Technical
Support Customer Service PhoNE Number, @ Quickbooks POS Technical Support
Customer ServiceNumber, @ Quickbooks POS 

[Wireshark-bugs] [Bug 13979] OSPF v3 LSA Type not well parsed

[bugzilla-daemon]

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

Alexis La Goutte  changed:

   What|Removed |Added

 CC||alexis.lagou...@gmail.com
 Ever confirmed|0   |1
 Status|UNCONFIRMED |INCOMPLETE

--- Comment #1 from Alexis La Goutte  ---
Hi,

Can you attach a pcap with this error?

-- 
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 13979] New: OSPF v3 LSA Type not well parsed

[bugzilla-daemon]

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

Bug ID: 13979
   Summary: OSPF v3 LSA Type not well parsed
   Product: Wireshark
   Version: 2.4.0
  Hardware: x86
OS: Debian
Status: UNCONFIRMED
  Severity: Normal
  Priority: Low
 Component: TShark
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: gaetan.brio...@gmail.com
  Target Milestone: ---

Build Information:
tshark -v
TShark (Wireshark) 2.4.0 (6449245 from master.el6-2.4)

Copyright 1998-2017 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 libpcap, without POSIX capabilities, without libnl, with
GLib 2.44.1, with zlib 1.2.3, without SMI, without c-ares, with Lua 5.1.4, with
GnuTLS 3.5.11, with Gcrypt 1.4.5, with MIT Kerberos, without GeoIP, without
nghttp2, without LZ4, without Snappy, with libxml2 2.7.6.

Running on Linux 2.6.32-358.el6.x86_64, with   Intel(R) Xeon(R) CPU
E31230 @ 3.20GHz (with SSE4.2), with 32081 MB of physical memory, with locale
en_US.UTF-8, with libpcap version 1.7.2, with GnuTLS 3.5.11, with Gcrypt 1.4.5,
with zlib 1.2.3.

Built using gcc 6.3.0.
--
Hello,

I think an issue regarding OSPFv3 has been introduced in the latest version of
tshark (2.4.0).

This filter does not work anymore: ospf.v3.lsa == 0xa027

Moreover, I noticed the value of the lsa type is not well parsed. Only the last
byte of the type is used, not the first one:
Open Shortest Path First
OSPF Header
Version: 3
Message Type: LS Update (4)
Packet Length: 60
Source OSPF Router: 1.20.1.8
Area ID: 0.0.0.0 (Backbone)
Checksum: 0xd02f [correct]
Instance ID: IPv6 unicast AF (2)
Reserved: 00
LS Update Packet
Number of LSAs: 1
LSA-type 39 (Unknown), len 40
.000   0001 = LS Age (seconds): 1
0...    = Do Not Age: False
1...    = LSA Handling: Treat the LSA as if it had
link-local flooding scope
.01.    = Flooding Scope: Area Scoping - Flooded only
in originating area (0x1)
...0  0010 0111 = LS Type: Unknown (39)
Link State ID: 0.0.0.20
Advertising Router: 1.20.1.8
Sequence Number: 0x8035
Checksum: 0xf9ea
Length: 40
[Expert Info (Warning/Protocol): Unknown LSA Type 39]
[Unknown LSA Type 39]
[Severity level: Warning]
[Group: Protocol]

  00 00 00 00 00 03 00 ff 07 00 00 01 86 dd 6c 00   ..l.
0010  00 00 00 3c 59 ff fe 80 00 00 00 00 00 00 02 00   ... 39 so 0x27 and not 0xa027

-- 
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 13977] RSVP-TE P2MP Objects

[bugzilla-daemon]

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

--- Comment #6 from Alexander Okonnikov  ---
(In reply to Alexis La Goutte from comment #5)
> (In reply to Alexander Okonnikov from comment #4)
> > (In reply to Alexis La Goutte from comment #3)
> > > About
> > > 
> > > Also, SESSION object C-Type 13/14 has different format. Wireshark uses 
> > > field
> > > names from SESSION object C-Type 7/8 (RFC 3209, Section 4.6.1). For 
> > > example,
> > > Wireshark marks field "P2MP ID" of C-Type 13/14 as "Destination address" 
> > > (as
> > > for C-Type 7/8).
> > > 
> > > PSMP ID is a IPv4 address ? (for the display)
> > 
> > No, it is purely ID. As soon as this P2MP in nature, there are multiple
> > destination addresses (multiple receivers). In attached dump a vendor just
> > have chosen to use source address as an P2MP ID, but it is just
> > implementation decision. Another vendor uses P2MP ID starting from 1, for
> > example.
> 
> Display with hex or dec ?

I think that dec will be appropriate, as far as other fields in the object are
displayed in dec format.

-- 
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 13977] RSVP-TE P2MP Objects

[bugzilla-daemon]

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

--- Comment #5 from Alexis La Goutte  ---
(In reply to Alexander Okonnikov from comment #4)
> (In reply to Alexis La Goutte from comment #3)
> > About
> > 
> > Also, SESSION object C-Type 13/14 has different format. Wireshark uses field
> > names from SESSION object C-Type 7/8 (RFC 3209, Section 4.6.1). For example,
> > Wireshark marks field "P2MP ID" of C-Type 13/14 as "Destination address" (as
> > for C-Type 7/8).
> > 
> > PSMP ID is a IPv4 address ? (for the display)
> 
> No, it is purely ID. As soon as this P2MP in nature, there are multiple
> destination addresses (multiple receivers). In attached dump a vendor just
> have chosen to use source address as an P2MP ID, but it is just
> implementation decision. Another vendor uses P2MP ID starting from 1, for
> example.

Display with hex or dec ?

-- 
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 13978] Expression button limitations

[bugzilla-daemon]

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

eric?  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

-- 
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 13977] RSVP-TE P2MP Objects

[bugzilla-daemon]

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

--- Comment #4 from Alexander Okonnikov  ---
(In reply to Alexis La Goutte from comment #3)
> About
> 
> Also, SESSION object C-Type 13/14 has different format. Wireshark uses field
> names from SESSION object C-Type 7/8 (RFC 3209, Section 4.6.1). For example,
> Wireshark marks field "P2MP ID" of C-Type 13/14 as "Destination address" (as
> for C-Type 7/8).
> 
> PSMP ID is a IPv4 address ? (for the display)

No, it is purely ID. As soon as this P2MP in nature, there are multiple
destination addresses (multiple receivers). In attached dump a vendor just have
chosen to use source address as an P2MP ID, but it is just implementation
decision. Another vendor uses P2MP ID starting from 1, for example.

-- 
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 13978] New: Expression button limitations

[bugzilla-daemon]

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

Bug ID: 13978
   Summary: Expression button limitations
   Product: Wireshark
   Version: 2.4.0
  Hardware: x86
OS: Windows 7
Status: UNCONFIRMED
  Severity: Minor
  Priority: Low
 Component: GTK+ UI
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: erka...@gmail.com
  Target Milestone: ---

Created attachment 15782
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15782=edit
What the expression button currently allows for

Build Information:
Version 2.4.0 (v2.4.0-0-g9be0fa500d)
--
Would be lovely if user had the ability to tack on additional filters via the
expression button.  In Version 2.4.0 (v2.4.0-0-g9be0fa500d) the expression
button allows user to build one filter exclusively.  IE, tcp.srcport==443 &&
tcp.dstport==443

-- 
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 13977] RSVP-TE P2MP Objects

[bugzilla-daemon]

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

--- Comment #3 from Alexis La Goutte  ---
About

Also, SESSION object C-Type 13/14 has different format. Wireshark uses field
names from SESSION object C-Type 7/8 (RFC 3209, Section 4.6.1). For example,
Wireshark marks field "P2MP ID" of C-Type 13/14 as "Destination address" (as
for C-Type 7/8).

PSMP ID is a IPv4 address ? (for the display)

-- 
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 13232] Buildbot crash output: fuzz-2016-12-09-9689.pcap

[bugzilla-daemon]

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

--- Comment #37 from Michael Mann  ---
*** Bug 13936 has been marked as a duplicate of this bug. ***

-- 
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 13936] Buildbot crash output: fuzz-2017-07-30-7572.pcap

[bugzilla-daemon]

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

Michael Mann  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Michael Mann  ---


*** This bug has been marked as a duplicate of bug 13232 ***

-- 
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 13232] Buildbot crash output: fuzz-2016-12-09-9689.pcap

[bugzilla-daemon]

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

--- Comment #36 from Michael Mann  ---
*** Bug 13954 has been marked as a duplicate of this bug. ***

-- 
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 13954] Buildbot crash output: fuzz-2017-08-07-5383.pcap

[bugzilla-daemon]

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

Michael Mann  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Michael Mann  ---


*** This bug has been marked as a duplicate of bug 13232 ***

-- 
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 13977] RSVP-TE P2MP Objects

[bugzilla-daemon]

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

Alexis La Goutte  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||alexis.lagou...@gmail.com
 Status|UNCONFIRMED |CONFIRMED

-- 
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 13977] RSVP-TE P2MP Objects

[bugzilla-daemon]

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

--- Comment #2 from Alexander Okonnikov  ---
Created attachment 15781
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15781=edit
RSVP Resv for P2MP LSP

-- 
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 13977] RSVP-TE P2MP Objects

[bugzilla-daemon]

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

--- Comment #1 from Alexander Okonnikov  ---
Created attachment 15780
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15780=edit
RSVP Path for P2MP LSP

-- 
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 13977] New: RSVP-TE P2MP Objects

[bugzilla-daemon]

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

Bug ID: 13977
   Summary: RSVP-TE P2MP Objects
   Product: Wireshark
   Version: 2.5.x (Experimental)
  Hardware: x86
OS: Linux
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: alexander.okonni...@gmail.com
  Target Milestone: ---

Build Information:
TShark (Wireshark) 2.5.0-694-g35f9349 (v2.5.0rc0-694-g35f9349)

Copyright 1998-2017 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 libpcap, without POSIX capabilities, without libnl, with
GLib 2.50.3, with zlib 1.2.8, with SMI 0.4.8, without c-ares, without Lua,
without GnuTLS, with Gcrypt 1.7.6-beta, without Kerberos, without GeoIP,
without
nghttp2, without LZ4, without Snappy, without libxml2.

Running on Linux 4.9.0-3-amd64, with Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz
(with SSE4.2), with 31604 MB of physical memory, with locale ru_RU.UTF-8, with
libpcap version 1.8.1, with Gcrypt 1.7.6-beta, with zlib 1.2.8.

Built using gcc 6.3.0 20170516.

--
RSVP-TE Extensions for P2MP LSPs (RFC 4875) are not supported.

RSVP Path and Resv messages dumps are attached.

Path:

SENDER_TEMPLATE (Class = 11, C-Type = 12/13): Format is specified in RFC 4875,
Section 19.2;

S2L_SUB_LSP (Class = 50, C-Type = 1/2): Format is specified in RFC 4875,
Section 19.3;

Also, SESSION object C-Type 13/14 has different format. Wireshark uses field
names from SESSION object C-Type 7/8 (RFC 3209, Section 4.6.1). For example,
Wireshark marks field "P2MP ID" of C-Type 13/14 as "Destination address" (as
for C-Type 7/8).

Resv:

SESSION object - the same as for Path message;

FILTER_SPEC (Class = 10, C-Type = 12/13): Format is described in RFC 4875,
Section 19.4 (the same format as for SENDER_TEMPLATE);

S2L_SUB_LSP (Class = 50, C-Type = 1/2): The same as for Path message.

-- 
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 13976] New: jarkontol

[bugzilla-daemon]

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

Bug ID: 13976
   Summary: jarkontol
   Product: Web sites
   Version: N/A
  Hardware: x86
OS: Windows 7
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Ask - ask.wireshark.org
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: shapuli...@yahoo.com
  Target Milestone: ---

Created attachment 15779
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15779=edit
eh asu

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
pekok view

-- 
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 13938] RADIUS: Filter issue when Extended attributes defined in dictionary

[bugzilla-daemon]

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

João Valverde  changed:

   What|Removed |Added

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

-- 
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 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

[bugzilla-daemon]

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

--- Comment #33 from conall.prenderg...@anam.com ---
Verified this latest build on this issue as well as the issues described at
13739, and also with a single continue.

Good work here Pascal, enjoy your vacation :)

-- 
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 13866] NBAP over SCTP heuristic dissector required

[bugzilla-daemon]

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

Alexis La Goutte  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||alexis.lagou...@gmail.com

-- 
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 13938] RADIUS: Filter issue when Extended attributes defined in dictionary

[bugzilla-daemon]

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

--- Comment #12 from Marius Paliga  ---
Solution of Bug 13745 fixes also this issue.

This Bug can be closed.

-- 
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