Mushroom Networks

Support answer

What is standalone mode and what is peered mode for Truffle units?

Search or browse documentation

Truffle devices have 2 operational modes:

1) Standalone mode: Truffle uses session-based load balancing to distribute separate sessions across available WAN links. Each session uses one link, so a single-session file download does not combine their bandwidth. For example, four 6 Mbps links can carry separate sessions across those links, but a single-session download remains limited by the link carrying it. Interface-binding policies can keep related sessions on the same WAN line when an application requires a consistent public IP address. Packet-level bonding requires peered mode.

Load-balancing can be done two ways using the interface group options: Round-Robin (random), Hash & Weighted hash. With the “Random” option traffic is distributed across all the desired interfaces. This can also be called as “Round Robin Distribution”. Whereas with Hash option, a hash is calculated depending on the source & destination IP address and the traffic is load-balanced according to the generated hash. Hash also uses weights in generating a weighted hash, which is used to load-balance the traffic according to the desired weights on different interfaces. 

2) Peered mode: When Truffle is peered with another Truffle device with a VLL server license over the Internet (let’s say a branch office and a headquarter office), the two units create a virtual leased line connection between them over the bonded pipe. In this mode downlink and uplink is bonded for all types of Internet traffic.

Peered mode can also be achieved by our monthly subscription service: Broadband Bonding Service (BBS). BBS is optional and lets the customer Truffle device peer with one of our data centers to enable bonding for all protocols. As mentioned, BBS is an optional add-on service.

 

Truffle operating modes

This article describes Truffle standalone and peered operation. Standalone uses session-based load balancing; packet-level bonding requires the selected cloud or customer-hosted endpoint. Confirm the active firmware, routes and service profile for your installation.

Current peering and service options