ByteBlower Server 2.0 changelog
Posted by Admin Kayako, Last modified by Admin Kayako on 08 July 2015 09:30 PM

ByteBlower Server 2.0 changelog


  • Fixed deadlock on 4100 series while getting realtime statistics.
    This is especially triggered when using non-zero initial time to wait on TX streams.
    I.e. in the GUI: Scenario with start time > 0


  • Fixed server crash on 2100 and 4100 series when a packet was received with Ethernet alignment or CRC error


  • Fixed filter issue on ByteBlower 2100 and 4100.
  • DHCPv4 message parsing fix.


  • IPv4 protocol crashed when to many sessions where opened.
  • Add update logs to the support archive.


  • Stability improvements for 1x00 and 2100 series.


  • 4100 series: Fixed major TCP performance issue for flows with a trunking interface as source.
  • 4100 series: Major stability improvements.
  • 4100 series: Server no longer requires link on both its dedicated data interfaces to function.
  • ARP protocol now marks messages with a 'zero' source MAC or source IP address as invalid. Fixes a server crash in such situations. ARP Probes are still supported.
  • TCP protocol calculates its Maximum Segment Size (MSS) as the minimum of the local configuration and the announced remote MSS, instead of simply taking the first.


  • TCP Window Scale value is now correctly applied per TCP session, instead of accross all configured sessions.
  • Increased TCP performance.
  • Improved stability on the 4100 series.
  • DHCP client implementation now always includes option 54 (Server Identifier option) in the request, since this is expected by some DHCP servers.
  • Known issue (4100): TCP performance on trunked (i.e. switched) 10 Gigabit interfaces is very low. This will be fixed in release 2.0.8.


  • Vlan tagged frames with a priority code are now accepted on the trunking interface ( ByteBlower 4100 ).
  • Unexpected frames are now logged and don't cause an assertion error.
  • Improved memory management in the ByteBlower stack.
  • Fixed wrong UDP checksum during DHCP renew.


  • DHCP client now always asks for default gateway and netmask values explicitly, through DHCP option 55 (Parameter Request List). Because of this, it now works with DHCP servers that don't provide these values by default.
  • Creating ByteBlower ports on 2100 or 4100 servers with more than one trunking interface should no longer give an unexpected error.


  • Complete new server installer and update mechanism.
  • New TCP/IP stack implementation.
  • Realtime results and results over time for packet counters, latency and out-of-sequence counters.
(0 vote(s))
Not helpful

Comments (0)

We to help you!