Hi all,

 

I have been using unraid for sometime but am spinning up a new server with some more resources and running in a rack mount vs a tower. Now this server has alot of extra ports (which i may not be using for some time at least) but it seems to have selected the fiber cards as eth0 and the ethernet ports dont kick in until Eth2.

 

Now for a summary

eth0-1 - Fiber cards both disconnected

eth2-3 configured in 802.3ad bonding (Connected to a Fortinet unit and supports aggregation )

 

Now I have already found it odd that eth0 seems to be the source of the DNS as for some reason there is no DNS collected from by ethernet cards and i needed to manually enter 1.1.1.1 for any DNS to actually resolve even when the card is not connected.

 

Now I wanted to know, best practice as I have seen some comments and posts online where comments have been 'just add everything to Eth0 and if its offline it wont impact anything' but if i plan to enable these ports later that will likely cause some down the track issues im sure.

 

The main reason why I'm asking is there is a number of odd issues I have noticed in this, my second Unraid deployment which seem to all point back to Eth0 not being used as the IP source.

 

The issues I have come across are 

- Unable to load dicker web UI on bridged and get 'about:blank#blocked' but works when manually typing in the port on the server

- Some docker containers seem to have very slow or in-consistant network connections (I tested downloading 1tb via bridged on the 802.3ad so that seems to be stable but some odd errors like servers unable to source the public IP address and needing it manually entered)

 

 

So I'm hoping someone can shed some light or is the true fix 'just add all the ethernet to Eth0 and bond that with 802.3ad untill they are activated?

eth0 is used for the Unraid GUI so I would have thought if the fibre cards are disconnected you need to set another LAN card as eth0.    Unraid allows you to specify which card should be treated as eth0.

43 minutes ago, itimpi said:

you need to set another LAN card as eth0.

How would one do this? As my cards arnt connected (no cable connected) but its showing as Eth0 and I cant see any settings to switch them or change the mapping?

 

Or would that be this section here?

 

Also I would guess making this change would kill my connection I assume i should make these changes on the terminal? Can you start the GUI from the CLI in the terminal or does it need a reboot?

20 minutes ago, brent3000 said:

Or would that be this section here?

Yes, set the NIC you want as main to eth0, note that you have to reboot for the changes to take effect.