https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2849
Summary: Bucket Leak Rate decoded incorrectly as bytes instead of
bits
Product: Wireshark
Version: 1.0.3
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Major
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: jinneemop@xxxxxxxxxxxx
Build Information:
Version 1.0.3 (SVN Rev 26134)
Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> 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.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with ADNS, with Lua 5.1, with GnuTLS 2.3.8, with Gcrypt 1.4.1, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.
Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
A trace on Gb interface of SGSN is made and PCU sends Flow Control MS message
to SGSN. The information element `Bucket Leak Rate' in the trace is decoded
incorrectly. It should be counted in bits, but on Wireshark it is counted in
bytes.
According to 3GPP 08.18 (Section 11.3.4 Bucket Leak Rate (R)), the information
element `Bucket Leak Rate' should be consisted by 4 octets, of which the last 2
octets is the R field. The R field is the binary encoding of the rate
information expressed in 100 bits/sec increments, starting from 0 x 100
bits/sec until 65535 x 100 bits/sec (6 Mbps). However on Wireshark this range
is 0 x 100 bytes/sec until 65535 x 100 bytes/sec.
See attachment for a sample.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
