ByteBlower Tcl API 2.5
Posted by Tom Ghyselinck, Last modified by Pieter Vandercammen on 31 August 2017 09:44 AM

This release of the Tcl API brings new features and bug fixes.

Type of service support on protocol stack

Some services suffer more from network delay than others. That's why both IPv4 and IPv6 are capable of defining the needed priorities in both delay and loss. For IPv4, the ToS field - renamed to DSCP field - is used for this, while IPv6 uses Class of Service.

ToS/DSCP (IPv4) and TrafficClass (IPv6) support has been enabled on the protocol stack:

  • HTTP Client (IPv4 and IPv6): Layer5.Http.Client::TypeOfService.Set
  • ICMP (IPv4): Layer3.IcmpEchoSession::TypeOfService.Set
  • ICMPv6 (IPv6): Layer3.Icmpv6EchoSession::TrafficClass.Set

This feature requires ByteBlower server >= 2.5.0

PPPoE Client

Now the ByteBlower server has support for PPPoE Client, we re-enabled the API in this release.

The client includes support for IPv4 and IPv6 via the Network Control Protocols IPCP, resp. IPv6CP. PPP authentication is possible via PAP or CHAP.

For more information, please check ourĀ documentation of the Layer2_5.Pppoe.Client.

This feature requires ByteBlower server >= 2.5.0

Backwards compatibility

The changes between to API 1.x and 2.x are significant. We won't provide the details of every change here but focus on the major ideas and changes. More info can be found in the documentation of the API.

The 2.x API supports ByteBlower server versions >= 2.1.0. Older versions of the server are no longer supported.

We preserved backwards compatibility at API level as much as possible. Many users will be able to just run the existing code using the new API. If this is not the cases, minor changes might be needed. If you don't succeed doing so, please don't hesitate to contact us for support.

Known issues

  • Unimplemented protocols
    • Real-time Transport Protocol (RTP)
    • Real-time Transport Control Protocol (RTCP)
    • Port Control Protocol (PCP)
  • Unavailable features
    • USB interfaces

Changelog 2.5.2

Enhancements

  • Improved Destructor speed.
  • Disabled some excessive logging
  • Exceptions during Refresh are now propagated to the user.

Bug Fixes

  • Fixed issue with client-server communication in Schedule Groups.
  • Fixed issue in argument validation in HTTPClient::Local.Port.Set and HTTPClient::Remote.Port.Set.
  • HTTPClient::WaitUntilFinished: If we enter the error state after successful connection establishment then we assume a TCP RST (reset) was received.

Changelog 2.5.0

Enhancements

  • Added support for ToS/DSCP (IPv4) and TrafficClass (IPv6) on the protocol stack:
    • HTTP Client (IPv4 and IPv6)
    • ICMP (IPv4)
    • ICMPv6 (IPv6)
  • Re-enabled PPPoE Client support including IPCP/IPv6CP and PAP/CHAP
  • excentis_basic:
    • Add support for generating VLAN tag and PPPoE header
  • HL API:
    • Added method to auto-complete the Layer 2 and Layer 2.5 headers in a frame to match the transmitting ByteBlowerPort: ::excentis::ByteBlower::LinkLayer.AutoComplete
    • Added helper functions for PPPoE client setup.
  • examples:
    • Added example scripts for PPPoE client API

Bug Fixes

  • Fixed issue where ByteBlower client sessions were not cleaned up properly: Enabled TCP keep-alive on management connection.

Download

The ByteBlower API 2.5 is not available anymore through the support portal. Of course you can still contact us at support@excentis.com.

Documentation

The HTML reference documentation for this API version

(0 vote(s))
Helpful
Not helpful

Comments (0)

We to help you!