> 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/configuration/network-creation-flags.md).

# Network Creation Flags

StifleR can automatically create a Network (location) the first time a client connects from a new subnet. The **Network Creation Flags** setting controls when this is allowed.

{% hint style="info" %}
This is a more granular alternative to the basic `AutoAddLocations` on/off switch. Where `AutoAddLocations` simply turns automatic network creation on or off, Network Creation Flags let you allow — or block — automatic creation based on specific connection criteria.
{% endhint %}

## How it works

In the configuration tool, each flag is a checkbox: enable it to turn that behavior on, leave it unchecked to turn it off. There's no manual value to calculate — just check the flags you want active.

Each flag either **allows** a network to be created when the client's connection matches it, or **filters** (blocks) matches based on specific conditions.

A network is created when the client's connection matches **at least one** of the checked "allow" flags, **and** is not stopped by a checked filter flag.

## Flags reference

<table data-search="false"><thead><tr><th>Flag</th><th>What it does</th></tr></thead><tbody><tr><td>iPXE (1)</td><td>Allow WinPE / iPXE clients (e.g. during OS deployment) to create networks.</td></tr><tr><td>ManagedNetwork (2)</td><td>Allow networks where Windows has detected a domain controller.</td></tr><tr><td>VPN (4)</td><td>Allow VPN clients to create networks; these are created as VPN networks.</td></tr><tr><td>DomainAuthenticatedNetwork (8)</td><td>Allow networks where the client has authenticated against the domain.</td></tr><tr><td>AuthenticatedNetwork (16)</td><td>Allow networks that Windows classifies as a Domain network.</td></tr><tr><td>AcceptedNetworkName (32)</td><td>Allow networks whose Windows network name matches the <strong>Accepted network names</strong> setting.</td></tr><tr><td>SuperNet (64)</td><td>Automatically link new subnets to a network group that has a matching SuperNet range.</td></tr><tr><td>WiFiAllowList (128)</td><td>Allow networks when the client is connected to an SSID in the <strong>List of allowed Wi-Fi SSIDs</strong> setting.</td></tr><tr><td>PowerShell (256)</td><td>Allow networks when your custom <code>AllowNewLocation.ps1</code> script returns true.</td></tr><tr><td>WiFiAllowListSeen (512)</td><td>Reserved for future use; currently has no effect.</td></tr><tr><td>DirectRoute (1024)</td><td>Allow networks when the client reaches the server without NAT (same internal and external IP).</td></tr><tr><td>AllowVirtualDuplicates (2048)</td><td>Accept virtual router MAC addresses (HSRP/VRRP) when matching clients to existing networks.</td></tr><tr><td>QueryClients (4096)</td><td>If the gateway MAC does not match, check other online clients on the subnet before treating it as a new network.</td></tr><tr><td>AllowInternetNetworks (8192)</td><td>Allow clients with a public IP address to create networks.</td></tr><tr><td>IgnoreNATChecks (16384)</td><td>Treat every client as directly routed. Use when a proxy or load balancer sits in front of the server.</td></tr><tr><td>OnlySecureWiFiAllowed (32768)</td><td>Block Wi-Fi networks that do not use 802.1X authentication.</td></tr><tr><td>DHCPAndDNSServerSameAsGateway (131072)</td><td>Block networks where the gateway is also the DHCP and DNS server — typical for home routers.</td></tr><tr><td>DHCPAndDNSServerSame (262144)</td><td>Block networks where the same server provides both DHCP and DNS.</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 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/configuration/network-creation-flags.md?ask=<question>&goal=<endgoal>
```

`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.