Hi, 

 

I have recently installed a 4-port NIC in my unraid server for use with pfSense. When I first installed it unraid grabed it and used one of the ports on that card as eth0. Then I went to the Network Setnings and under Network rules I changed the ports so that the onboard nic got the name eth0 so it became the default port. Then I went to the system devices page and added all four ports on the extra nic to bind to vfio on boot, rebooted and assigned them to the vm running pfSense. All worked fine and I got pfsense up and running no problem and unraid was using the onboard nic dor it's network interface (eth0). 

 

Then today when I needed to reboot the system I could not get it online. The pfSense VM botted and all went good there, but the onboard nic did not work so the server all but pfsense vm was offline. I then rebooted into GUI-mode so I could see what was going on. There I saw that unraid had renamed the onboard nic to eth1 and eth0 had no physical port. 

 

I have googled a lot and found that it might be the nic getting renamed to eth1 during boot for some reason, I found that some had solved this by editing a persistant network rules file, but I cant find it on my usb flash stick. I can see in the system logs that it got renamed at some point. Is there a easy way to get unraid to change the onboard nic to eth0 on boot? The mac addr for the onboard nic is: 10:7B:44:4B:28:D5 

 

And I am not able to change the name manually from the GUI as I see it now. I will attach the syslogs.

 

Thanks for any tips

tower-syslog-20210904-0811.zip

tower-diagnostics-20210904-1427.zip

Edited September 4, 20214 yr by Vegard

4 hours ago, Vegard said:

I will attach the syslogs.

Instead

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
 

Here are the diagnostics attached. I also edited the org. post with the diagnostic file now.

tower-diagnostics-20210904-1427.zip