Yes, you can use many possible combinations of links. Some basic examples include: a T1 link from one Internet service provider (ISP) and an xDSL link from another ISP, or two cable links from the same ISP and one xDSL link from a different ISP.

The Elfiq Link Balancer offers standard Ethernet interfaces as interconnection points. Therefore, dedicated links, xDSL, cable, Frame Relay, fixed wireless, 3G/4G/LTE mobile, ISDN and more are all supported as long as a router encapsulates or converts the link traffic to Ethernet before it passes through the Link Balancer.

The Link Balancer can manage links of equal, different or asymmetric (different download and upload speeds) speeds just as well. Links of different speeds are managed transparently through the Link Balancer, which also guarantees that the most effective link is used for each given situation.

There are several models in the LBX and VLBX product lines. To know the level of performance for each, please visit our products section to see our product matrix.

Yes, the Link Balancer monitors each of the WAN/Internet links in order to detect logical or physical problems. In the case of a failure on one of the links, the traffic will transparently be redistributed to the other links.

In the case of a service rupture on one of the links, a syslog event will be sent to the syslog server preconfigured in the Link Balancer’s configuration. Optionally, an SNMP alert can also be sent. When a service rupture occurs, traffic is redirected to the other links. Most TCP applications will automatically retransmit the few packets that were lost during the transition. This will therefore make the loss of a link practically transparent to users and applications.

There are several models in the LBX and VLBX product lines. To know the level of performance for each, please visit our products section to see our product matrix.

No, it is not always required to use network address translation. In fact, you can prevent the manipulation of certain protocols, such as IPSEC HA. You can also associate multiple IP addresses (aliases) with each server located in the demilitarized zone (DMZ). The remaining problem depends on the complexity of the firewall configuration.

All you need to do is deactivate the corresponding GMAC. This way, your configuration is not modified and the Link Balancer will continue to balance all the traffic on all the other links, except the one that has just been deactivated.

No, the Elfiq Link Balancer manages transmitted packets and estimates link utilization per ISP by itself since access to the service providers’ routers in order to read statistics is usually blocked for security reasons.

No. A key factor in the Elfiq Link Balancer design is that it is easy to integrate, so no ASN is required to use the Elfiq Link Balancer.

The Link Balancer checks the status of each WAN link every 3 seconds (default value). If a link does not answer, the ISP is automatically deactivated and the network traffic is dynamically redistributed to the other links.

We have done our research on the Heartbleed vulnerability as well as performed relevant tests, and your Link Balancer (any firmware version) is not vulnerable or even affected.

Following the issues discovered in the OpenSSL library, we have identified that our units could be affected by vulnerability CVE-2014-0224. We have since brought the necessary corrections to our firmware.
These revisions are available on our website in Elfiq Central.

We have reviewed CVE-2014-6271 and CVE-2014-7169 and have determined that the Elfiq Operating System (EOS) was affected. These two CVEs affect the standard bash login shell, which is used in the EOS to support the Command Line Interface.

The problem can be corrected by updating your Elfiq Link LB to EOS version:
3.5.3.13141 for models LB550B, LB550E, LB1100E, LB1500E, LB1600E, LB3000E, LB4000E.
3.6.1.13141 for all other supported models.

We have reviewed CVE-2014-3566 and have determined that Elfiq Operating System (EOS) build 3.6.1.13141 was affected. The problem can be corrected by updating your firmware to the next release (build number and date to be provided as soon as possible).

We have done our research on the GHOST vulnerability as well as performed relevant tests, and your Link Balancer (any firmware version) is not vulnerable or even affected.