# Locations

A Location is defined by one or more IP ranges intended to identify machines that are connected over a LAN. Setting up Locations is the first step in designing your network topology.

For more information regarding network topology, please see our [Network Topology](https://docs.adaptiva.com/platform-guide/platform-management/network-topology) page. This page covers additional information regarding:

* [Location hierarchy](https://docs.adaptiva.com/platform-guide/platform-management/network-topology#locations)
* [Content flow](https://docs.adaptiva.com/platform-guide/platform-management/network-topology#content-flow)
* [Transport protocols](https://docs.adaptiva.com/platform-guide/platform-management/network-topology#onesite-protocols)

## Location types

Location types affects the behavior of how the Adaptiva Client communicates within a Location. There are three Location types: Default, VPN, and WiFi. Each location type is defined below.

{% hint style="info" %}
It is important to define Locations by their Location types accurately to the physical network. If not properly added to a correct location type, you may run into issues like:

* If a Default location is created for devices connected to a wireless network, those devices will attempt to communicate by broadcast. The wireless Access Point, may block these transmissions preventing peers from communicating effectively within the Location.
* A VPN client added to a Default Location will pull content in two WAN hops—first to the VPN gateway, then through the tunnel to the client—slowing delivery and increasing network load.

When a physical location includes both a wired and a wireless subnet, create a separate Location for each. Set the wireless location to WiFi and assign it as a child of the wired location. This setup ensures the wireless Location retrieves content from its parent.
{% endhint %}

### Default

* Defines a standard wired Local Area Network (LAN).
* ALL subnets at this physical location should be combined into a single Location.
* Example: Central or regional headquarters office with wired connections.

### VPN

* Defines a Location and IP range allocated to clients connecting with a VPN.
* Does not use peer-to-peer communication and only pulls content from the Parent Location.
* It is recommended that **ALL** VPN subnets from a given concentrator be combined in a single Location.
* Example: Subnet devices are assigned addresses from when connected to the company VPN.

### WiFi

* Defines a Location and IP range or ranges allocated to clients connected over Wi-Fi.
* Uses unicast instead of broadcast to communicate between devices on the same subnet.
* Example: Wireless network at an Office which end-user devices will connect to. It is recommended that wireless networks be defined as a child Location to a wired network in the same physical location.

## Creating a new Location

This task will guide you on how to create a new Default Location. For a full comprehensive list of Location settings and actions, please see our [Locations Settings and Actions](https://docs.adaptiva.com/platform-guide/platform-features/locations/locations-settings-actions) page.

1. Hover over **Assets** and select **Locations** from the Platform Features side navigation.

   ![Locations button under Assets tab](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-2f48b2a72624be577e454d677b643d9a30df3c77%2FAssests%20Side%20Bar%20Locations.png?alt=media)
2. Click **+New** in the upper right corner of the Locations pane.

   ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-c059b6f57d258cded5e3c23d4087bd16f924fae7%2FCreate%20new%20location.png?alt=media)
3. In the **General Settings** enter the following:

   * **Name** - "Seattle HQ"
   * **Description** - "Seattle Headquarters office"
   * **Location Type** - Default
   * **Metered Connection** - Toggle **OFF**.
   * **Allow Direct CDN Download** - Toggle **OFF**.

   ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-437bca393224719dd044936c1f9c8fc7a03a8d25%2Fdemo-general-settings-parent-location.png?alt=media)
4. In the **Address Range** settings enter an IP range that reflects your subnet of your location. For the purpose of this task we will enter the following:

   * Click **+Create IP Range**
   * **Starting** and **Ending IP** - `10.0.0.1` and `10.0.0.255`.
   * Click **+Create IP Range**

   ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-7771d2754d5519d78876f875201bdf478722c60d%2Ffinal-address-range.png?alt=media)
5. Click **Browse** from **Topology Settings** and select the **Central Office** from the table.

   ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-00f4c031a5c5db597884c96b54d3c3a15352789b%2Ftopology-settings-central-office.png?alt=media)
6. Click **OK**.

   ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-e6a0f49f929267eeab01722fd1d95fd668b4f762%2Ftopology-settings-final.png?alt=media)
7. Ignore the **Location Devices** section. This would only be applicable if you already had a location with associated devices.
8. Click **Save**.
9. Select **Tree** from the **Display As** dropdown.

   ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-645d4d865510b5dc3c8009928ffc8553415b1cd6%2Flocation-hierarchy.png?alt=media)

You'll notice the Network Typology of your Locations will be stacked from Parent to Child accordingly.
