Connected IPs¶

A connected IP configures networking between the bonder and the customer’s router. For example, if the bonder is connected to the customer’s router on interface eth0, a connected IP of 203.0.113.1/30 could be configured on eth0 allowing the bonder to communicate with the router at 203.0.113.2. The subnet 203.0.113.0/30 is then routed from the aggregator to the bonder.

Connected IPs require a matching route to be added from the aggregator to the bond’s tunnel device. This is handled automatically by Bonded Internet. It also requires a route from the partner’s core routers to the aggregator. This works automatically when the aggregator is integrated into the core network dynamic routing.

Connected IPs can use private networks as well. In this case, at least one CPE NAT IP is required for the customer’s firewall to be able to connect to the Internet, and no routes for the connected IP are added on the aggregator or partner core network.

Adding, editing, & deleting connected IPs¶

Connected IPs are displayed in a table on the bond details page.

To add a connected IP, click the node-object-add button to the upper-left of the connected IPs table. This will open the “add connected IP” modal.

To edit a connected IP, click the node-object-edit button on the connected IP action toolbar. This will open the “edit connected IP” modal.

To delete a connected IP, click the node-object-delete button on the connected IP action toolbar. This will ask for confirmation, and is permanent.

Configuring connected IPs¶

The configuration modal for a connected IP is accessed by editing an existing connected IP or adding a new one.

cip-config-modal

Interface¶

The interface on the bonder where the customer’s network is connected.

Multiple connected IPs may be created on the same network interface.

IP¶

The IP address to use on the interface specified in the interface field. Connected IPs can be either IPv4 or IPv6.

Connected IP IPv4 addresses can be either public or private. Public IPv4 connected IPs must be within a network allocated to the bond’s space. Private IPv4 connected IPs do not need an allocation.

Connected IP IPv6 addresses can be either globally routable or link-local addresses.

For bonds in spaces that don’t use private WAN (PWAN), multiple bonds can be assigned the same private IPv4 connected IP. For bonds in spaces that use PWAN, the connected IP must be unique within the space—no two bonds in the same PWAN space can use the same connected IP.

As of version 6.0, netmasks of /31 can be used for connected IPs. Valid IP subnets larger than /31 from prior versions are still valid and can continue to be used.

Warning

If a connected IP’s IP address is the same as a gateway IP on any leg on the same bond, then the routing behaviour becomes undefined and can lead to outages.

Enabled¶

When checked, loads the connected IP on the bonder and aggregator.

Use IPv6 link-local¶

If set, this IP will represent the automatically configured IPv6 link-local address, eliminating the need to define IPv6 interconnection ranges between a bonder and an internal router or firewall

Include in private WAN¶

When the PWAN option of the bond’s space is enabled, this option controls whether or not traffic from this connected IP is included in the PWAN routing. If enabled, traffic is sent to and received from the PWAN space. If disabled, traffic is not sent to the PWAN space, but is routed directly to the partner’s core network as if the bond’s space did not use PWAN.

This option has no effect when the bond is in a space with PWAN disabled.

Disabled by default.

Note

The default setting for this option has changed from enabled to disabled as of version 6.4.

Aggregator routing¶

This option allows the aggregator’s routing mode to be overridden. The options are

Automatic (default): If the connected IP is globally routable, a route for the network is created from the aggregator to the bonder. Otherwise, no route is created.
Always: A route for the network is created from the aggregator to the bonder, unconditionally.
Never: A route for the network is not created from the aggregator to the bonder, unconditionally.

DHCP & DNS caching¶

As of 6.4, connected IPs can no longer be configured to act as DHCP servers or perform DNS caching. Instead, DHCP & DNS caching services can be created and assigned to connected IPs.