Network config fails after reboot

[eJwhNt8tFCJVKJL]

Hello,

 

I'm experiencing an issue that I haven't been able to figure out. My unraid instance seems to remember its network setting following a reboot, but either they don't take affect or the routes fail during startup. During boot, it errors out saying something along the lines of "can't find bond1"

 

I'm running a quad gigabit ethernet nic in a 802.3ad bonding configuration. I've set it to both bonding and bridging.

When I reboot, no network connectivity to or from unraid is possible at first. I have to go into the network settings and change anything on the eth1(bond primary) nic hit apply and then it works until I reboot again.

Any help here would be greatly appreciated.

 

Thanks

Edited April 10, 2020 by eJwhNt8tFCJVKJL

[bonienl]

Unraid uses eth0 as its management connection.

 

You need to reconfigure your network settings and use eth0 instead of eth1.

[eJwhNt8tFCJVKJL]

craftsman, thanks for the response!

Eth0 is the onboard nic in my system. Can I configure unraid in such a way that I eth0 is only used for management and the lagg group can be used for network shares and docker?

 

 

 

[bonienl]

Unraid management and shares both use eth0.

It is possible to use a different interface for docker containers, see Docker Settings.

 

Under Interface Rules you can re-assign interfaces, e.g. swap eth0 and eth1

Edited April 10, 2020 by bonienl