Skip to content

NUC Networking

This page covers the NUC's network configuration, with emphasis on the Tata NNI link and routing requirements.

Interface Table

Interface Type IP Address Subnet Gateway Purpose
enp86s0 Ethernet (NNI) 10.54.225.90 /30 10.54.225.89 Tata SBC connectivity
wlo1 WiFi 192.168.0.13 /24 192.168.0.1 LAN / Internet (default route)
enx9c69d3197bc6 USB Ethernet 192.168.0.14 /24 192.168.0.1 Backup LAN connectivity
wg0 WireGuard 10.10.10.2 /24 -- Tunnel to cloud

The enp86s0 interface connects directly to the Tata NNI on VLAN 1922.

Parameter Value
VLAN 1922
NUC IP 10.54.225.90/30
Gateway 10.54.225.89
SBC IP 10.79.215.102
Media Pool 1 10.79.167.0/28
Media Pool 2 10.79.167.48/28

Persistent Configuration

The NNI interface is configured persistently at /etc/network/interfaces.d/enp86s0:

auto enp86s0
iface enp86s0 inet static
    address 10.54.225.90
    netmask 255.255.255.252
    up ip route add 10.79.215.102/32 via 10.54.225.89 dev enp86s0
    up ip route add 10.79.167.0/28 via 10.54.225.89 dev enp86s0
    up ip route add 10.79.167.48/28 via 10.54.225.89 dev enp86s0

This ensures the interface comes up with the correct IP and all required routes are added automatically.

Why Routes Matter

Critical: Without correct routes, calls will fail

The NUC has multiple interfaces and a default route through the WiFi/LAN gateway (192.168.0.1). Without explicit routes for Tata's networks, SIP responses and RTP packets destined for the SBC or media pools would be sent out through the wrong interface (WiFi instead of NNI), and Tata would never receive them.

The following routes must exist:

Destination Via Interface Purpose
10.79.215.102/32 10.54.225.89 enp86s0 SIP signaling to Tata SBC
10.79.167.0/28 10.54.225.89 enp86s0 RTP media pool 1
10.79.167.48/28 10.54.225.89 enp86s0 RTP media pool 2

Route Verification

Check that the required routes are present:

# Show all routes through the NNI interface
ip route show dev enp86s0

# Expected output should include:
# 10.54.225.88/30 proto kernel scope link src 10.54.225.90
# 10.79.167.0/28 via 10.54.225.89
# 10.79.167.48/28 via 10.54.225.89
# 10.79.215.102 via 10.54.225.89

Verify specific routes:

# Check route to SBC
ip route get 10.79.215.102

# Check route to media pool
ip route get 10.79.167.1
ip route get 10.79.167.49

Each should show dev enp86s0 and via 10.54.225.89.

Manual Recovery

If routes are missing (e.g., after a network restart or interface flap), add them manually:

# Add route to Tata SBC
sudo ip route add 10.79.215.102/32 via 10.54.225.89 dev enp86s0

# Add route to media pool 1
sudo ip route add 10.79.167.0/28 via 10.54.225.89 dev enp86s0

# Add route to media pool 2
sudo ip route add 10.79.167.48/28 via 10.54.225.89 dev enp86s0

Or bring the interface down and up to re-trigger the persistent config:

sudo ifdown enp86s0 && sudo ifup enp86s0

Verify after recovery

After adding routes manually or cycling the interface, always verify with ip route show dev enp86s0 and test with a ping to the Tata gateway:

ping -c 3 -I enp86s0 10.54.225.89