cheesysenator

After some total reconfiguration of my home network, adding an additional router and routing ethernet wires through it, the problem is fixed. The fiber modem seems to only want to have one device immediately attached to it, and got confused when a switch was attached to it. Seems like the fiber install guy should have known something about that, considering he plugged a switch into the fiber modem, but, whatever. Now the DHCP server is accessible.

What does the wireguard tunnel on my PC have to do with unraid being unable to reach the DHCP server?

Here they are.

I suppose the DHCP server is run on the fiber box provided by my ISP. I have tried restarting that a number of times to no avail. Could it be some weirdness since I'm running straight back there rather than through a router? My PC works fine with the same configuration...

I have completely removed the intel nic and plugged into the 1 gig on-board card. It is still not generating a proper IP address. I have attached a new diagnostics file. There is also not a vlan switch on my switch. tower-diagnostics-20241228-2127.zip

Shouldn't be anything. I know I haven't configured anything like that. The unraid server is plugged into an unmanaged switch which is running other devices without issue.

Yes, leds on both ends light up and blink. On motherboard eth port and eth switch

Tried that several times during this process. It did not work.

Planning to use the intel NIC. The other one doesn't even have a cable connected. The connection to the router should be fine, there is another computer connected to the same switch that is functioning fine. Tried different ports and cables to no avail.

Definitely does regenerate config with bonding enabled, although I don't know why that would be the problem. If I set USE_DHCP to 'yes', then it fails to contact the DHCP server for an IP, staying in the 169 range, and is unreachable. If I set it to 'no', I specify the IP, and I can see the IP in my network from my desktop, but it is unreachable. All pings will timeout. I have tried it now with and without bonding, by editing the file to remove the bonding lines. Neither way has worked.

When I delete the network.cfg from another computer, it regenerates with the same settings, bonding included.

Bond deleted, plugged into realtek card, still nothing. Rebooting seems to reinitiate the bond, so I'm guessing I need to disable bonding altogether? I can't find how to do that online without using the GUI, which I cannot access. The "two" intel cards are actually one card with two ports. I would like to use one of them for my unraid. Assuming I need to disable bonding, how can I do that without GUI access?

So tonight I was mucking about trying to figure out why the apps tab on my unraid server wouldn't load after a reboot. In the process of diagnostic, I unplugged the ethernet cable and plugged it back in. After that, I was no longer able to access my server in any capacity. No webgui, no access to my array. I tried deleting the network.cfg to generate a fresh one and nothing. The IP it shows on startup is 169.254.208.234, but when I try to connect to that via HTTP://169.254.208.234, I get HTTP://169.254.208.234 is unreachable. I'm new to unraid and an event like this is leaving me very lost. I've attached the diagnostics file if anyone can help me. Still don't know why the apps page won't load after reboot. tower-diagnostics-20241225-1938.zip