- Solved
- Urgent
Hi,
Summary:
Since upgrading from Beta4 to either RC1 or RC2 it is not possible to connect to the network anymore.
The reason seems to be that an additional ethernet interface is detected which sets itself up as ETH0 and is not even to be able to be changed via the "interface rule" settings or with deleting the config/network.cfg file.
Hardware:
The following hardware is built into the server:
Motherboard: Asus W680-Ace IPMI
Network Card: TP-Link TX401 - a 10gig network card based on the Aquantia AQC107 Chipset
In addition it is important to say that i normally have the 2x2,5gig onboard ethernet ports disabled in the BIOS.
Details / Troubleshooting steps:
When using Unraid 7 Beta4 (or older, like 6.12) only one ethernet interface is detected - The 10gig network card.
Once RC1/RC2 is installed an additional ethernet card is detected which gets configured to ETH0 (MAC 36:2F:E6:75:BD:8B).
Unfortunately i am not really well versed in linux and can not find out for the life of me what that device actually should be.
Per default this new card is bonded with the 10gig card (which is now eth1) and i have no route to my network.
I can remove the bonding, but i get no "interface rule" to select the 10gig card as eth0 and the new device as eth1.
I would expect that if i have more than one device i would get the "interface rule" setting to show up.
Where it even gets stranger is once i enable the two onboard 2x 2,5gig ports. (done for troubleshooting purposes)
At this point the "interface rule" option shows up with selections for the 10gig and the two 2,5 gig ports/cards.
The strange thing here is i can then select them between eth1, eth2 and eth3, but i get no possibility to change any of them to eth0.
I also do not get the possibility to select/shift the new device to anything else than ETH0, it does not even show up in the "interface rule" configuration.
Seems like that this new detected device is hard stuck/configured on eth0.
Although i have not yet tried to just change the eth assignment in the network.cfg file if this would help.
Also disregard the wonky IP address in the RC2 screenshot.
I tried to properly set up the new device to my standard 192.168.1.5 IP with proper gateway/...
I simply cannot connect to it. Even stranger is that the bonding does not work where i would then connecto through eth1
Network Settings Beta4:
Network Settings RC2 (via Unraid GUI / IPMI)
Additionally attached are the diagnostics of the Beta4 and the RC2 installation.
Beta4_slave-diagnostics-20241221-1929.zip RC2_slave-diagnostics-20241221-1942.zip