Configuring Interfaces
Why should I use different interface types?
A Link Aggregation (bond interface) optimizes multi-user performance, balances network traffic, and provides network failover protection. In a failover it prevents a network outage by dynamically reassigning traffic to another interface when a physical link, like a cable or NIC, fails.
A network bridge enables communication between two networks and provides a way for them to work as a single network. Bridges can serve IP addresses to multiple VMs on one interface, which allows your VMs to be on the same network as the host.
Interconnect Maximum Effective Data Rates
These tables list the maximum effective data rates, in a single data flow direction, for various data interconnect protocols. A best effort attempt has been made to exclude physical link encoding overheads where appropriate.
| PCI Express 5.0 | Maximum Effective Data Rate (One Direction) | |||
|---|---|---|---|---|
| (10242 Bytes) MiB/s | (10002 Bytes) MB/s | (10003 Bits) Gb/s | Notes | |
| x1 | 3,756 | 3,938 | 31.5 | |
| x2 | 7,512 | 7,877 | 63.0 | NVMe M.2 (M+B Key) |
| x4 | 15,024 | 15,754 | 126 | NVMe M.2 (M Key) U.2/U.3 (1x4 or 2x2) E1.S/E1.L (typical) E3 |
| x8 | 30,048 | 31,508 | 252.1 | E1.S/E1.L (max) E3 |
| x16 | 60,096 | 63,015 | 504.1 | E3 (max) |
| PCI Express 4.0 | Maximum Effective Data Rate (One Direction) | |||
|---|---|---|---|---|
| (10242 Bytes) MiB/s | (10002 Bytes) MB/s | (10003 Bits) Gb/s | Notes | |
| x1 | 1,878 | 1,969 | 15.8 | |
| x2 | 3,756 | 3,938 | 31.5 | NVMe M.2 (M+B Key) |
| x4 | 7,512 | 7,877 | 63.0 | NVMe M.2 (M Key) U.2/U.3 (1x4 or 2x2) E1.S/E1.L (typical) E3 |
| x8 | 15,024 | 15,754 | 126.0 | E1.S/E1.L (max) E3 |
| x16 | 30,048 | 31,508 | 252.1 | E3 (max) |
| PCI Express 3.0 | Maximum Effective Data Rate (One Direction) | |||
|---|---|---|---|---|
| (10242 Bytes) MiB/s | (10002 Bytes) MB/s | (10003 Bits) Gb/s | Notes | |
| x1 | 939 | 985 | 7.9 | |
| x2 | 1,878 | 1,969 | 15.8 | NVMe M.2 (M+B Key) |
| x4 | 3,756 | 3,938 | 31.5 | NVMe M.2 (M Key) U.2/U.3 (1x4 or 2x2) |
| x8 | 7,512 | 7,877 | 63.0 | |
| x16 | 15,024 | 15,754 | 126.0 | |
| SAS-4 (24 Gb/s) | Maximum Effective Data Rate (One Direction) | |||
|---|---|---|---|---|
| (10242 Bytes) MiB/s | (10002 Bytes) MB/s | (10003 Bits) Gb/s | ||
| x1 | 2,289 | 2,400 | 19.2 | |
| x4 | 9,155 | 9,600 | 76.8 | |
| x8 | 18,311 | 19,200 | 153.6 | |
| SAS-3 (12 Gb/s) | Maximum Effective Data Rate (One Direction) | |||
|---|---|---|---|---|
| (10242 Bytes) MiB/s | (10002 Bytes) MB/s | (10003 Bits) Gb/s | ||
| x1 | 1,144 | 1,200 | 9.6 | |
| x4 | 4,578 | 4,800 | 38.4 | |
| x8 | 9,152 | 9,600 | 76.8 | |
| SAS-2 & SATA 3.0 (6 Gb/s) | Maximum Effective Data Rate (One Direction) | |||
|---|---|---|---|---|
| (10242 Bytes) MiB/s | (10002 Bytes) MB/s | (10003 Bits) Gb/s | ||
| x1 | 572 | 600 | 4.8 | |
| x4 | 2,289 | 2,400 | 19.2 | |
| x8 | 4,576 | 4,800 | 38.4 | |
| Ethernet | Maximum Effective Data Rate (One Direction) | |||
|---|---|---|---|---|
| (10242 Bytes) MiB/s | (10002 Bytes) MB/s | (10003 Bits) Gb/s | ||
| 1 GbE | 119 | 125 | 1.0 | |
| 10 GbE | 1,192 | 1,250 | 10.0 | |
| 25 GbE | 2,980 | 3,125 | 25.0 | |
| 40 GbE | 4,768 | 5,000 | 40.0 | |
| 100 GbE | 11,920 | 12,500 | 100.0 | |
| 200 GbE | 23,842 | 25,000 | 200.0 | |
| 400 GbE | 47,684 | 50,000 | 400.0 | |
| Fibre Channel | Maximum Effective Data Rate (One Direction) | |||
|---|---|---|---|---|
| (10242 Bytes) MiB/s | (10002 Bytes) MB/s | (10003 Bits) Gb/s | ||
| 8 Gb | 773 | 810 | 6.5 | |
| 16 Gb | 1,545 | 1,620 | 13.0 | |
| 32 Gb | 3,091 | 3,241 | 25.9 | |
| 64 Gb | 6,543 | 6,861 | 54.9 | |
Interface Configuration
TrueNAS supports configuring different types of network interfaces such as a standard interface, network bridge, link aggregation (bond), and VLAN interfaces to use as part of the various backup, sharing, and virtualization features in TrueNAS. The tutorials in this section guide you through each of the various network interface configurations.
- Configuring Interfaces: Provides instructions to add, edit, and manage network interfaces in TrueNAS.
- Setting Up a Network Bridge: Provides instructions on setting up a network bridge interface.
- Setting Up a Link Aggregation: Provides instructions on setting up a link aggregation (bond) interface.
- Setting Up a Network VLAN : Provides instructions on setting up a network VLAN interface.
- Network Interface Screens: Provides information on the Network screen Interfaces widget and configuration screens.
Managing Network Configurations
Use the Network Configuration Settings widget shows existing general network settings like the default gateway and DNS servers, set services allowed to externally communicate, enter an HTTP proxy, or host name database.
You can lose your TrueNAS connection if you change the network interface that the web interface uses! You might need command line knowledge or physical access to the TrueNAS system to fix misconfigured network settings.
Setting Up a Network Bridge
In general, a bridge refers to various methods of combining (aggregating) multiple network connections into a single aggregate network.
TrueNAS uses bridge(4) as the kernel bridge driver. Bridge(8) is a command for configuring the bridge in Linux. While the examples focus on the deprecated brctl(8) from the bridge-utilities package, we use ip(8) and bridge(8) from iproute2 instead. Refer to the FAQ section that covers bridging topics more generally.
Network bridging does not inherently aggregate bandwidth like link aggregation. Bridging is often used for scenarios that require extending a network segment or combining different types of network traffic.
Configuring IPv6
TrueNAS provides the option to configure network interfaces using either IPv4 or IPv6 addresses. IPv4 networks cannot see or communicate with an IPv6 website or network unless a gateway or some other implementation is configured to allow it. See Understanding IPv6 for more information.
After configuring your network infrastructure for IPv6, assign the IP addresses for your TrueNAS system. Use the TrueNAS UI to configure your network settings. If setting TrueNAS up for the first time after a clean install, use the Console Setup menu to enter IPv6 addresses.
Configuring Static Routes
TrueNAS does not pre-define static routes by default, but TrueNAS administrators can manually add static routes if they want or need to enter routes to a router to send packets to a destination network.
Static routes are not aliases, they are fixed IP addresses assigned as alternative routes for network traffic sent to a specific destination (server, device) in the network.
You can use the Console Setup menu during installation or any time after the initial system configuration to add a static route through an SSH session or by connecting a monitor and keyboard to the system, but we recommend using the web UI to make changes to the network configuration.
Network Configuration
Network configuration covers global network settings, interface options, and platform-specific configurations.
- Managing Network Configurations: Provides instructions on configuring or managing global network configuration settings.
- Configuring IPv6: Provides instructions configuring a network interface and other network settings for IPv6, and configuring an SMB or NFS share for IPv6.
- Managing Network Settings (Enterprise HA): Provides instructions on how to make changes to network settings on TrueNAS Enterprise (HA) systems.
- Network Configuration Screens: The Network Configuration widget shows the general TrueNAS network settings not specific to any interface.
Setting Up a Link Aggregation
A link aggregation combines multiple network interfaces into a single logical bond interface (e.g., bond0, bond1) to provide additional bandwidth or redundancy. TrueNAS implements link aggregation using Linux kernel bonding.
Setting Up IPMI
IPMI requires a compatible motherboard with IPMI support. Refer to your hardware documentation to determine compatibility.Many TrueNAS systems include a built-in out-of-band management port, enabling system access even when the web interface is unavailable.
Intelligent Platform Management Interface (IPMI) allows users to check the log, access the BIOS setup, and boot the system without physical access. IPMI also enables users to remotely access the system to assist with configuration or troubleshooting issues.

