ByteBlower Server 2.2 changelog
Posted by Tom Ghyselinck, Last modified by Tom Ghyselinck on 19 October 2016 03:58 PM

ByteBlower Server 2.2 changelog

2.2.6

Enhancements

  • No longer return zero timestamps over RPC. If a counter is not available then it is not included in the mapping. (So the client can throw UnavailableException.)
  • "First time" events in interval snapshots now return first time the event occurred in the interval. (They used to return value from cumulative snapshot.)
    • Rx.Timestamp.First.Get
    • Tx.Timestamp.First.Get
  • Added method HasSession to HTTP server. This is needed because we can't assume as server session will once the client is in connected state.
    • Example: $httpServer HasSession [ $httpClient ServerClientId.Get ]
  • Once a TCP session is established HTTP immediately starts sending. (There used to be a 10ms delay.)
  • The server will return a result code "HTTP/1.1 200 OK\r\n\r\n" when receiving a PUT request. (It used to return nothing.)
    This means that the HTTP client snapshots will now have Rx values (Rx.Timestamp.First/Last and Rx.ByteCount.Header/Total).
  • Server logs a warning message if router advertisement was rejected. The message also includes the reason why was rejected.
    e.g.
    • Rejecting router advertisement because its source IP is not link-local address
    • Rejecting router advertisement because its hop limit is not equal to 255
    • etc..
  • Server logs an info message for each prefixes found in a router advertisement.
    • Prefix entry has the L-flag set. We can use this prefix for on-link determination.
    • Prefix entry has the A-flag set. We can use this prefix fox stateless autoconfiguration.

Fixes

  • Fixed an issue on the ByteBlower 4100 which could case negative loss.
  • Fixed an invalid assertion on snapshot processing
  • Fixed handling of certain DHCPv6 messages

2.2.4

Enhancements

  • Improved TCP SACK efficiency.
  • 4100 series: Improved timing stability at line rate transmission with multiple streams.

Fixes

  • 4100 series: Fixed incorrect timing in mulitple burst timing modifier.
  • 2200 series: Fixed time synchronization of second network adapter to first one.
  • 2x00 and 4100 series: Fixed possible error during startup while obtaining network adapter time.
  • Reimplemented DHCP and DHCPv6 release.
  • Telnet client: Fixed hang trying to connect to remote IPv6 address when configured with local IPv4 address.
  • Fixed HTTP SessionInfo returning incorrect request type and value when performing time-based TCP test.

2.2.2

Enhancements

  • Improved TCP performance for devices with TCP ACK suppression.
  • Improved TCP rate limiting algorithm.
  • Minimized RPC overhead for result history.
    • Not returning any values which would be invalid (e.g. when no packets received)
    • Not returning snapshots when nothing received in a given interval (missing snapshots are generated at client-side since 2.2.0)

Fixes

  • Fixed incorrect assertion on 2100 series in some rare conditions.
  • Fixed possible threading issue when changing stream configuration during run (applies on all but 4100 series)
  • Fixed possible memory corruption in TCP when running high number of sessions (> 10000)
  • Fixed server crash when TCP received RST
  • Fixed issue where HTTP PUT received more data than transmitted.
  • Out-of-sequence detection: fixed sequence number reset when packet counters were cleared
  • Fixed DHCP and DHCPv6 handling maximum number of retransmissions as maximum number of transmissions.
  • 4100 series: Fixed stream history results returning incorrect snapshot with timestamp value 0
  • All but 4100 series: Fixed applying stream timing modifiers. Timing modifiers were no longer applied in 2.2.0.
  • Now throwing "InProgressError" instead of "ConfigError" when trying to configure objects which are currently "active".
    Applies to stream, TCP, HTTP

ByteBlower environment and update

  • ByteBlower configurator: Fixed button labels
  • ByteBlower configurator: Fixed default selected button when "discarding changes"
  • Fixed issue in updater: Clearing cache partition did not work which
    caused ByteBlower environment still running old version after update.

Known issues

  • 4100 series: multiple burst timing modifier timing is not correct.

2.2.0

Enhancements

  • Add 2200 series support
  • Telnet client protocol support is enabled again.
  • ARP, DHCP and DHCPv6 can now be inialized in parallel.
  • Implemented CUBIC TCP congestion avoidance algorithm (extension).
  • Improved TCP performance on all systems.
  • Improved general protocol stack performance on 4100 series for some test conditions.
  • Removed auto-announcement on the network (Avahi / zero-conf). This is no longer used since 2.0.0 clients.
  • Improved transmission stability on the 1x00 series.

Fixes

  • Fixed destruction of captures.
  • Fixed issue in out-of-sequence history result timestamps.
  • Fixed incorrect counters in IGMP and MLD protocol.
  • Fixed incorrect processing and possible assertion failure when receiving older-version IGMP queries.
  • Fixed some assertion failures for rare test conditions on 4100 series.
  • Fixed some assertion failure on 2100 series for specific test setup.
  • Fixed hang of server when performing test with > 10000 TCP sessions.
  • Fixed issue where Tx.Stream::Result.Get could take up to 30ms (when performin test with very low traffic rate).

ByteBlower environment and update

  • ByteBlower configurator now processes different notations for multiple DNS servers.
  • Add support in ByteBlower configurator for multiple adapters in 2200 series.
(0 vote(s))
Helpful
Not helpful

Comments (0)

We to help you!