Learn NAS - Networking & Basic Access

#Introduction

A NAS is useless without a healthy network. Episode 8 covers networking and basic access: how to assign a static IP, combine links with bonding, separate traffic with VLANs, and leverage jumbo frames and 10GbE tuning for maximum throughput.

On the access side, you'll learn to mount SMB shares from Windows, macOS, and Linux, mount NFS from Unix-like clients, and trace through the most common connection problems. Mastering this material will become a troubleshooting tool you'll use for the rest of the series.

By the end of this episode you'll be able to configure NAS networking correctly and access data from all major operating systems without confusion.

#Static IP Configuration

#Why a Static IP

A storage server shouldn't depend on DHCP, which can change at any time. A static IP ensures clients, backup jobs, and DNS always find the NAS at the same address. In TrueNAS SCALE, the IP is set through the Console Setup Menu or Network in the Web UI; in OpenMediaVault, through the Network interface in Workbench.

nmcli con mod eth0 ipv4.addresses 192.168.1.100/24
nmcli con mod eth0 ipv4.gateway 192.168.1.1
nmcli con mod eth0 ipv4.method manual
nmcli con up eth0

The nmcli con mod eth0 commands modify the NetworkManager configuration. The same IP/netmask pattern is used when registering the hostname in DNS.

#Checking Connectivity

After setting the IP, verify from the client:

ip addr show
ping -c 3 192.168.1.100

The ping command confirms the NAS is reachable. If there's no reply, check the firewall and make sure the client's subnet matches the NAS's subnet.

#Bonding and LAG

#Why Bonding

Bonding/LAG (Link Aggregation) combines two or more NICs into one logical interface. It has two benefits: bandwidth aggregation for many simultaneous clients, and redundancy if one link or switch port dies.

nmcli con add type bond con-name bond0 ifname bond0 mode 802.3ad
nmcli con add type ethernet con-name eth0 ifname eth0 master bond0
nmcli con add type ethernet con-name eth1 ifname eth1 master bond0

The commands above create a bond in 802.3ad (LACP) mode from two interfaces. Other modes like active-backup are used when the switch doesn't support LACP.

#Important Notes on LACP

LACP requires a port channel configuration on the switch, and maximum throughput is only reached for many simultaneous connections, not a single one. For one large client, a direct 10GbE connection is often better than bonding four 1GbE ports.

#VLANs and Jumbo Frames

#Separating Traffic with VLANs

A VLAN logically separates networks over the same switch. A common homelab pattern: a storage VLAN for NAS traffic, a management VLAN for admin access, and a user VLAN for clients. This separation simplifies firewall rules and prevents backup traffic from flooding the work network.

nmcli con add type vlan con-name vlan10 ifname eth0.10 dev eth0 id 10

The nmcli con add type vlan command creates a VLAN 10 interface on top of eth0. Make sure the switch is configured with the same tagged VLAN.

#MTU and Jumbo Frames

Jumbo frames raise the MTU from 1500 to 9000 bytes, reducing overhead per packet. The benefit is real for large file transfers, but every device in the path — including switches — must support the same MTU.

nmcli con mod eth0 mtu 9000
ip link show eth0

The nmcli con mod eth0 mtu 9000 command sets the MTU to 9000. If transfers become slower or drop after that, revert to 1500 and check switch support.

#Basic Access: Mounting SMB

#Windows and macOS

On Windows, open File Explorer, type the NAS address, then enter your credentials:

\\192.168.1.100\data

On macOS, from Finder choose Go > Connect to Server and enter the URL:

smb://192.168.1.100/data

Both operating systems handle SMB natively, so the share appears like a local folder once credentials are verified.

#Linux with cifs-utils

On Linux, mounting SMB is done with the cifs-utils package and specific mount options. For a persistent mount, add an entry to /etc/fstab.

sudo mount -t cifs //192.168.1.100/data /mnt/data -o username=devnull

The mount -t cifs command attaches the SMB share to /mnt/data. Protocol version options like vers=3.1.1 can be added to match the server configuration in episode 9.

#Basic Access: Mounting NFS

#Manual NFS Mount

NFS is a popular share protocol for Unix-like clients and virtualization. On the server, shares are registered in /etc/exports; on the client, mounting is done with mount.

sudo mount -t nfs 192.168.1.100:/tank/data /mnt/data

The mount -t nfs command connects the NAS export directory to /mnt/data. Export configuration details will be covered in episode 10.

#Persistent Mounts with fstab

To make the mount survive a reboot, register it in /etc/fstab. Use the nofail option so boot isn't disrupted when the NAS isn't up yet.

192.168.1.100:/tank/data  /mnt/data  nfs  defaults,nofail  0 0

#Troubleshooting Connections

#Diagnostic Steps

When access fails, trace through layer by layer:

1. Check the physical layer and IP: ip addr show, then ping the NAS.
2. Check the protocol ports: SMB uses 445, NFS uses 2049.
3. Check credentials and user permissions.
4. Check the NAS and switch firewalls (especially with VLANs or large MTUs).

ss -tlnp | grep -E '445|2049'

The ss -tlnp command shows ports currently listening. If the port doesn't appear, the SMB or NFS service isn't running on the server.

#Closing

In this episode 8 you mastered the NAS networking foundation: static IP, bonding/LAG, VLANs, jumbo frames, 10GbE tuning, mounting SMB on Windows, macOS, and Linux, mounting NFS, and troubleshooting.

Key takeaways:

• A static IP is a must for a server; DNS and firewall follow.
• Bonding helps many clients; 10GbE for one large client.
• VLANs separate traffic; jumbo frames need end-to-end support.
• SMB is used on Windows and macOS; NFS for Unix-like and virtualization.
• Always troubleshoot from the physical layer up to the application.

In the next episode, episode 9, we'll dissect SMB/CIFS sharing in depth — from smb.conf configuration, server min and max protocol, browsing and printer shares, to oplocks tuning and Windows integration like permissions and DFS. Basic access is working; now it's time to hone the world's most popular file sharing protocol.