How the StriveCast eCDN network management works

To optimize your corporate network, StriveCast needs to reduce bandwidth consumptions on critical points in your network. Typically, these critical points (so-called "bandwidth bottlenecks") occur in one of the following places:

  • Public internet breakouts from your corporate network to the internet

  • Internal breakouts from physical buildings to proxy servers, acting as public internet breakouts

The solution offered by StriveCast is to build software-defined P2P networks within each location, such that media content is shared within each P2P network instead of pulled through the bottlenecks:

To build these P2P networks most efficiently, the following questions need to be answered:

Question

How can physical locations be detected based on private IP information?

How can external VPN users be detected based on private IP information?

Are there subnets within any location, which should be excluded from peering?

Are there subnets that shall allow cross-subnet peering?

Should peering be configured on a whitelisting approach (enable all users to peer except some) or a blacklisting approach (enable no users to peer except some)?

Available Peering Policies

Typically, these questions can be answered using the corporate network's internal structure of subnets and IP ranges. StriveCast offers the following rules and configurations:

Peering Policy

Description

Use-Case

Public IP

Peer between all peers with the same public IP address.

Every office location has its own public internet breakout with one or more static IP addresses.

Note: For this peering policy, Advanced peering rules are not available.

Split by /24

Peer between all peers within the same /24 subnet.

Every office location is assigned one or more /24 subnets.

Note: If an office location is split into multiple /24 subnets, peering will only work within each individual subnet.

Split by /16

Peer between all peers within the same /16 subnet.

Every office location is assigned one or more /16 subnets.

Note: If an office location is split into multiple /16 subnets, peering will only work within each individual subnet.

Split by /8

Peer between all peers within the same /8 subnet.

Every office location is assigned one or more /8 subnets.

Note: If an office location is split into multiple /8 subnets, peering will only work within each subnet.

Custom

Peer purely based on custom IP-ranges and rules.

You can configure your peering policy in your Deployment configuration:

Advanced peering rules based on IP-ranges

On top of the configured peering policy, you can specify additional networks and locations by providing custom IP ranges. These ranges can then be configured to either allow or block peering. IP ranges can be provided in two ways:

  1. Provide specific start_ip and end_ip values for each range.

  2. Provide an IP CIDR block of the form a.b.c.d/size to specify a subnet of size /size .

Note: If you provide start_ip and end_ip, StriveCast will automatically try to find a matching CIDR block. Vice versa, if you provide a CIDR block, StriveCast will automatically calculate the corresponding start_ip and end_ip values.

Navigate to the account menu to configure advanced peering rules, click on your initials in the top right corner, and select "Networks & Locations.

Add your advanced peering rules either with the Visual Editor or the Text Editor.

Using the visual editor

  1. Create new locations via the interface to create a new, named location (typically done per site, see example).

  2. For each location, you can create Networks, which contain multiple (potentially non-connected) IP ranges. Each network can be configured to be either blocked or allowed:

    1. For an allowed network, peering will be possible between all devices from all IP ranges within the network.

    2. For a blocked network, peering will be deactivated for all devices from all IP ranges within the network.

  3. Each Locations & Networks table entry can be understood as a classification rule of the device's internal IP address. The set of rules will be applied from top to bottom. The first match will define the device's classification. You can move Networks up and down with the user interface to change the order of evaluation.

Using the text editor

Click on "Show Editor" on the Locations & Networks page to open the editor panel for text-based configuration:

The user interface provides two input fields for allowed and blocked network ranges:

  • The first input field (allowed IP ranges) expects each row to contain the data structure
    start_ip, end_ip, target_ip, network_name , where:

    • start_ip contains the IP range's start IP

    • end_ip contains the IP range's end IP

    • target_ip shall be any valid IP address, which is uniquely equal for all ranges where peering between devices should be allowed.

    • network_name is the name of the IP range

  • The second input field (blocked IP ranges) each row to contain the data structure
    start_ip, end_ip, network_name, where:

    • start_ip contains the IP range's start IP

    • end_ip contains the IP range's end IP

    • network_name is the name of the IP range

Setting up your peering policy and custom peering rules

Please do not hesitate to contact your StriveCast eCDN representative to get support during your peering policy configuration.