> ## Documentation Index
> Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL.
> Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other.
> Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking.
> Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify.

# Create a Network

> Configure a network object in Edge Infrastructure Services to assign IP addressing, DNS, NTP, and proxy settings to a node port.

## Introduction

This procedure explains how to create a network object in Edge Infrastructure Services. A network object defines the IP addressing, DNS, NTP, and optional proxy settings that EVE-OS applies to a physical port on a node. You must assign a network to each port you want to use for management or application traffic.

The creation wizard adapts to the network type you select: an Ethernet network has only Identity and IP Configuration sections; a Wireless network adds a Wi-Fi section; a Cellular network adds an Access Point section and an optional Advanced section.

## Prerequisites

* You have the SysManager or SysAdmin role in your enterprise. See [Manage Roles](https://zededa.mintlify.site/new-ui/infrastructure-services/administration/manage-roles.md).
* A node onboarded to Edge Infrastructure Services. You can also create networks before onboarding and assign them during the onboarding flow.
* Only networks assigned to the same project as the node are available during onboarding or port assignment.

## Select a Network Type

1. In the sidebar, click **Infrastructure > Fleet > Networks**.
2. Click the **Add** button (floating button in the lower right of the page).
3. On the **Create New Network** screen, select the type that matches the physical interface you are configuring:
   * **Ethernet**: Wired network connection. Supports DHCP, Static IP, and more.
   * **Wireless**: Wi-Fi network configuration for wireless connectivity.
   * **Cellular**: Mobile data network (3G through 5G) for remote or mobile edge deployments.
4. The wizard opens for the selected type. Complete the sections described in the following steps.

## Configure Identity

The Identity section is required for all network types.

1. In the **Name** field, enter a unique name for the network. The name is unique across the enterprise and cannot be changed after creation. Spaces are automatically replaced with hyphens.
2. In the **Title** field, enter a display label. The title auto-fills from the name but can be changed independently. It is not used by EVE-OS.
3. In the **Description** field, enter an optional description to help other administrators understand the purpose of this network.
4. From the **Project** dropdown, select the project to associate this network with. You can also create a new project inline using the quick-create option, see [Create a Project](https://zededa.mintlify.site/new-ui/infrastructure-services/projects/create-a-project.md) for the full setup steps. Nodes can only use networks from their own project.
5. Toggle **Enterprise Default** if you want this network applied by default to new node ports in the enterprise.
6. Click **Next** to proceed.

## Configure Wi-Fi (Wireless Networks Only)

Complete this section when creating a Wireless network.

1. In the **SSID** field, enter the name of the wireless network. This field is required.
2. From the **Key Management** dropdown, select the authentication scheme:
   * **WPA-PSK**: Pre-shared key authentication.
   * **WPA2-Enterprise**: IEEE 802.1x authentication with per-user credentials.
3. In the **Priority** field, enter a priority value (0–7). When two Wi-Fi networks with the same link cost are both available, EVE-OS uses the one with the higher priority value.
4. In the **Username** field, enter the Wi-Fi username if required.
5. In the **Password** field, enter the Wi-Fi password. This field is required.
6. Click **Next** to proceed.

## Configure Access Point (Cellular Networks Only)

Complete this section when creating a Cellular network.

1. In the **APN** field, enter the Access Point Name for the cellular carrier. This field is required.

2. From the **Authentication Protocol** dropdown, select the authentication method if your APN requires credentials:

   * **Password Authentication Protocol**
   * **Challenge-Handshake Authentication Protocol**
   * **Both PAP and CHAP**

   If you select an authentication protocol, the **User Name** and **Password** fields appear. Enter the credentials for your APN.

3. From the **Radio Access Technology** dropdown, select the preferred radio technology:
   * **5G (Only)**
   * **5G (Preferred), 4G, 3G**
   * **4G (Only)**
   * **4G (Preferred), 3G**
   * **3G (Only)**

4. From the **IP Type** dropdown, select the IP addressing type for the data connection: **IPv4**, **IPv4 And IPv6**, or **IPv6**.

5. In the **Preferred Network** field, enter a PLMN code if the modem should prefer a specific carrier. Leave blank to let the modem select automatically.

6. Toggle **Enable Roaming** if the node may operate outside the home carrier's coverage area.

7. Click **Next** to proceed.

## Configure IP Configuration

The IP Configuration section applies to all network types.

1. From the **IP Address Config** dropdown, select the addressing mode:
   * **Static IP**: Assign a fixed IP address, subnet, gateway, and DNS.
   * **Static IP - Adapter Specific**: Create a general-purpose template without a fixed IP address. You complete the IP details per port during node onboarding. See [Configure Per-Adapter IP Addresses](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/onboard-nodes.md#configure-per-adapter-ip-addresses).
   * **DHCP Client**: EVE-OS requests an IP address automatically from a DHCP server on the network.
   * **None**: EVE-OS does not assign an IP address to this port. Use this mode with a switch virtual network instance when applications should obtain addresses from an external DHCP server.

2. If the IP Address Config is not **Static IP - Adapter Specific**, the following fields appear:
   * **Kind**: Select the IP addressing stack:
     * **Dual-stack, IPv4 preferred**
     * **Dual-stack, IPv6 preferred**
     * **IPv4 Only**
     * **IPv6 Only**
   * **MTU**: Enter the Maximum Transmission Unit in bytes (default: 1500). The minimum accepted value is 1280.

3. If you selected **Static IP**, enter the following:
   * **Subnet**: The network subnet in CIDR notation (for example, `192.168.1.0/24`).
   * **Gateway**: The default gateway IP address.
   * **Domain**: An optional DNS domain name for local name resolution.
   * **DNS**: One or more DNS server addresses, comma-separated.
   * **NTP Server**: One or more NTP server addresses (IP or FQDN, comma-separated). See the [NTP Overview](https://zededa.mintlify.site/new-ui/infrastructure-services/networks/ntp.md) for more information.

4. If you selected **DHCP Client**, you can optionally enter an **NTP Server** value to supplement or override NTP servers received from DHCP.

5. Under **Optional**, toggle **Proxy** to configure a proxy server for this network. When enabled, select the proxy type and complete the required fields:

   * **Auto Proxy Discovery**: EVE-OS uses DHCP or DNS with WPAD/PAC protocols to discover proxy settings automatically.
   * **Manual**: Enter the proxy server host and port for each protocol.
   * **PAC File**: Supply a Proxy Auto-Config script directly.
   * **Transparent**: Upload one or more CA certificates if the proxy performs TLS inspection.
   * **URL**: Specify the URL of a WPAD server that hosts the PAC file.

   Proxy settings are not available when the IP Address Config is set to **Static IP - Adapter Specific**.

6. Click **Next** to proceed, or **Create Network** if this is the last section.

## Configure Advanced Cellular Settings (Cellular Networks Only, Optional)

The Advanced section for Cellular networks is optional and collapsed by default. Click the **Advanced Cellular** heading to expand it.

**Attach bearer settings:**

1. In the **Attach APN** field, enter a separate APN for the initial bearer connection if your private LTE network or carrier profile requires one. Leave blank in most cases.
2. From the **Attach IP Type** dropdown, select the IP type for the initial bearer: **IPv4**, **IPv4 And IPv6**, or **IPv6**.
3. From the **Attach Auth Protocol** dropdown, select an authentication protocol for the attach bearer if required. If selected, enter the **Attach User Name** and **Attach Password**.

**Connectivity probing:**

4. Toggle **Connectivity Probing** to enable periodic reachability checks on this cellular interface.
5. From the **Probing Method** dropdown, select **ICMP Ping** or **TCP Handshake**.
6. In the **Custom Address** field, enter the IP address to probe.
7. If you selected TCP Handshake, enter the **TCP Port** (1–65535).

**GPS:**

8. Toggle **Send GPS Data** to have the modem report GPS location data.

## Verify the Configuration

After the network is created, a success toast appears and you are returned to the Networks list at **Infrastructure > Fleet > Networks**. Confirm the new network appears in the list with the correct project assignment and IP configuration type.

When you assign the network to a node port, the node's status page shows the management port IP address and controller connectivity state.

## Next Steps

> [card] [Manage a Network](https://zededa.mintlify.site/new-ui/infrastructure-services/networks/manage-a-network.md)
>
> Update or delete network objects after creation.

> [card] [NTP Overview](https://zededa.mintlify.site/new-ui/infrastructure-services/networks/ntp.md)
>
> Understand how EVE-OS uses the NTP server values configured here.

> [card] [Create a Virtual Network](https://zededa.mintlify.site/new-ui/infrastructure-services/virtual-networks.md)
>
> Configure application-facing network connectivity on the node.