dvap Posted August 20, 2015 Share Posted August 20, 2015 I upgraded to 6rc2 and things were working fine for awhile. I set up a few dockers. Did a few other things and now I cannot access tower via browser or telnet. it appears to be a networking problem. -it gets a lease from the router, i can see it get assigned (192.168.2.22) -i can't ping or telnet to unraid. attached is my syslog. -same result booting in safe mode. any ideas? i am sure it is something dumb. thx in advance for any advice. syslog.txt Link to comment
timz Posted August 20, 2015 Share Posted August 20, 2015 How did you get the syslog? The http interface is working? Link to comment
dvap Posted August 20, 2015 Author Share Posted August 20, 2015 i got the syslog at the command line copied to the usb drive and manually moved to my laptop. attached is a photo of my ip config for eth0. the MAC address ending in e7 is the MAC address of the only ethernet port on my motherboard. and, the one apparently assigned 192.168.2.22 in the syslog. thx again. Link to comment
gubbgnutten Posted August 20, 2015 Share Posted August 20, 2015 As you can see from the picture, the IP address is not 192.168.2.22, but rather 192.168.81.235. Looking at the system log, it seems that you have two DHCP servers responding (192.168.2.1 and 192.168.81.1). In the end, the system decides to go with 192.168.81.235 rather than 192.168.2.22. If your router is 192.168.2.1, figure out what device 192.168.81.1 is and disable the DHCP server on that device (or move it to a separate network). Link to comment
dvap Posted August 21, 2015 Author Share Posted August 21, 2015 I see the repetitive DHCP activity below, but I don't understand what is causing it. - I only have one DHCP server. - All other devices on the network are able to connect and obtain IP addresses without a problem. - If I assign a manual IP address I can connect to Unraid (but then I have issues with my docker items). - I don't have a 192.168.81.XXX host network. - i don't understand where the 192.168.81.235 address is coming from. any additional insight or direction anyone can point me in? Thx! Aug 19 02:21:24 Tower dhcpcd[1390]: dhcpcd-6.8.1 starting Aug 19 02:21:24 Tower dhcpcd[1390]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' PREINIT Aug 19 02:21:24 Tower dhcpcd[1390]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER Aug 19 02:21:24 Tower dhcpcd[1390]: eth0: waiting for carrier Aug 19 02:21:24 Tower kernel: r8169 0000:03:00.0 eth0: link down Aug 19 02:21:24 Tower kernel: r8169 0000:03:00.0 eth0: link down Aug 19 02:21:28 Tower dhcpcd[1390]: eth0: carrier acquired Aug 19 02:21:28 Tower kernel: r8169 0000:03:00.0 eth0: link up Aug 19 02:21:28 Tower dhcpcd[1390]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' CARRIER Aug 19 02:21:28 Tower dhcpcd[1390]: eth0: delaying IPv4 for 0.8 seconds Aug 19 02:21:28 Tower dhcpcd[1390]: eth0: using ClientID 01:00:30:48:b3:0d:e7 Aug 19 02:21:28 Tower dhcpcd[1390]: eth0: soliciting a DHCP lease Aug 19 02:21:28 Tower dhcpcd[1390]: eth0: sending DISCOVER (xid 0x84312e40), next in 4.1 seconds Aug 19 02:21:32 Tower dhcpcd[1390]: eth0: sending DISCOVER (xid 0x84312e40), next in 7.8 seconds Aug 19 02:21:40 Tower dhcpcd[1390]: eth0: sending DISCOVER (xid 0x84312e40), next in 16.3 seconds Aug 19 02:21:41 Tower dhcpcd[1390]: eth0: offered 192.168.2.22 from 192.168.2.1 Aug 19 02:21:41 Tower dhcpcd[1390]: eth0: sending REQUEST (xid 0x84312e40), next in 3.8 seconds Aug 19 02:21:41 Tower dhcpcd[1390]: eth0: acknowledged 192.168.2.22 from 192.168.2.1 Aug 19 02:21:41 Tower dhcpcd[1390]: eth0: probing for 192.168.2.22 Aug 19 02:21:41 Tower dhcpcd[1390]: eth0: ARP probing 192.168.2.22 (1 of 3), next in 1.4 seconds Aug 19 02:21:42 Tower dhcpcd[1390]: eth0: ignoring offer of 192.168.81.235 from 192.168.81.1 Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: NAK: wrong server-ID from 192.168.81.1 Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: message: wrong server-ID Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' NAK Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: soliciting a DHCP lease Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: sending DISCOVER (xid 0x2d5e2f4d), next in 4.3 seconds Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: offered 192.168.2.22 from 192.168.2.1 Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: sending REQUEST (xid 0x2d5e2f4d), next in 5.0 seconds Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: ignoring offer of 192.168.81.235 from 192.168.81.1 Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: acknowledged 192.168.2.22 from 192.168.2.1 Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: probing for 192.168.2.22 Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: ARP probing 192.168.2.22 (1 of 3), next in 1.3 seconds Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: NAK: wrong server-ID from 192.168.81.1 Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: message: wrong server-ID Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' NAK Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: soliciting a DHCP lease Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: sending DISCOVER (xid 0xc7413751), next in 4.0 seconds Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: offered 192.168.81.235 from 192.168.81.1 Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: sending REQUEST (xid 0xc7413751), next in 3.3 seconds Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: ignoring offer of 192.168.2.22 from 192.168.2.1 Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: acknowledged 192.168.81.235 from 192.168.81.1 Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: probing for 192.168.81.235 Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: ARP probing 192.168.81.235 (1 of 3), next in 1.5 seconds Aug 19 02:21:43 Tower dhcpcd[1390]: eth0: ARP probing 192.168.2.22 (2 of 3), next in 1.8 seconds Aug 19 02:21:44 Tower dhcpcd[1390]: eth0: ARP probing 192.168.2.22 (2 of 3), next in 1.2 seconds Aug 19 02:21:44 Tower dhcpcd[1390]: eth0: ARP probing 192.168.81.235 (2 of 3), next in 1.4 seconds Aug 19 02:21:44 Tower dhcpcd[1390]: eth0: ARP probing 192.168.2.22 (3 of 3), next in 2.0 seconds Aug 19 02:21:45 Tower dhcpcd[1390]: eth0: ARP probing 192.168.2.22 (3 of 3), next in 2.0 seconds Aug 19 02:21:46 Tower dhcpcd[1390]: eth0: ARP probing 192.168.81.235 (3 of 3), next in 2.0 seconds Aug 19 02:21:46 Tower dhcpcd[1390]: eth0: leased 192.168.81.235 for 3600 seconds Aug 19 02:21:46 Tower dhcpcd[1390]: eth0: renew in 1800 seconds, rebind in 3150 seconds Aug 19 02:21:46 Tower dhcpcd[1390]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease' Aug 19 02:21:46 Tower dhcpcd[1390]: eth0: adding IP address 192.168.81.235/24 Aug 19 02:21:46 Tower dhcpcd[1390]: eth0: adding route to 192.168.81.0/24 Aug 19 02:21:46 Tower dhcpcd[1390]: eth0: adding default route via 192.168.81.1 Aug 19 02:21:46 Tower dhcpcd[1390]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' BOUND Aug 19 02:21:46 Tower dhcpcd[1390]: forking to background Aug 19 02:21:46 Tower dhcpcd[1447]: eth0: ARP announcing 192.168.2.22 (1 of 2), next in 2.0 seconds Aug 19 02:21:46 Tower dhcpcd[1390]: forked to background, child pid 1447 Link to comment
dvap Posted August 21, 2015 Author Share Posted August 21, 2015 also, here are my DHCP server settings. pretty straightforward. Link to comment
dvap Posted August 21, 2015 Author Share Posted August 21, 2015 My smart friend solved this for me. I didn't realize that the Vera Z-Wave had a DHCP server in it. Here is what he gave me and it solved the problem: So you must have another device with a DHCP server on the network that your server is connected. I’m guessing the odd dhcp server is 192.168.81.1 Which when I google around I see that a Vera Z-wave home automation device uses that IP as its default dhcp server. Do you have one of these devices? Link to comment
RobJ Posted August 21, 2015 Share Posted August 21, 2015 I think gubbgnutten is right. You have another machine on your network at 192.168.81.1 with a DHCP server and it's getting you to connect. You need to find that device! It's possible you are being attacked some how. Or a neighbor or driveby is connecting to your network, and setting up services. My next recommendation is to set a static IP - * Set Obtain IP address automatically to No * Set IP address to 192.168.2.22 (or whatever you want it to be) * Set Default gateway to 192.168.2.1 * etc Edit: I see you have figured it out, good. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.