So built a new machine to replace an aging unraid server.

 

On first boot to unraid, IP address is not getting assigned.

 

 

I know the 169.254.* ip is a result of this machine not being assigned an IP address via DHCP.

 

Some googling yields a number of similar occurrences, but no obvious answer.

 

Things I've tried so far:

 

- Using 3 different types of usb sticks

- Unraid versions 6.8.2 and 6.8.3

- network.cfg = USE_DHCP = yes and no

- network.cfg = BONDING = yes and no

 

The the one and only NIC is onboard Realtek:

 

 

I'm preparing to purchase a pcie nic card to see if it's an issue with the onboard nic.  But running windows from this same machine, there are NO networking issues (I'm planning to passthrough a win10 nvme to vm).

 

Diagnostics are here:

 

tower-diagnostics-20200623-1050.zip

 

Any insights would be appreciated.

Edited June 24, 20206 yr by thisguyhere
grammar

You have other clients on that network getting a proper DHCP address?  Your logs show something weird. 99.X network? 

Can't you just setup a static IP under Setting / Network Settings.  Boot in GUI and setup up that way?

 

 

Jun 23 10:43:34 Tower kernel: r8125: eth0: link up
Jun 23 10:43:34 Tower kernel: br0: port 1(eth0) entered blocking state
Jun 23 10:43:34 Tower kernel: br0: port 1(eth0) entered forwarding state
Jun 23 10:43:34 Tower dhcpcd[2116]: br0: carrier acquired
Jun 23 10:43:35 Tower dhcpcd[2116]: br0: soliciting a DHCP lease
Jun 23 10:43:36 Tower dhcpcd[2116]: br0: offered 99.1.1.90 from 99.1.1.1
Jun 23 10:43:40 Tower dhcpcd[2116]: br0: probing for an IPv4LL address
Jun 23 10:43:45 Tower dhcpcd[2116]: br0: using IPv4LL address 169.254.249.152
Jun 23 10:43:45 Tower dhcpcd[2116]: br0: adding route to 169.254.0.0/16
Jun 23 10:43:45 Tower dhcpcd[2116]: br0: adding default route

 

99.1.1.90 is a public IP so thats weird it was offered that if it is plugged into your lan. 

https://db-ip.com/99.1.1.90

Realtek came up in another thread today too:   

 

 

2 hours ago, thisguyhere said:

I'm preparing to purchase a pcie nic card to see if it's an issue with the onboard nic.  But running windows from this same machine, there are NO networking issues

In general, you're better off avoiding Realtek in Unraid. The may work OK in Windows, but their Linux drivers are hit and miss. They will work in one version and then have problems after an upgrade.

2 hours ago, johnwhicker said:

Your logs show something weird. 99.X network? 

 

2 hours ago, PeteAsking said:

99.1.1.90 is a public IP

that's what i have my lan ip range set to, just because it's easier to type (ultra laziness).

 

29 minutes ago, ljm42 said:

you're better off avoiding Realtek in Unraid

 

got it, yea the previous (current) server has a supermicro mb + intel nic and it's been troublefree.

 

i'll get a hold of a pcie intel nic and try again.

 

thanks for linking to the other post describing it.

Edited June 24, 20206 yr by thisguyhere

Yup, as expected, it was the NIC.  Got a intel nic today, everything's working fine now.

 

Damn realtek...