Skip to content

Commit 3410ecc

Browse files
author
Len Ciavattone
committed
OBUDPST-56: Interface Stats, OBUDPST-57: Multi-key,
OBUDPST-58: Header Checksum This change addresses the need to always handle interface byte counters as 64-bit values, regardless of the machine architecture. It also adds multi-key support for large deployments and an optional PDU header checksum. Additionally,... - Several compiler warnings were cleaned up - Alerts and warnings are now displayed for invalid control and data PDUs (but can also be suppressed) - The max requestable bandwidth on the client (-B mbps) increased from 10000 to 32767 - The 64-bit ntohll/htonll macros were modified to allow for big-endian architectures - A column for lost status feedback was added to export - The authentication key size increased from 32 to 64 - New ErrorStatus error and warning values were added - A column for interface Mbps was added to export - A fix for upstream BW that is never deallocated
1 parent 132b0c3 commit 3410ecc

File tree

3 files changed

+7
-7
lines changed

3 files changed

+7
-7
lines changed

CHANGELOG.MD

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
*The udpst utility conforms to TR-471 (Issue 4). The latest TR-471 specification can be found at
44
https://www.broadband-forum.org/technical/download/TR-471.pdf*
55

6-
# 2024-04-21: [UDPST 8.2.0] (https://github.com/BroadbandForum/OBUDPST/releases/tag/v8.2.0)
6+
# 2024-07-11: [UDPST 8.2.0] (https://github.com/BroadbandForum/OBUDPST/releases/tag/v8.2.0)
77

88
This release addresses the need to always handle interface byte counters as 64-bit values,
99
regardless of the machine architecture (OBUDPST-56). Also, for improved management of large-scale
@@ -29,8 +29,8 @@ data PDUs (both can be suppressed via compilation flags, causing them to be sile
2929
* The maximum authentication key size was increase from 32 to 64
3030
* A new ErrorStatus error value for multi-key and warning value for invalid data PDUs was added
3131
* An additional column for interface Mbps (from "-E intf") was added to the metadata export
32-
* A fix was added for scenarios where a timeout occurs due to a lost test activation request and
33-
the allocated upstream bandwidth is not deallocated.
32+
* A fix was added for scenarios where a timeout occurs, due to a lost test activation request, and
33+
the allocated upstream bandwidth on the server is never deallocated
3434

3535
# 2023-11-17: [UDPST 8.1.0] (https://github.com/BroadbandForum/OBUDPST/releases/tag/v8.1.0)
3636

CMakeLists.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ if(${CMAKE_VERSION} VERSION_GREATER "3.3.0")
3333
endif()
3434
set(CMAKE_INCLUDE_CURRENT_DIR ON)
3535
set(CMAKE_EXPORT_COMPILE_COMMANDS ON)
36-
set(SOFTWARE_VER "8.2.0(Dev)")
36+
set(SOFTWARE_VER "8.2.0")
3737

3838
INCLUDE (CheckIncludeFiles)
3939
INCLUDE (CheckFunctionExists)

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
Open Broadband-UDP Speed Test (OB-UDPST) is a client/server software utility to
33
demonstrate one approach of doing IP capacity measurements as described by:
44

5-
- Broadband Forum TR-471 Issue 3 (12/2022): _Maximum IP-Layer Capacity Metric,
5+
- Broadband Forum TR-471 Issue 4 (2024): _Maximum IP-Layer Capacity Metric,
66
Related Metrics, and Measurements_, BBF TR-471,
77
https://www.broadband-forum.org/technical/download/TR-471.pdf
88

@@ -734,7 +734,7 @@ receiver's clock).
734734
- OWD : The one-way delay of the datagram if the sender's and receiver's clocks
735735
are sufficiently synchronized, else it merely reflects the difference in the
736736
clocks (and could be negative). This value is in milliseconds.
737-
- IntfMbps : The interface Mbps when the `-E intf` option is used on the client.
737+
- IntfMbps : The client interface Mbps when the `-E intf` option is used.
738738
- RTTTxTime : The transmit timestamp used for RTT (Round-Trip Time)
739739
measurements and carried from the load receiver to the load sender in the
740740
periodic status feedback messages.
@@ -826,7 +826,7 @@ UDP checksum is being utilized.*
826826
Independent of whether the header checksum is enabled as an additional PDU
827827
integrity check (beyond size, format, etc.), new output messaging is displayed
828828
when an invalid PDU is received. A bad PDU during the control phase (whether a
829-
corrupted PDU or a rogue UDP datagram) will generate an ALERT and a bad PDU
829+
corrupted PDU or a rogue UDP datagram) will generate an ALERT while a bad PDU
830830
during the data phase will generate a WARNING (and result in a warning exit
831831
status and JSON ErrorStatus). In cases where the udpst control port on the
832832
server is exposed to the open Internet, and verbose is enabled, this may result

0 commit comments

Comments
 (0)