|
This page contains the changelog for version 2.11 of the ByteBlower. How to update your ByteBlower server is explained in following article:
2.11.8 (2020-06-25)
Fixes
- Fixed an issue where the performance of a 3x00 server dropped significantly on v2.11.6
- Adding timestamps to the standard output / error logs for the ByteBlower and MeetingPoint
- DHCP protocol implements the elapsed time value. DHCP servers which rely on this field for high availability will now work as expected.
2.11.6 (2020-04-15)
Fixes
- Improve the transmit time accuracy of Frame Blasting flows.
- The "Port.Create" method now works again on the ByteBlower 1200 series.
- The ByteBlowerPort's result history counters can now be consumed by multiple ByteBlowerPort objects (each ByteBlowerPort contains its own copy of the result history.)
- Configurator: IPv4 address validation failed when configuring static IP addresses on a management interface
2.11.4 (2020-02-20)
Fixes
- Fixed a bug which used unicast addresses in the DHCP requests. This could confuse some bridging devices which dropped the requests.
Misc
- To help our support engineers, we now add the server and meetingpoint version to the logs.
2.11.2 (2020-02-11)
This release primarily focusses on bugfixes.
One of the fixes changes the default behaviour of the DHCP client running on a ByteBlower Port. The DHCP Client used the broadcast DHCP-technique to obtain its IPv4 address. As some customers noticed, some devices flagged this DHCP traffic as a broadcast storm when performing DHCP on multiple ByteBlower Ports. This change in the ByteBlower DHCP client changes the default DHCP technique to the unicast technique, working around the limitation imposed by these devices. The DHCP technique (broadcast/unicast) can be configured using the ByteBlower API.
Enhancements
- Server: Added the possibility for the DHCP client to disable the BROADCAST bit in the DHCP flags. The ByteBlowerPort will then use unicast packets when possible.
Please note that this is now the default behaviour. Using our API it is possible to revert to the older broadcast technique when needed.
- Server: Added extra DHCP timing statistics (timestamps when the DHCP discover/offer/request/ack, DHCPv6 solicit, advertise, request, reply are sent or received)
- MeetingPoint: Android 10 is now added to the list of supported operating systems.
Fixes
- Server: Fixed a crash when a ByteBlowerPort was being destroyed and the IGMP or MLD protocols needed to transmit messages.
- Server: Fixes for IGMPv1 and IGMPv2 where an incorrect back-off interval was used.
- Server: Fixed an issue where IGMPv1 did check the group address too much.
- Configurator: Fixed a crash when the network configuration reached an inconsistent state.
- MeetingPoint: Fixed a crash when the process got an interrupt signal
2.11.0 (2019-12-04)
Enhancements
- The meetingpoint is aware of SSID, BSSID, RSSI, WiFi Channel and WiFi transmit rate on supported devices. To use these features you will also need to update the Wireless Endpoint on the device and the ByteBlower API installed on your computer
- The 24 port NBASE-T swtich for ByteBlower has been added to the byteblower-configurator. This makes it much easier tconfigure it.
- Unsupported Operating Systems and devices can be registered at the MeetingPoint. This makes them available for test-runs. To make it clear that we've not yet tuned our code for the system we do add the 'unsupported' to the name of the device.
Fixes
- When requesting the result history on a Wireless Endpoint, all results were returned instead of only the new ones. This resulted in growing histories (and thus memory usage) over time.
- Improve TCP performance for flows that have a high number of packets in flight.
- Fix packet duplication in Streams that have a small number of frames configured.
| 
(0 vote(s))