So, after years using my unraid server with  a i7 6700k I finally upgraded to a xeon e5 2696v4. 

 

Upgrade went smooth and all the drives are in the right place but I have a problem here:

 

The onboard NIC is gigabit only and I have a second NIC which is 2.5gbit. 

The onboard NIC is set as ETH0 and the PCIE is set as ETH1. 

 

All I want to do is to invert it but sadly I'm one of those that interface rules section doesn't show up at all. 

 

What I've tried so far:

 

• deleting /boot/config/network.cfg
• create /boot/config/network-rules.cfg
• moving 2.5gbit NIC from PCI-E slots
• upgrading unraid from 6.12.10 to 7.0.1
• Tried disabling onboard NIC but there's no option in bios to do so. 

 

Is there any way to replace ETH0 with ETH1 and vice versa? 

Edited May 1, 20251 yr by TheFreemancer

FINALLY GOT IT WORKING:

 

This is sadly the only solution:

 

 

Basically, deleting network.cfg won't solve my problem because when rebooting unraid will create a new network.cfg with active backup and bonding between both interfaces.

 

What worked for me was: create the network-rules.cfg like this:

 

# PCI device 0x15b3:0x1003 (mlx4_core)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="*******", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x1533 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="******", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

 

set each mac address to the interface you want. 

 

And I had to have a network.cfg ready for this to work, no bonding, and everything set up as I wanted. 

 

and you can't reboot from ssh, reboot from unraid gui. Not sure why but it seems to be a different kind of reboot to apply those settings. 

 

This is such an old bug from unraid, not having the interface rules section sucks. I gave 4+ hours trying different solutions to such a simple problem. 

This should be fixed ASAP.

Spoke too soon. 

 

After rebooting and getting the right NIC as ETH0.. unraid created a ETH123?? wtf.. 

 

And this would not show up in settings and it seems this is not persistent when rebooting. 

 

EDIT: Gave up, I'm swaping the cables and have to give up 2500 network for now. 

I'll order another PCIE NIC and see if unraid enforces so badly a NIC to be it's default one. 

 

Edited May 1, 20251 yr by TheFreemancer

On 5/2/2025 at 4:43 AM, TheFreemancer said:

# PCI device 0x15b3:0x1003 (mlx4_core)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="*******", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x1533 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="******", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

mlax4 should be 10G NIC, but you never mention your system have 10G NIC. The problem likely relate 2.5G NIC detect problem.

 

I got similes problem when trying USB-NIC, never have problem with PCIe-NIC and easy swap NIC in GUI.

Edited May 2, 20251 yr by Vr2Io

12 hours ago, Vr2Io said:

mlax4 should be 10G NIC, but you never mention your system have 10G NIC. The problem likely relate 2.5G NIC detect problem.

 

I got similes problem when trying USB-NIC, never have problem with PCIe-NIC and easy swap NIC in GUI.

 

The commented line is from the network-rules.cfg example from the post I linked earlier. 

I only made adjustements for the MAC ADDRESS which I replaced with ***** to hide it here. 

 

 

I actually got it working as I wanted. I had another spare 2.5NIC with 4 ports. Intel chipset.

Put those on unraid and interface rules showed up. Still no option to switch eth0, only eth1 2 3 4.

 

So I took it to chat gpt and got a way to block the onboard nic via syslinux.cfg. 

 

Now I can switch anyway I want all 4 and eth1 became eth0.