---
title: "Preparing for TCP/UDP device connection onboarding"
slug: "recommendations-for-onboarding-tcpudp-connections"
description: "Recommendations for TCP/UDP device connection onboarding in the Remote Access Portal"
updated: 2024-12-06T15:42:00Z
published: 2024-12-06T15:42:00Z
canonical: "docs.neeve.ai/recommendations-for-onboarding-tcpudp-connections"
---

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

# Preparing for TCP/UDP device connection onboarding

Review the following information when preparing to onboard TCP/UDP device connections.

## Prerequisites

In the Secure Edge Portal, confirm the following:

1. The default destination for the node’s (formerly *iNode*) LAN network is set to **WAN Network**.
2. At least one IP address is available from the reserved IP address range of the LAN network.
3. The LAN network is connected to Cloud Connector (formerly *Virtual iNode*).

## Workflow recommendations

- Create one TCP/UDP connection at a time.
- Always associate the newly created TCP/UDP connection to a group from the device's connection page (**Associate Connections for <device>**), one at a time. Do not associate TCP/UDP connections from the group page.
- Ensure each TCP/UDP connection is onboarded successfully before proceeding to create the next connection.

## Limitations

- We do not recommend creating multiple TCP/UDP connections simultaneously, as this may result in some connections being inaccessible.
- Avoid associating multiple TCP/UDP connections with a group at the same time, as this can lead to connection issues.
- **Do not delete** the connector service running on the node.
- For TCP/UDP connections in a cluster or high-availability site, access to the device may be lost if the Edge Node is switched over.