Interfaces

Configure and manage the node’s local network configuration
Tags:

  4 minute read  

Network Interfaces

Navigate to a node, then select Interfaces under the Network section.

Interfaces panel

The Interface dropdown at the top allows you to select which interface to manage.

Interface Dropdown

ETH0 - WAN Interface

This interface is always used to build the outbound TLS tunnels for control and data plane connectivity. If the node is deployed in a single interface configuration, this interface will also be used for local network connectivity.

ETH# - LAN Interface

Used in configurations with more than one interface for local network connectivity.

VLAN Subinterface

Virtual under a physical LAN interface that will apply a VLAN tag to traffic

Configuration

Field NameDescription
Hardware AddressMAC address of the interface.
Interface NameName assigned to the interface by the operating system. This varies between hardware models and is sometimes needed when using tools such as Sniff Interface or reviewing logs.
Interface VRFSelects to which VRF the interface is attached.
VLAN ID (Subinterfaces Only)Sets the VLAN ID/tag for the subinterface.
IP Assignment
  • DHCP - requires a DHCP server or relay in the same broadcast domain as the interface connection
  • Static - configured using the fields below
IPv4 Address CIDRIP address using classless inter-domain routing (CIDR) notation.
Gateway IP
  • ETH0 - The IP address of the default gateway for this device. All traffic not in the same network as an interface IP or with a specified route will use this gateway.
  • ETH1 - This is only used in a 2-interface setup to access local resources outside the interface’s configured network. Routes must be defined.
DNS Servers IP(ETH0 only) Used to resolve DNS names to connect to the Trustgrid control plane.
Cluster Virtual IPUsed in clusters, this IP address is moved between member nodes based on the active cluster member. It can be used to route traffic between the virtual and local networks. This IP address can only be changed within the cluster interfaces page.
MTUThis field allows you to change the Maximum Transmission Unit (MTU) of the interface. MTU impacts the maximum size of packets sent or received on the interface.
Auto-NegotiationSets if the interface will use auto-negotiation to determine the speed and duplex settings. Values can be AUTO (default) or MANUAL.
DuplexLocked unless Auto-Negotiation set to MANUAL. Sets the interface to either FULL (default) or HALF duplex
SpeedLocked unless Auto-Negotiation set to MANUAL. Sets the interface to 10, 100, 1000 Mbps.
Ignore Health CheckValue can be Disable (default) or Enable. If set to Enable, the interface’s link status will no longer be used by the node to determine its cluster member health state. Useful if a single node has a network connection it’s peer does not such as an alternate WAN path.

Interface Routes

If the node is part of a cluster, these must be configured at the cluster level

These routes are used to access networks that are not in the same network as a configured interface and that are not accessed using the default gateway IP configured for ETH0 - WAN Interface. It is rare to need to define these on the ETH0 interface.

  1. Select the interface from the Network Interface dropdown.

  2. Click the + Add Entry button.

  3. Enter the route information There are three fields:

    Field NameDescription
    Destination CIDRThis is the CIDR notation of the network or host that needs to be routed. For a single host, use /32 as the CIDR suffix.
    Next HopThe IP address to which traffic destined for the above defined network will be sent. No CIDR suffix is needed.
    DescriptionOptional field to provide additional information about the route.

  4. Click the green check to confirm the route.

  5. Repeat steps 2-4 with any additional routes.

  6. Click the Save button.

Additional IPs

IP address entries added to the list below will be bound to the current interface.

Advanced Network Settings

Field NameDescription
Dark ModeValue can be Disable (default) or Enable. When set to Enable the node will restrict ICMP responses so that it will not respond to ICMP (Ping) echo requests or respond to failed TCP/UDP connection attempts with reset or ICMP Destination Port Unreachable