Port 2 on NIC, Causes hanging

[panzerscope]

Hello all,

I am noticing some strange behaviour regarding my NIC in TrueNas Core 13.

My NIC is the Intel X540 T2. I decided yesterday that I would make use of the second port on the NIC. However after it was setup, either via DHCP or Static, I noticed a couple of odd things.

1. Plex Streaming started to become jumpy or completely stop. Nothing had changed with Plex at all. Only change was the enabling of the second port on the NIC. Plex was still using port 1.

2. When shutting down or restarting TrueNas, it would hang when reaching the "Syncing Buffers" Stage. I left it for ages but nothing. However, as soon as a physically disconnected my LAN cable from port 2 on the NIC, the system shutdown. I was able to replicate this again, so it was not coincidental. So something regarding the second port on the NIC is causing the system to hang/do unexpected things.

Fortunately I had a second X540 T2 to test, thinking that just possibly I had a bad NIC. However we can throw that possibility out the window as with the replacement NIC, I get the exact same behaviour.

Still being new to the whole platform I am unsure how to retrieve any appropriate logs for looking at and to show you guys. Could someone give me a hand ?

Many thanks,
P

 

[sretalla]

How have you set up the second port? Are you using a bridge and/or LAGG/LACP?

 

[panzerscope]

How have you set up the second port? Are you using a bridge and/or LAGG/LACP?

Admittedly none, I set it with a static IP via my router so even though the NIC was set to DHCP, the router was giving it an address based on its MAC address. but thinking about it, perhaps it should have been set in bridge mode ?

 

[Patrick M. Hausen]

You need to define what exactly you want to achieve. If you "just connect" and some of the magic built into TrueNAS works out the wrong way, you create a bridge across both ports. This will bring down your network.

You cannot have two interfaces with different IP addresses in the same network. If you want to "bundle" two ports for resiliency and bandwidth, you need a managed switch and LACP. If you want some kind of manual load distribution by e.g. putting all file sharing service on one NIC and VMs and/or jails on another, that can be done but needs specific complex setup beforehand.

 

[panzerscope]

You need to define what exactly you want to achieve. If you "just connect" and some of the magic built into TrueNAS works out the wrong way, you create a bridge across both ports. This will bring down your network.

You cannot have two interfaces with different IP addresses in the same network. If you want to "bundle" two ports for resiliency and bandwidth, you need a managed switch and LACP. If you want some kind of manual load distribution by e.g. putting all file sharing service on one NIC and VMs and/or jails on another, that can be done but needs specific complex setup beforehand.

Hey Patrick,

Thanks for your response. So yes, originally my thoughts were to run different services over different ports as I was having issues with TeamViewer at one point as it kept removing my "Easy Access" two the two VM's I have on TrueNas. I felt this may be because I have Two VM's running off of one port with the same MAC address and thought TeamViewer was not liking it. However for whatever reason after a while that seemed to resolve itself.

Ultimately at the moment I no longer NEED to split my services over two different ports, however if I wanted to, what would that complex setup be ? Just so I have some idea.

Thanks!