June 18, 20233 yr Unraid version: 6.11.5 I have two NICs in my system; a 1G NIC built into the motherboard which is unused, and a 2.5G NIC on an external card which is the primary network connection. Originally, I had the 2.5G NIC setup as eth0 and the 1G NIC setup as eth1, which bridging, etc. turned on on eth0 for my VMs. However I discovered that after a reboot my VM wasn't able to connect to the network and upon further investigation it seems that the NICs have switched places, with the 1G NIC becoming eth0 and the 2.5G card becoming eth1, which has bridging disabled. Is there a way to lock a NIC to a particular interface so that it doesn't change at reboot?
June 18, 20233 yr Community Expert If you go to Settings -> Network Settings -> Interface Rules and set eth0 and eth1 the way you want and then reboot the settings won't keep?
June 18, 20233 yr Author 5 hours ago, JorgeB said: set eth0 and eth1 the way you want I'm sorry, I must be missing something obvious but how do I do that on this page? The 2.5G NIC is being set as eth1 in this SS, I want it to be eth0.
June 19, 20233 yr Community Expert It's missing that setting, delete/rename /boot/config/network.cfg (and network-rules.cfg if it exists) and reboot, note that network settings will go to default DHCP.
June 29, 20233 yr Author On 6/18/2023 at 11:51 PM, JorgeB said: It's missing that setting, delete/rename /boot/config/network.cfg (and network-rules.cfg if it exists) and reboot, note that network settings will go to default DHCP. Renamed the network config to a different name. Finally got the chance to reboot. The interfaces switched places again, but I still don't see the setting to assign the interfaces. Any ideas what would cause this?
June 29, 20233 yr Community Expert In your new post, attach your diagnostics file. Be sure that this file includes the time period when you updated the configuration with the desired settings.
June 30, 20233 yr Author 17 hours ago, Frank1940 said: In your new post, attach your diagnostics file. Be sure that this file includes the time period when you updated the configuration with the desired settings. Diagnostics attached. Not really sure what you mean by "when you updated the configuration"; I can't update the configuration to assign a NIC to eth0 because the menu to do so isn't there. tower-diagnostics-20230629-2011.zip
July 3, 20233 yr Community Expert Just now, sazrocks said: Bump. Anyone know why the NIC assignment menu is missing? Had you stopped the array? Not currently in a position to check, but I suspect that is needed.
July 3, 20233 yr Author 1 minute ago, itimpi said: Had you stopped the array? Not currently in a position to check, but I suspect that is needed. Yes the array was stopped. If the array isn’t stopped then all the NIC configuration fields get grayed out and a message tells you to stop the array.
July 3, 20233 yr Community Expert Network-rules.cfg is not getting created, without that you won't have an option to select the NICs, you can try deleting network.cfg and reboot to try again or update to v6.12 to see if it's any different.
July 3, 20233 yr Author 37 minutes ago, JorgeB said: Network-rules.cfg is not getting created, without that you won't have an option to select the NICs, you can try deleting network.cfg and reboot to try again or update to v6.12 to see if it's any different. No dice. I guess I’ll go to 6.12.2 now. Hopefully I don’t see stuff spontaneously disappear like others have…
July 3, 20233 yr Author 1 hour ago, JorgeB said: Network-rules.cfg is not getting created, without that you won't have an option to select the NICs, you can try deleting network.cfg and reboot to try again or update to v6.12 to see if it's any different. Upgraded to 6.12.2, still no menu to set the NIC assignments. Also 6.12.2 caused my array to no longer stop properly, fun
July 4, 20233 yr Community Expert If 6.12 doesn't help with creating network-rules.cfg you can downgrade.
July 4, 20233 yr Author 13 hours ago, JorgeB said: If 6.12 doesn't help with creating network-rules.cfg you can downgrade. Went ahead and did that, I can successfully stop the array now. Still no interface rules though.
July 5, 20233 yr Community Expert You'd need to try with a different NIC/board, unfortunately this is known to sometimes happen.
July 5, 20233 yr Author 8 hours ago, JorgeB said: You'd need to try with a different NIC/board, unfortunately this is known to sometimes happen. Um, ok? Is there a list of officially supported NICs? I thought I would be safe with the Intel I211 in my motherboard and Intel I225-V in my 2.5G card…
July 5, 20233 yr Community Expert It's not NIC specific, I have those same NIC without issues, possibly could be more board related, but it's just my opinion.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.