Skip to content

VLANs

t1n1wall supports 802.1Q VLAN tagging, allowing a single physical NIC to carry traffic for multiple logically separated networks. A VLAN interface is created first, then assigned as an optional interface.

Web UI location

Interfaces > VLANs

NIC compatibility

Not all NIC drivers support 802.1Q tagging natively. Cards without native driver support will still function but with a reduced MTU (the maximum transmission unit is lowered to accommodate the VLAN tag). This can cause fragmentation for traffic near the MTU boundary and may impact performance.

Check the FreeBSD driver documentation for your NIC to confirm 802.1Q support before deploying VLAN-dependent configurations in production.

Creating a VLAN

Field Notes
Interface Physical interface that carries the VLAN trunk (e.g., em0, igb1)
VLAN tag Numeric ID, 1–4094; must match the tag configured on the connected switch port
Description Human-readable name

Multiple VLANs can be created on the same physical interface, each with a different tag.

Assigning a VLAN as an interface

A VLAN is not functional until it is assigned as an interface:

  1. Go to Interfaces > Assign
  2. Select the VLAN entry from the available interfaces list and assign it to an optional interface slot (OPT1, OPT2, etc.)
  3. Configure the optional interface at Interfaces > OPT1 (IP address, enable, description)

See Configure Optional Interfaces for the full configuration flow.

Deletion

A VLAN cannot be deleted while it is assigned as an interface (LAN, WAN, or optional). Unassign the interface first before deleting the VLAN.

Switch configuration

The connected switch port must be configured as a trunk port carrying the corresponding VLAN tag. The physical interface on t1n1wall should connect to that trunk port. Access-mode switch ports with a single VLAN do not require VLAN configuration on the t1n1wall side.