> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/stifler/features-breakdown/templates.md).

# Templates

A Template is a way to control all settings for a Network Group. A linked Network Group inherits all values from the template it's assigned.

A Template offers the following:

* Controls initial settings at network creation.
* The best template is matched using Beacons, selected as follows:
  * Fastest Beacon — any Template that matches the Beacon ID is considered.
  * StifleR then matches the best list of Templates using latency and bandwidth.

2Pint Software provides many out-of-the-box templates which represent settings for various scenarios. On the "Templates" page, select the edit button next to any template to view and adjust its settings.

<figure><img src="https://425521159-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1rrK0lTrlpunspNbITJB%2Fuploads%2FduYBjv7GkUgzfRP3gNHS%2Fimage.png?alt=media&amp;token=e57e3d66-bef8-4e26-b9b3-1f8397969ea7" alt=""><figcaption></figcaption></figure>

The table below lists all of the settings available within a template. The setting defaults will differ between templates depending on their purpose. Please review the information on the Bandwidth management and allocation page, which explains how different settings apply to different scenarios.

#### Network Group Template

| Setting                                    | Description / Options                                 |
| ------------------------------------------ | ----------------------------------------------------- |
| Id                                         | The GUID which is assigned to the template.           |
| Description                                | A description of the template.                        |
| Date Added                                 | The date and time in which the template was created.  |
| Networks on this group are directly routed | Options: Direct route / Not directly routed (via NAT) |

#### Bandwidth and throttling settings

<table data-search="false"><thead><tr><th>Setting</th><th>Description / Options</th></tr></thead><tbody><tr><td>Type of network</td><td>Options: Regular network (default), Well connected, VPN, DataCenter, BuildDepot</td></tr><tr><td>Internet breakout</td><td>Options: No separate throttling for Internet traffic (default) / Separate throttling for Internet traffic</td></tr><tr><td>Throttling of bandwidth</td><td>Mb/s (Mbps)</td></tr><tr><td>Max bandwidth (downstream)</td><td>b/s (Not set)</td></tr><tr><td>Target bandwidth by %</td><td>0-100%</td></tr><tr><td>Separate throttling of internet bandwidth</td><td>b/s</td></tr><tr><td>Well connected DO bandwidth</td><td>b/s</td></tr><tr><td>Well connected BITS bandwidth</td><td>b/s</td></tr><tr><td>Non-leader DO bandwidth for regular networks</td><td>Kb/s</td></tr><tr><td>Non-leader BITS bandwidth for regular networks</td><td>Kb/s</td></tr></tbody></table>

#### Automatic throttling and LEDBAT++ settings

| Setting                    | Description / Options                                                                                                                          |
| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Beacon                     | FQDN of Beacon server                                                                                                                          |
| Measure vs template values | Options: Beacon measure wins (default) / Template wins                                                                                         |
| Automatic bandwidth tuning | Options: 0 - Disabled, 1 - Latency, 8 - LEDBAT, 16 - Estimate Max Bandwidth. See Bandwidth tuning monitoring and control for more information. |
| LEDBAT target bandwidth    | 0 b/s                                                                                                                                          |

#### BranchCache and BITS

<table data-search="false"><thead><tr><th>Setting</th><th>Description / Options</th></tr></thead><tbody><tr><td>Disable BranchCache</td><td>Options: Do not disable (default) / Yes, disable</td></tr><tr><td>Set BranchCache to Local mode only</td><td>Options: Allow other modes (default) / Yes, local only</td></tr><tr><td>Server Secret</td><td>&#x3C;Enter the server secret></td></tr><tr><td>Set LEDBAT++ on BITS Uploads</td><td>Options: Do not use LEDBAT++ for uploads (default) / Use LEDBAT++ for uploads</td></tr><tr><td>Set BranchCache to local mode on Wi-Fi</td><td>Options: Disabled (default) / Enabled</td></tr><tr><td>Force distributed mode</td><td>Options: Disabled (default) / Enabled</td></tr><tr><td>Force Hosted Cache Mode</td><td>Options: Disabled (default) / Enabled</td></tr><tr><td>Set BranchCache to use ports 1337, 1338, 1339</td><td>Options: Yes, manage the ports automatically (default) / Manually manage ports</td></tr><tr><td>Manage cache sizes</td><td>Options: Enabled (default) / Managed manually</td></tr><tr><td>Cache options set (change via WMI)</td><td>10 GB for disks 128 GB and less, 10% for 250–500 GB, and 50 GB for 480 GB+</td></tr><tr><td>Disable Green Leader for clients on wired networks</td><td>Options: Wired clients can use Green Leaders (default) / Wired clients use distributed mode</td></tr><tr><td>Always use Green Leader(s) for clients on Wi-Fi</td><td>Options: Wi-Fi clients may use Green Leaders (default) / Wi-Fi clients always use Green Leaders</td></tr><tr><td>Automatically select Blue Leader(s) if needed</td><td>Options: No, manually define (default) / Yes, select for me if needed</td></tr></tbody></table>

#### Delivery Optimization

<table data-search="false"><thead><tr><th>Setting</th><th>Description / Options</th></tr></thead><tbody><tr><td>Delivery Optimization mode</td><td>Options: Group (default), Not Configured, HTTP Only, LAN, Internet, Simple, Bypass</td></tr><tr><td>Automatically set group ID (using Network Group ID)</td><td>Options: Enabled (default) / Managed manually</td></tr><tr><td>Disable P2P on Wi-Fi networks</td><td>Options: Managed manually (default) / Enabled</td></tr><tr><td>Enable DNS-SD for peer discovery</td><td>Options: Disabled (default) / Enabled</td></tr><tr><td>Disable Teredo responses to multicast</td><td>Options: Disabled (default) / Enabled</td></tr><tr><td>Randomize fallback times to randomize start times</td><td>Options: Enabled (default) / Managed manually</td></tr><tr><td>Force low RAM machines to use P2P</td><td>Options: Enabled (default) / Managed manually</td></tr><tr><td>Manage cache size</td><td>Options: Enabled (default) / Managed manually</td></tr><tr><td>Cache options set (change via WMI)</td><td>10 GB for disks 128 GB and less, 10% for 250–500 GB, and 50 GB for 480 GB+</td></tr><tr><td>Allow small files to peer</td><td>Options: Enabled (default) / Not set</td></tr><tr><td>Configure maximum cache age</td><td>Options: Enabled (default) / Not set</td></tr><tr><td>Configure minimum background QoS for more P2P</td><td>Options: Enabled (default) / Not set</td></tr><tr><td>Delay foreground download from HTTP for more P2P</td><td>Options: Enabled (default) / Not set</td></tr><tr><td>Delay background download from HTTP for more P2P</td><td>Options: Enabled (default) / Not set</td></tr><tr><td>Delay Cache Server fallback foreground for more P2P</td><td>Options: Enabled (default) / Not set</td></tr><tr><td>Delay Cache Server fallback background for more P2P</td><td>Options: Enabled (default) / Not set</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.2pintsoftware.com/stifler/features-breakdown/templates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.