April 9, 20251 yr So a little back story, I was running consumer HW without issues and recently switched to some server grade HW. This includes an ASROCK ROMED8-2T MB with 3 ethernet ports 1 IPMI, and 2 10Gig Intel NIC's. However, for the life of me I cant figure out what is going on with my ethernet settings. For some odd reason when Unraid boots the ethernet ports are telling me all different things about the IP address. I can connect to the IPMI and Unraid, but Unraid can't connect to the internet for some reason. None of it is making any sense. Anyone have suggestions and yes setting statics freaks everything out? Connect to Addresses: IPMI - 10.27.20.236 or 10.27.30.220 Unraid - 10.27.30.169 or 10.27.30.170 Unraid Boot: 169.254.188.22 Unraid Web GUI: Eth0: 169.254.188.22 Eth1: 10.27.30.169 Eth2: 10.27.30.170 MB IPMI GUI: Eth0: 10.27.20.236 Eth1: 10.27.30.220 Eth2: doesnt show up Ubiquity Switch: Eth0: 10.27.20.236 Eth1: 10.27.30.169 Eth2: 10.27.30.170 Edited April 9, 20251 yr by neomac3444
April 9, 20251 yr An adapter normally gets an 169 address when there is no connection, so there may be something wrong with the Eth0 cable, or the device on the other end (perhaps a bad port). Since you don't have bridging enabled, it uses that non-existing connection and so can't reach the internet, so you'll need to fix that.
April 9, 20251 yr Community Expert 6 hours ago, neomac3444 said: ASROCK ROMED8-2T Make sure you are running 7.0.1 or newer, 7.0.0 for example, will have an issue with the IPMI NIC.
April 9, 20251 yr Author 7 hours ago, JorgeB said: Make sure you are running 7.0.1 or newer, 7.0.0 for example, will have an issue with the IPMI NIC. I am currently running 6.12.15 - do i need to upgrade to 7.0.1? or can i stay on 6 until i get this resolved? 8 hours ago, Wody said: An adapter normally gets an 169 address when there is no connection, so there may be something wrong with the Eth0 cable, or the device on the other end (perhaps a bad port). Since you don't have bridging enabled, it uses that non-existing connection and so can't reach the internet, so you'll need to fix that. So that's what is odd, that is the IPMI port which does have an IP but, I feel like unraid shouldn't even be reading this port as it shouldn't be trying to communicate through it. Is there a way to disable the eth0 so it can ignore the port in Unraid? I dont want to disable it on the MB since i still want to be able to use the IPMI feature of the machine. The other thing that doesnt make sense is i can access the IPMI from both eth0 and eth1 using the respective IP's per the MB's "ip address". However, i can also access Unraid at the same time with eth1 and eth2 using the ip address per Unraid. When i change the eth0 ip address to a static address in unraid GUI i can no longer access unraid via web terminal from any IP and have to go back to the GUI on the machine.
April 9, 20251 yr Community Expert Solution 2 minutes ago, neomac3444 said: I am currently running 6.12.15 That release also has the issue, and I believe only security patches are expected for 6.12, but maybe they will include it if/when 6.12.16 is released, since it's a simple fix, for now you can do it manually: https://forums.unraid.net/bug-reports/stable-releases/61214-no-network-after-updating-eth0-assigned-to-virtual-usb-nic-cdc-ethernet-device-with-169-ip-instead-of-mellanox-10gbe-nic-r3407/#findComment-31251 After blacklisting the driver, also delete /config/network-rules.cfg and reboot.
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.