Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Solved] Please Help, Network Issues with compromised array

Featured Replies

Hello all,

Long time user, but I believe this is my first request for help... It's also been a while since I have posted.

 

I have been fighting this issue for a few days now and cannot for the life of me find a solution. Searching google and the forum have yielded no results.

 

The story:

Unraid 6.1.6

I had a data disk show up as red the other day.  I bought a new hard drive and replaced the disk (physically inside the computer).  I booted up the computer back up and now my eth0 interface won't get a good ip address via dhcp.  My syslog shows it getting a good ip(192.168.1.3) from my router(192.168.1.1) but then drops it in favour of a non-valid ip address(for my network, from 192.168.0.254 which does not exist on my network).  I have tried rebooting my router, using different ports on the router as well as multiple cables.  I even purchased a new pci Ethernet card with the same result. The last reboot, a few weeks ago, was without any issue.

 

Syslog attached.

 

these lines stand out to me:

Apr 21 17:47:27 server dhcpcd[1417]: eth0: sending DISCOVER (xid 0xaa5107c2), next in 4.0 seconds

Apr 21 17:47:27 server dhcpcd[1417]: eth0: offered 192.168.1.3 from 192.168.1.1

Apr 21 17:47:27 server dhcpcd[1417]: eth0: sending REQUEST (xid 0xaa5107c2), next in 3.2 seconds

Apr 21 17:47:27 server dhcpcd[1417]: eth0: acknowledged 192.168.1.3 from 192.168.1.1

Apr 21 17:47:27 server dhcpcd[1417]: eth0: probing for 192.168.1.3

Apr 21 17:47:27 server dhcpcd[1417]: eth0: ARP probing 192.168.1.3 (1 of 3), next in 1.7 seconds

Apr 21 17:47:29 server dhcpcd[1417]: eth0: ARP probing 192.168.1.3 (2 of 3), next in 1.8 seconds

Apr 21 17:47:29 server dhcpcd[1417]: eth0: ignoring offer of 192.168.0.103 from 192.168.0.254

Apr 21 17:47:29 server dhcpcd[1417]: eth0: ignoring offer of 192.168.0.103 from 192.168.0.254

Apr 21 17:47:29 server dhcpcd[1417]: eth0: NAK: from 192.168.0.254

Apr 21 17:47:29 server dhcpcd[1417]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' NAK

Apr 21 17:47:29 server dhcpcd[1417]: eth0: soliciting a DHCP lease

Apr 21 17:47:29 server dhcpcd[1417]: eth0: sending DISCOVER (xid 0xcebf097), next in 3.2 seconds

Apr 21 17:47:29 server dhcpcd[1417]: eth0: offered 192.168.0.103 from 192.168.0.254

Apr 21 17:47:29 server dhcpcd[1417]: eth0: sending REQUEST (xid 0xcebf097), next in 3.9 seconds

Apr 21 17:47:29 server dhcpcd[1417]: eth0: ignoring offer of 192.168.0.103 from 192.168.0.254

Apr 21 17:47:29 server dhcpcd[1417]: eth0: acknowledged 192.168.0.103 from 192.168.0.254

Apr 21 17:47:29 server dhcpcd[1417]: eth0: probing for 192.168.0.103

Apr 21 17:47:29 server dhcpcd[1417]: eth0: ARP probing 192.168.0.103 (1 of 3), next in 1.7 seconds

Apr 21 17:47:29 server dhcpcd[1417]: eth0: ignoring offer of 192.168.1.3 from 192.168.1.1

Apr 21 17:47:31 server dhcpcd[1417]: eth0: ARP probing 192.168.0.103 (2 of 3), next in 1.1 seconds

Apr 21 17:47:31 server dhcpcd[1417]: eth0: ARP probing 192.168.1.3 (3 of 3), next in 2.0 seconds

Apr 21 17:47:32 server dhcpcd[1417]: eth0: ARP probing 192.168.0.103 (3 of 3), next in 2.0 seconds

Apr 21 17:47:33 server dhcpcd[1417]: eth0: leased 192.168.0.103 for 60 seconds

Apr 21 17:47:33 server dhcpcd[1417]: eth0: renew in 30 seconds, rebind in 52 seconds

Apr 21 17:47:33 server dhcpcd[1417]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'

Apr 21 17:47:33 server dhcpcd[1417]: eth0: adding IP address 192.168.0.103/24

Apr 21 17:47:33 server dhcpcd[1417]: eth0: adding route to 192.168.0.0/24

Apr 21 17:47:33 server dhcpcd[1417]: eth0: adding default route via 192.168.0.254

Apr 21 17:47:33 server dhcpcd[1417]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' BOUND

Apr 21 17:47:33 server dhcpcd[1417]: forking to background

Apr 21 17:47:33 server dhcpcd[1464]: eth0: ARP announcing 192.168.1.3 (1 of 2), next in 2.0 seconds

Apr 21 17:47:33 server dhcpcd[1417]: forked to background, child pid 1464

 

Can someone please provide some assistance in helping me resolve this issue? Thank you in advance.

syslog20160421.txt

It looks like you have another device on your network at 192.168.0.254 that is acting as a DHCP server and trying to hand out an IP to your UnRaid server (192.168.0.103)

I would find this device and either get it off your network or turn off the DHCP server on it. You should be able to connect to it via a web browser at 192.168.0.254

Have you put any new devices on your network, all in one printer wireless router?

  • Author

Thank you very much ashman70.  It was indeed another device on the network.  A TP-Link wireless repeater.  Weird, it has never caused an issue before.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.