BalanceNG is a modern, IPv6 capable software IP load balancing solution. It is small, fast, and easy to use and set up. It offers session persistence, different distribution methods (Round Robin, Random, Weighted Random, Least Session, Least Bandwidth, Hash, Agent, and Randomized Agent) and a customizable UDP health check agent in source code. It supports VRRP to set up high availability configurations on multiple nodes. It supports SNMP, integrating the BALANCENG-MIB with Net-SNMPD. It implements a very fast in-memory IP-to-location database, allowing powerful location-based server load-balancing.
|Tags||Internet Proxy Servers Clustering/Distributed Networks Web Networking Load-Balancing Software Distribution Load-Balancer TCP/IP|
|Licenses||Proprietary with Free Trial|
|Operating Systems||Linux Solaris|
Release Notes: Specific LOG_INFO syslog messages have been introduced on bng start, stop, and reload. The host operating system architecture is logged on startup. Special Solaris DLPI timing issues have been resolved. The Solaris bnx0 interface is now recognized as "primary interface". A "bng reload" is now refused after a vrrp priority change.
Release Notes: An issue with "ICMP Fragmentation Needed" packet forwarding has been fixed. "bng stop" now uses SIGTERM, SIGHUP, and SIGKILL in that order. A new command "inject" allows packet injections from a PCAP file for debugging and QA purposes.
Release Notes: Outdated session table entries are now reclaimed very quickly on an idle BalanceNG system. The rate per second is controlled by the new parameter "sessiongclimit".
Release Notes: "ICMP Fragmentation Needed" packets are now forwarded to all associated targets of a virtual server (DSR mode only).
Release Notes: The command "rmt" now accepts a comma-separated list of targets. The server plugin implementation and protocol now support IPv6. A new parameter "vrrpstateplugin" has been introduced (if set to 1 (active), a VRRP state change is reported to all active server plugins). The default module chain is now "vrrp,arp,ping,hc,master,slb,tnat,nat,rt". To obtain BalanceNG V2 backwards-compatibility, the module chain "vrrp,classic" needs to be set explicitly. Running BNG V3 on TKLB legacy hardware now requires an additional action and a valid support contract (BNGSUP or BNGHPS).