---
title: "How to choose the correct xNIC type"
slug: "how-to-determine-the-correct-xnic-type"
updated: 2025-12-15T17:51:17Z
published: 2025-12-15T17:51:17Z
canonical: "docs.swxtch.io/how-to-determine-the-correct-xnic-type"
---

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

# How to choose the correct xNIC type

> [!NOTE]
> **WHAT TO EXPECT**
> 
> **In this article**, users will learn how to determine the best xNIC type to be installed.

### xNIC Types

xNIC comes in different types, but if not specified differently, the default will be **xNIC Type 2**. This xNIC type is faster and should always be used unless kernel bypass interferes with the function of the application, or the user needs a feature not available for type 2.

When choosing the type, consider:

- When [High Availability](/v2/docs/high-availability-wxcked-eye) is needed and the xNIC is doing the duplication or deduplication then, users must use Type 1 or 3
- If SLP is needed and the agent is a Linux VM, users should use Type 3

Type 1 or Type 3 are ”overlay” modes that use a tunnel interface. It can be>

- TAP (by default) is Layer 3 (IP packet). Currently can be used on Linux only.
- TUN (can be configured) is Layer 2 (Ethernet frame). Can be used on Linux or Windows.

Users will need to produce and consume through a virtual interface called `swx0` (that’s the default name, but it can be changed).

For example, if a program requires packet capture, we would recommend using the TAP interfaces since they would expose packets earlier in the network. Another example would be a video multi-viewer, as these applications typically require more information than just the video packets themselves.

When installing Type 1 or 3, the `-t 1` or `-t 3` argument should be used during installation. For a complete list of available arguments, see [Installing xNIC](/v2/docs/xnic-installation) on Linux or Windows.