This page contains the changelog for version 2.13 of the ByteBlower. How to update your ByteBlower server is explained in following article:
Server 2.13.4 (2021-09-16)
- The ByteBlower 5100 series update could hang due to incomplete configuration.
- The DHCP header option list now starts with "Message Type" as the first option. This is more conventional and some users rely on it for their testing.
Server 2.13.2 (2021-09-07)
- The speed of the nontrunk interface can now be configured in the port configuration. This will allow the ByteBlower server to match the transmission speed for specific ByteBlower Switches. As an example: The ByteBlower server can now limit a 100Gbit/s interface to 40Gbit/s when connected to a Netgear M4300 (40Gbit/s) switch.
- Fixed a bug where a ByteBlower Stream did not always report "OutOfResources" when the hardware limit is exceeded.
- The MeetingPoint did not push its version information to the WirelessEndpoint at registration. This could lead to backwards compatibility issues.
- The MeetingPoint HeartBeat connections with the WirelessEndpoints now have a specific keep-alive option. Dead peers will now be cleaned up.
- Fixed a PacketDump (capture) issue where data was received too slowly over the API when capturing specific frame sizes.
- The Wireless Endpoint Stream and TriggerBasic Interval results did not have the TimestampFirst and TimestampLast available.
- The Wireless Endpoint NetworkInfoResultHistory was missing intervals when using intervals not aligned to a second.
- The MeetingPoint did not implement a stub for SamplingIntervalDurationSet for the supported triggers, stream and frame. This resulted in a Technical error while ConfigError is more appropiate.
- Fix occasional spikes in latency measurements on the ByteBlower 4100. This completes the same bugfix in the previous version.
- The TCP MSS (Maximum Segment Size) option in a SYN-ACK now advertises the maximum segment size the TCP can receive. It is no longer affected by the MSS option in the original SYN request it is replying to.
- The alpha implementation of the latency Distribution trigger for the Wireless Endpoint is now available.
Operating System changes
The machine-id of the system was the same for all systems, causing multiple ByteBlower servers obtain the same IP address through DHCP. It is now generated at first boot time, fixing the symptoms. (5100 only)