Web UI disconnects when using multiple NICs and multiple subnets

TrueNAS General
,
1

Hello, I’m new here. I did a search and found some similar topics that amounted to an invalid configuration. I think what I’m trying to do is different enough so I’ll ask just in case this is possible and I’m just configuring something incorrectly.

TLDR: I have multiple NICs setup and when I access the web UI I frequently get disconnected with the error “Connecting to TrueNAS … Make sure the TrueNAS system is powered on and connected to the network.”

I am running a homelab. I have several networks configured and use pfSense as my router.

I’ve installed TrueNAS Scale to a Dell R710 and have connected four RJ45 ports to a managed switch. I’ve set it up this way:

  • Port 1: 192.168.10.5/24 (connects via Access port to VLAN 10, Management VLAN)
  • Port 2: 192.168.14.5/24 (connects via Access port to VLAN 14, Storage VLAN)
  • Ports 3 and 4: aggregated as bond0 (connects as Access ports to VLAN 12, Production VLAN)
  • bond0: 192.168.12.5/24 (Ports 3 and 4)
  • Global Configuration (network): Nameserver and gateway are 192.168.10.1 (this is my pfSense host on that network).
  • General Settings \ Web Interface IPv4 Address: 192.168.10.5
  • pfSense has a gateway interface on both management and production network with x.x.x.1/24

My intention behind this was:

  • Management VLAN is where I can manage this and any other equipment on my network (for example I connect iDRAC to the same network)
  • Storage network is for things like iSCSI
  • Production network will be where I expose SMB and NFS for apps and resources to use

For the most part I try to keep the Management network isolated from other networks, but for ease of use I do have some routes enabled in pfSense so that a few specific machines (like my personal desktop) can route from Production to Management to manage devices. This works with everything else fine, but with TrueNAS I’m frequently getting kicked out of the web UI.

Something like every 2 minutes I get the error: “Connecting to TrueNAS … Make sure the TrueNAS system is powered on and connected to the network.”

This issue only began once I started adding other network connections to TrueNAS.

On my machine right now if I run tracert 192.168.10.5 I get:

1 pfsense [192.168.12.1]
2 TRUENAS [192.168.10.5]

So I’m routing from my machine to TrueNAS properly, I’m landing on the interface that is configured to be the only one with the web UI. I can also ping that IP and get a response, no problem. I don’t understand why the web UI keeps cutting out.

2

I don’t understand this.

What is your machines address.?
Why are you tracert the xxx.1 address?

3

Good catch, that was a typo which I have now fixed - it was tracert 192.168.10.5 as in tracert to the TrueNAS.

The machine I am connecting from is 192.168.12.54, on the production network.

4

So, it will route asymetrically
It will go via pfsense in one direction
and come back directly in the other direction.

My guess is pfsense doesn’t like that

If you connect from 192.168.10.54 it should all work.

1 Like
5

This is the way… asynchronous routing and pfSense state timeouts. There are a couple of options such as modifing the state types on rules, timeouts or changing Firewall Optimization on pfSense or OPNsense.

Typically and IMO asynchronous routing isn’t something you want, so I avoid this type of config. The correct way is using VRFs or FIBs on a device so you can have multiple routing tables. But this isn’t supported on truenas.

Sorry for the bad news, but without VRF you cannot configure segmented management interfaces properly. I am looking into options for this myself.