October 21, 20205 yr [Solved] Unfortunately I tried many many things and don't know what specifically brought it back online but all good now. Yesterday we had an internet outage (not actually sure what went wrong but basically unplugged and replugged everything and it started working again) and for whatever reason every device in my home is back online just fine except for the unraid box which keeps pulling a 169.254.x.x IP which, from my research so far, seems to indicate it failed to get a proper DHCP lease. In addition to not being a correct IP from my DHCP server I also can't connect to this IP from another machine via the web UI. My router is a pfsense box which allocates 192.168.125.100 through 192.168.125.254 for dynamic leases and I also have a static IP outside of this range (192.168.125.10) configured for the Unraid box which it can't seem to grab. Also to be clear this configuration was working fine until the outage yesterday. Also every other device in my network is grabbing IPs within range and have internet access no problem. Things I have tried: Restarting unraid Restarting pfsense Using a different network cable from the unraid box to my switch Using a different port on the switch (Note: all other ports are in use and all devices besides Unraid pull IPs just fine) Deleting the static IP configuration in pfsense Re-adding the static IP configuration in pfsense Deleting the network config file on my unraid boot drive I have grabbed the diagnostics and attached them here in case anyone has any ideas. I don't have a ton of experience looking through these logs but this seems to be relevant: Oct 20 22:33:12 Apollo kernel: device bond0 entered promiscuous mode Oct 20 22:33:12 Apollo kernel: IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready Oct 20 22:33:12 Apollo kernel: 8021q: adding VLAN 0 to HW filter on device bond0 Oct 20 22:33:12 Apollo kernel: br0: port 1(bond0) entered blocking state Oct 20 22:33:12 Apollo kernel: br0: port 1(bond0) entered disabled state Oct 20 22:33:12 Apollo rc.inet1: polling up to 60 sec for DHCP server on interface br0 Oct 20 22:33:12 Apollo rc.inet1: timeout 60 dhcpcd -w -q -t 10 -h Apollo -C resolv.conf -4 br0 Oct 20 22:33:12 Apollo dhcpcd[2238]: br0: waiting for carrier Oct 20 22:33:13 Apollo kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 1 Gbps, Flow Control: RX/TX Oct 20 22:33:13 Apollo kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex Oct 20 22:33:13 Apollo kernel: bond0: making interface eth0 the new active one Oct 20 22:33:13 Apollo kernel: device eth0 entered promiscuous mode Oct 20 22:33:13 Apollo kernel: bond0: first active interface up! Oct 20 22:33:13 Apollo kernel: br0: port 1(bond0) entered blocking state Oct 20 22:33:13 Apollo kernel: br0: port 1(bond0) entered forwarding state Oct 20 22:33:13 Apollo dhcpcd[2238]: br0: carrier acquired Oct 20 22:33:14 Apollo dhcpcd[2238]: br0: soliciting a DHCP lease Oct 20 22:33:19 Apollo dhcpcd[2238]: br0: probing for an IPv4LL address Oct 20 22:33:24 Apollo dhcpcd[2238]: br0: using IPv4LL address 169.254.35.72 Oct 20 22:33:24 Apollo dhcpcd[2238]: br0: adding route to 169.254.0.0/16 Oct 20 22:33:24 Apollo dhcpcd[2238]: br0: adding default route Oct 20 22:33:24 Apollo dhcpcd[2238]: forked to background, child pid 2280 Anyone have ideas on what could be going wrong or things to try? Edited October 22, 20205 yr by aspiziri
Archived
This topic is now archived and is closed to further replies.