BalanceNG is really a modern, IPv6 capable software IP load balancing solution. It’s little, quick, and easy to use and set up. It offers session persistence, various 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 extremely quick in-memory IP-to-location database, allowing powerful location-based server load-balancing.
But what is IPv6?
In 1991, the IETF decided that the current edition of IP, known as IPv4, had outlived its design. The new edition of IP, called either IPng (Next Generation) or IPv6 (version 6), was the result of a long and tumultuous process which came to a head in 1994, when the IETF gave a clear direction for IPv6.
IPv6 is created to solve the issues of IPv4. It does so by creating a new version of the protocol which serves the function of IPv4, but with out the same limitations of IPv4. IPv6 is not totally different from IPv4: what you’ve learned in IPv4 will be valuable when you deploy IPv6. The differences between IPv6 and IPv4 are in five major areas: addressing and routing, security, network address translation, administrative workload, and support for mobile devices. IPv6 also includes an important feature: a set of possible migration and transition plans from IPv4.
Since 1994, over 30 IPv6 RFCs have been published. Changing IP means changing dozens of Internet protocols and conventions, ranging from how IP addresses are stored in DNS (domain name system) and applications, to how datagrams are sent and routed over Ethernet, PPP, Token Ring, FDDI, and every other medium, to how programmers call network functions.