bugzilla-daemon | 1 Jan 16:42 2011

[Bug 5540] New: ipv6 display filter

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

           Summary: ipv6 display filter
           Product: Wireshark
           Version: unspecified
          Platform: x86-64
        OS/Version: Debian
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs <at> wireshark.org
        ReportedBy: j.paul.landers <at> gmail.com

Build Information:
Copyright 1998-2010 Gerald Combs <gerald <at> wireshark.org> and contributors.
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 with GTK+ 2.20.1, (32-bit) with GLib 2.24.2, with libpcap 1.1.1, with
libz 1.2.3.4, with POSIX capabilities (Linux), with libpcre 8.2, with SMI
0.4.8,
with c-ares 1.7.3, with Lua 5.1, with GnuTLS 2.8.6, with Gcrypt 1.4.5, with MIT
Kerberos, with GeoIP, with PortAudio V19-devel (built Nov 25 2010), without
AirPcap.

Running on Linux 2.6.32-5-686, with libpcap version 1.1.1, GnuTLS 2.8.6, Gcrypt
1.4.5.

Built using gcc 4.4.5.
(Continue reading)

bugzilla-daemon | 1 Jan 20:34 2011

[Bug 5445] Enable Bluetooth profile dissection on top of L2CAP and RFCOMM

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

Allan M. Madsen <allan.m <at> madsen.dk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #5617|0                           |1
        is obsolete|                            |
   Attachment #5688|                            |review_for_checkin?
               Flag|                            |

--- Comment #9 from Allan M. Madsen <allan.m <at> madsen.dk> 2011-01-01 11:34:17 PST ---
Created an attachment (id=5688)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=5688)
Updated patch to eliminate reported problems

--

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs <at> wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-request <at> wireshark.org?subject=unsubscribe

bugzilla-daemon | 1 Jan 21:26 2011

[Bug 5540] ipv6 display filter

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

Stephen Fisher <steve <at> stephen-fisher.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE

--- Comment #1 from Stephen Fisher <steve <at> stephen-fisher.com> 2011-01-01 13:26:15 MST ---

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

--

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs <at> wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-request <at> wireshark.org?subject=unsubscribe

bugzilla-daemon | 1 Jan 21:26 2011

[Bug 5538] ipv6.addr (etc) filter should be able to be specified by a network or prefix

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

Stephen Fisher <steve <at> stephen-fisher.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |j.paul.landers <at> gmail.com

--- Comment #1 from Stephen Fisher <steve <at> stephen-fisher.com> 2011-01-01 13:26:15 MST ---
*** Bug 5540 has been marked as a duplicate of this bug. ***

--

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs <at> wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-request <at> wireshark.org?subject=unsubscribe

bugzilla-daemon | 2 Jan 01:56 2011

[Bug 2426] SNMPv3 Engine ID registration

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

--- Comment #14 from Sake <sake <at> euronet.nl> 2011-01-01 16:56:33 PST ---
(In reply to comment #13)

> Until Lego is fixed...

Hmmm... I'm not sure if Lego wants to get fixed, see:
http://wiki.wireshark.org/LuisOntanon ;-)

--

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs <at> wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-request <at> wireshark.org?subject=unsubscribe

bugzilla-daemon | 2 Jan 02:32 2011

[Bug 2426] SNMPv3 Engine ID registration

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

--- Comment #15 from Walter Benton <wbenton <at> aa.aeonnet.ne.jp> 2011-01-02 10:32:04 JST ---
Then use my workaround... it still works for me as I don't do it that often!

--

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs <at> wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-request <at> wireshark.org?subject=unsubscribe

bugzilla-daemon | 2 Jan 05:28 2011

[Bug 5541] New: Custom Window Size Column Shows Two Values and Doesn't Sort Properly

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

           Summary: Custom Window Size Column Shows Two Values and Doesn't
                    Sort Properly
           Product: Wireshark
           Version: 1.5.x (Experimental)
          Platform: x86
        OS/Version: Windows Vista
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs <at> wireshark.org
        ReportedBy: Jim <at> agdatasystems.com

Created an attachment (id=5689)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=5689)
TCP Packets with Scaled Window Size Values

Build Information:
Version 1.5.0-SVN-35322 (SVN Rev 35322 from /trunk)

Copyright 1998-2011 Gerald Combs <gerald <at> wireshark.org> and contributors.
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 (32-bit) with GTK+ 2.16.6, with GLib 2.24.2, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with
(Continue reading)

bugzilla-daemon | 2 Jan 05:47 2011

[Bug 5541] Custom Window Size Column Shows Two Values and Doesn't Sort Properly

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

--- Comment #1 from Stephen Fisher <steve <at> stephen-fisher.com> 2011-01-01 21:47:38 MST ---
(In reply to comment #0)

> Shouldn't the two window size fields be identified by different field names so
> that they can be filtered on or added to custom columns independently? This
> would also correct the sorting issue.

This was a judgment call on my part when improving the display of the window
sizes recently.  It is only possible to show the scaled window size if the
3-way handshake for the TCP stream is in the current capture session/file.  The
preferences have also have to be enabled (the default; but it can be disabled
by turning off "window scaling" and/or "analyze TCP sequence numbers" in the
TCP protocol's preferences.)  Since the user of Wireshark may not realize if
these requirements are met, they won't know whether to use the display filter
for the scaled or normal window size.

You can use the "field occurrence" setting when adding custom columns to make
it show only the first (always the actual value from packet) or second (always
the scaled value or blank if it can't be computed) by changing field occurence
from "0" (all occurrences) to "1" or "2".

I also changed it to show the window size value from the packet on every packet
and then show the scaled value (a multiple of the packet's value known only
from the 3-way handshake earlier) for clarity in understanding how the TCP
protocol works.

--

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
(Continue reading)

bugzilla-daemon | 2 Jan 06:17 2011

[Bug 5541] Custom Window Size Column Shows Two Values and Doesn't Sort Properly

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

--- Comment #2 from Jim Aragon <Jim <at> agdatasystems.com> 2011-01-01 21:17:44 PST ---
Thanks for the explanation. The use of the "field occurrance" setting is new to
me, so I learned something.

A trace file may contain the 3-way handshake for some streams and not for
others. Unfortunately, there is no longer a single field that sorts properly
and has Wireshark's best idea of the window size: Scaled if the scaled value
can be calculated, otherwise unscaled.

From my perspective, it would be more useful if occurrence 2 contained the
unscaled value if the scaled value can't be calculated, rather than being
blank.

I recognize that this is a judgment call, so you can close the bug if this is
the expected behavior.

--

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs <at> wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-request <at> wireshark.org?subject=unsubscribe

bugzilla-daemon | 2 Jan 09:14 2011

[Bug 5445] Enable Bluetooth profile dissection on top of L2CAP and RFCOMM

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

Kovarththanan Rajaratnam <kovarththanan.rajaratnam <at> gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #5688|review_for_checkin?         |review_for_checkin+
               Flag|                            |

--- Comment #10 from Kovarththanan Rajaratnam <kovarththanan.rajaratnam <at> gmail.com> 2011-01-02
00:14:27 PST ---
(From update of attachment 5688)
Thanks.

Committed as revision 35323

--

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs <at> wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-request <at> wireshark.org?subject=unsubscribe


Gmane