SBO Version 4 is now available (launched 18th April 2015) . The release of version 4 further cements SBO as a premium featured VPN technology for the ISP and Telco environment.
|1.||Performance ImprovementsNow use around 10% less CPU load at high RTP levels vs V3. Can run efficiently on NUMA architectures (normally multiple processor systems where each processor is connected to its own cache and/or bank of RAM.)|
|2.||Virtual interfaces can now listen on different SBO ports.|
|3.||‘Endpoint Mode’. This new mode of operation allows:Complex NAT configurations.
SBO protocol running over ICMP or TCP as well as UDP.
More complex port and IP hopping, whereby the SBO tunnel switches between different destination IP addresses and/or protocol ports.
Blocked route detection. SBO can now detect if the route to a given IP address or port within a group is down, and cease to use that IP/port until it is restored. For example, if the SBO CPE is talking to a server by hopping between addresses 184.108.40.206, 220.127.116.11 and 18.104.22.168, and the route to 22.214.171.124 is blocked, it will continue by using onlythe working two until such time as the blocked route is restored.
HTML encoding. SBO protocol packets can be encoded using base64 in order to allowthem to appear to be standard HTML data.
Multilink and IP hopping are now compatible.
|4.||Metrics on SBO tunnel routes.This allows alternative routes to networks via other tunnels that are normally up. Tunnels which have overlapping more/less specific routes are now also handled correctly.|
|5.||RADIUS authentication and accounting support.|
|6.||Improved support for passive backup links connecting to servers using MAC address and dynamic IPs.|
|7.||The ability to generate additional link traffic in order to hide the real traffic profile. This can be either random or can utilise the whole link.|
|8.||In multilink setups, RTP can now be prevented from using one or more of the links, providing that at least one link that is allowed to carry it is up.|
|9.||The ability to disable SIP blocked log messages.|
|10.||Configuration option to set virtual interface MTU to other than 1500. This allows jumbo frames to be sent through SBO tunnels even if the underlying network does not support them.|
|11.||Support for configuration profiles containing common tunnel parameters.|
|12.||RAIN+ (see additional information in the Knowledge section).|
|13.||Branch Network (see additional information in the Knowledge section).|
|14.||MPLS CONNECT (see additional information in the Knowledge section).|
|15.||Management Interface Improvements.|