So ETH0 is somehow connected to my BMC (ASRock ROMED8-2T) 

I think I figured out it's some sort of USB NIC that gets pushed through. 

 

This causes delays when booting, and changing any network related options, 

 

I would like to just disable this random ETH0 and use ETH1/2 as my main networks. 

But for whatever reason as soon as I mess with it, I lose all connection. 

 

I would love some assistance here if anyone knows? 

 

lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 005 Device 012: ID 046b:ff01 American Megatrends, Inc. Virtual Hub
Bus 005 Device 013: ID 046b:ffb0 American Megatrends, Inc. Virtual Ethernet
Bus 005 Device 014: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse

 

That virtual ethernet I believe is what is causing my pain. 

namek-diagnostics-20250102-0958.zip

Current setup:

 

Not sure why you keep creating new threads, did you see this reply in the previous one?

 

Try this:

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

 

4 hours ago, JorgeB said:

Not sure why you keep creating new threads, did you see this reply in the previous one?

 

Try this:

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

 

 

Yes I did see that, let me try it again with a fresh install of unRAID.

 

I did find that IP would work but only after about 5mins of being booted... 

Its like it tries ETH0 and then goes yup its defo down, and then does the br0 failover to ETH1.

 

And sorry for the multiple posts.

@JorgeB

I did the command:

echo "blacklist cdc_ether" > /boot/config/modprobe.d/cdc_ether.conf

 

Restarted and I still see ETH0.

 

I did see during boot up:

 

 

And I still cannot disable or remove this ETH0, so I have to leave it there otherwise I get no network.

If I click the bonding and change type or anything else I just get nothing.

Post new diags please.

1 hour ago, JorgeB said:

Post new diags please.

namek-diagnostics-20250103-1212.zip

 

Thanks 

Not sure why, but this is the second case I've seen where the NIC is renamed from eth0 to eth1 during boot:

 

Jan  3 09:22:23 namek kernel: ixgbe 0000:42:00.0 eth1: renamed from eth0

 

The solution for now is to use a bond with eth1 or eth2

38 minutes ago, JorgeB said:

Not sure why, but this is the second case I've seen where the NIC is renamed from eth0 to eth1 during boot:

 

Jan  3 09:22:23 namek kernel: ixgbe 0000:42:00.0 eth1: renamed from eth0

 

The solution for now is to use a bond with eth1 or eth2

Yeah I've left it as a Bond as per the image above.

If I disable that I lose everything.

 

Is it worth uncommenting out that blacklist and just leaving it default until we get some sort of solution?

You can still leave the driver blacklisted, since it cannot be used, this was due to a kernel change, hopefully they will fix it gain in a future kernel release, or Asrock needs to update their BIS/firmware, this is only happening with Asus and Asrock boards AFAIK, it does not happen to my Supermicro boards with IPMI.

4 hours ago, JorgeB said:

You can still leave the driver blacklisted, since it cannot be used, this was due to a kernel change, hopefully they will fix it gain in a future kernel release, or Asrock needs to update their BIS/firmware, this is only happening with Asus and Asrock boards AFAIK, it does not happen to my Supermicro boards with IPMI.

Makes sense, thanks Jorge for helping me out