> 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/operations-and-features/overview-and-navigation/network-topology.md).
# Network topology
The **Network topology** section of the StifleR dashboard is used to define the structure of your network, apply specific configuration settings to clients within the networks, as well define peering groups.
An important concept to understand when working with network topologies in StifleR is the relationship between three components:
* **Locations –** contains one or more network groups which are often separated by a WAN link. For example, this might represent a physical office location.
* **Network groups –** a group of networks (subnets) which should peer with one another. For example, this might be a building within a campus of offices in the same physical location.
* **Networks –** an individual subnet.
The below diagram illustrates the logical structure of a StifleR network topology.
Another concept which applies to the network topology is [Templates](/stifler/operations-and-features/overview-and-navigation/devices/stifler-server/templates-detail.md). Templates are used to apply settings to network groups.
## [Locations](/stifler/operations-and-features/overview-and-navigation/network-topology/locations.md)
## [Network Groups](/stifler/operations-and-features/overview-and-navigation/network-topology/network-groups.md)
## [Networks](/stifler/operations-and-features/overview-and-navigation/network-topology/networks.md)
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://documentation.2pintsoftware.com/stifler/operations-and-features/overview-and-navigation/network-topology.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.