spinbot Posted January 6, 2011 Share Posted January 6, 2011 Every 12 hours there is an entry in my syslogs like below. My networking skills are so-so. I am running a custom firmware ( Tomato-MLPPP ) and the DHCP range is set as: 192.168.1.100 - 192.168.1.149 Would the best option be to just statically assign my server to 192.168.1.67 and 255.255.255.0 for subnet and 192.168.1.1 for gateway and DNS server? Jan 1 00:45:11 Tower dhcpcd[1476]: sending DHCP_REQUEST for 192.168.1.67 to 192.168.1.254 Jan 1 00:45:11 Tower dhcpcd[1476]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 1 00:45:11 Tower dhcpcd[1476]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 1 00:45:11 Tower dhcpcd[1476]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 1 00:45:11 Tower dhcpcd[1476]: DHCP_ACK received from (192.168.1.254) Jan 1 12:45:11 Tower dhcpcd[1476]: sending DHCP_REQUEST for 192.168.1.67 to 192.168.1.254 Jan 1 12:45:11 Tower dhcpcd[1476]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 1 12:45:11 Tower dhcpcd[1476]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 1 12:45:11 Tower dhcpcd[1476]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 1 12:45:11 Tower dhcpcd[1476]: DHCP_ACK received from (192.168.1.254) Jan 2 00:45:11 Tower dhcpcd[1476]: sending DHCP_REQUEST for 192.168.1.67 to 192.168.1.254 Jan 2 00:45:11 Tower dhcpcd[1476]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 2 00:45:11 Tower dhcpcd[1476]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 2 00:45:11 Tower dhcpcd[1476]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 2 00:45:11 Tower dhcpcd[1476]: DHCP_ACK received from (192.168.1.254) Jan 2 12:45:12 Tower dhcpcd[1476]: sending DHCP_REQUEST for 192.168.1.67 to 192.168.1.254 Jan 2 12:45:12 Tower dhcpcd[1476]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 2 12:45:12 Tower dhcpcd[1476]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 2 12:45:12 Tower dhcpcd[1476]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 2 12:45:12 Tower dhcpcd[1476]: DHCP_ACK received from (192.168.1.254) Jan 2 15:24:28 Tower kernel: mdcmd (188157): spindown 2 Jan 2 15:59:01 Tower kernel: mdcmd (188365): spindown 0 Jan 2 16:18:08 Tower kernel: mdcmd (188479): spindown 0 Jan 2 16:24:48 Tower kernel: mdcmd (188520): spindown 1 Jan 2 16:24:49 Tower kernel: mdcmd (188521): spindown 6 Jan 2 16:24:49 Tower kernel: mdcmd (188522): spindown 7 Jan 2 16:24:49 Tower kernel: mdcmd (188523): spindown 8 Jan 2 16:24:50 Tower kernel: mdcmd (188524): spindown 9 Jan 2 16:48:44 Tower kernel: mdcmd (188670): spindown 5 Jan 2 16:50:35 Tower kernel: mdcmd (188686): spindown 0 Jan 2 17:00:15 Tower kernel: mdcmd (188745): spindown 1 Jan 2 17:00:16 Tower kernel: mdcmd (188746): spindown 6 Jan 2 17:00:16 Tower kernel: mdcmd (188747): spindown 7 Jan 2 17:00:16 Tower kernel: mdcmd (188748): spindown 8 Jan 2 17:00:17 Tower kernel: mdcmd (188749): spindown 9 Jan 2 18:31:51 Tower kernel: mdcmd (189328): spindown 0 Jan 2 18:41:22 Tower kernel: mdcmd (189386): spindown 1 Jan 2 18:41:23 Tower kernel: mdcmd (189387): spindown 6 Jan 2 18:41:23 Tower kernel: mdcmd (189388): spindown 7 Jan 2 18:41:23 Tower kernel: mdcmd (189389): spindown 8 Jan 2 18:41:24 Tower kernel: mdcmd (189390): spindown 9 Jan 2 21:32:51 Tower kernel: mdcmd (190418): spindown 1 Jan 2 21:32:52 Tower kernel: mdcmd (190419): spindown 6 Jan 2 21:32:52 Tower kernel: mdcmd (190420): spindown 7 Jan 2 21:32:52 Tower kernel: mdcmd (190421): spindown 8 Jan 2 21:32:53 Tower kernel: mdcmd (190422): spindown 9 Jan 2 22:28:52 Tower kernel: mdcmd (190758): spindown 1 Jan 2 22:28:53 Tower kernel: mdcmd (190759): spindown 6 Jan 2 22:28:53 Tower kernel: mdcmd (190760): spindown 7 Jan 2 22:28:53 Tower kernel: mdcmd (190761): spindown 8 Jan 2 22:28:54 Tower kernel: mdcmd (190762): spindown 9 Jan 2 23:07:00 Tower kernel: mdcmd (190991): spindown 0 Jan 2 23:07:00 Tower kernel: mdcmd (190992): spindown 1 Jan 2 23:07:01 Tower kernel: mdcmd (190993): spindown 6 Jan 2 23:07:01 Tower kernel: mdcmd (190994): spindown 7 Jan 2 23:07:01 Tower kernel: mdcmd (190995): spindown 8 Jan 2 23:07:02 Tower kernel: mdcmd (190996): spindown 9 Jan 3 00:45:12 Tower dhcpcd[1476]: sending DHCP_REQUEST for 192.168.1.67 to 192.168.1.254 Jan 3 00:45:12 Tower dhcpcd[1476]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 3 00:45:12 Tower dhcpcd[1476]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 3 00:45:12 Tower dhcpcd[1476]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 3 00:45:12 Tower dhcpcd[1476]: DHCP_ACK received from (192.168.1.254) Jan 3 12:45:12 Tower dhcpcd[1476]: sending DHCP_REQUEST for 192.168.1.67 to 192.168.1.254 Jan 3 12:45:12 Tower dhcpcd[1476]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 3 12:45:12 Tower dhcpcd[1476]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 3 12:45:12 Tower dhcpcd[1476]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 3 12:45:12 Tower dhcpcd[1476]: DHCP_ACK received from (192.168.1.254) Jan 3 22:16:27 Tower kernel: mdcmd (199322): spindown 0 Jan 3 22:16:27 Tower kernel: mdcmd (199323): spindown 1 Jan 3 22:16:28 Tower kernel: mdcmd (199324): spindown 6 Jan 3 22:16:28 Tower kernel: mdcmd (199325): spindown 7 Jan 3 22:16:28 Tower kernel: mdcmd (199326): spindown 8 Jan 3 22:16:28 Tower kernel: mdcmd (199327): spindown 9 Jan 3 22:39:40 Tower kernel: mdcmd (199466): spindown 0 Jan 3 22:39:40 Tower kernel: mdcmd (199467): spindown 1 Jan 3 22:39:41 Tower kernel: mdcmd (199468): spindown 6 Jan 3 22:39:41 Tower kernel: mdcmd (199469): spindown 7 Jan 3 22:39:41 Tower kernel: mdcmd (199470): spindown 8 Jan 3 22:39:42 Tower kernel: mdcmd (199471): spindown 9 Jan 4 00:45:12 Tower dhcpcd[1476]: sending DHCP_REQUEST for 192.168.1.67 to 192.168.1.254 Jan 4 00:45:12 Tower dhcpcd[1476]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 4 00:45:12 Tower dhcpcd[1476]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 4 00:45:12 Tower dhcpcd[1476]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 4 00:45:12 Tower dhcpcd[1476]: DHCP_ACK received from (192.168.1.254) Jan 4 12:45:12 Tower dhcpcd[1476]: sending DHCP_REQUEST for 192.168.1.67 to 192.168.1.254 Jan 4 12:45:12 Tower dhcpcd[1476]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 4 12:45:12 Tower dhcpcd[1476]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 4 12:45:12 Tower dhcpcd[1476]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 4 12:45:12 Tower dhcpcd[1476]: DHCP_ACK received from (192.168.1.254) Jan 4 17:30:30 Tower kernel: mdcmd (206247): spindown 0 Jan 4 17:39:30 Tower kernel: mdcmd (206302): spindown 1 Jan 4 17:39:31 Tower kernel: mdcmd (206303): spindown 6 Jan 4 17:39:31 Tower kernel: mdcmd (206304): spindown 7 Jan 4 17:39:31 Tower kernel: mdcmd (206305): spindown 8 Jan 4 17:39:32 Tower kernel: mdcmd (206306): spindown 9 Jan 4 21:00:38 Tower kernel: mdcmd (207511): spindown 1 Jan 4 21:00:39 Tower kernel: mdcmd (207512): spindown 6 Jan 4 21:00:39 Tower kernel: mdcmd (207513): spindown 7 Jan 4 21:00:39 Tower kernel: mdcmd (207514): spindown 8 Jan 4 21:00:40 Tower kernel: mdcmd (207515): spindown 9 Jan 4 21:27:45 Tower kernel: mdcmd (207678): spindown 0 Jan 4 21:43:17 Tower kernel: mdcmd (207772): spindown 1 Jan 4 21:43:17 Tower kernel: mdcmd (207773): spindown 6 Jan 4 21:43:17 Tower kernel: mdcmd (207774): spindown 7 Jan 4 21:43:17 Tower kernel: mdcmd (207775): spindown 8 Jan 4 21:43:18 Tower kernel: mdcmd (207776): spindown 9 Jan 4 22:19:36 Tower kernel: mdcmd (207994): spindown 1 Jan 4 22:19:37 Tower kernel: mdcmd (207995): spindown 6 Jan 4 22:19:37 Tower kernel: mdcmd (207996): spindown 7 Jan 4 22:19:37 Tower kernel: mdcmd (207997): spindown 8 Jan 4 22:19:38 Tower kernel: mdcmd (207998): spindown 9 Jan 4 22:33:50 Tower kernel: mdcmd (208084): spindown 0 Jan 4 22:33:50 Tower kernel: mdcmd (208085): spindown 3 Jan 5 00:45:12 Tower dhcpcd[1476]: sending DHCP_REQUEST for 192.168.1.67 to 192.168.1.254 Jan 5 00:45:12 Tower dhcpcd[1476]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 5 00:45:12 Tower dhcpcd[1476]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 5 00:45:12 Tower dhcpcd[1476]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 5 00:45:12 Tower dhcpcd[1476]: DHCP_ACK received from (192.168.1.254) Jan 5 05:06:05 Tower apcupsd[1738]: UPS Self Test switch to battery. Jan 5 05:06:13 Tower apcupsd[1738]: UPS Self Test completed: Not supported Jan 5 05:09:15 Tower kernel: mdcmd (210455): spindown 0 Jan 5 05:09:15 Tower kernel: mdcmd (210456): spindown 1 Jan 5 05:09:16 Tower kernel: mdcmd (210457): spindown 6 Jan 5 05:09:16 Tower kernel: mdcmd (210458): spindown 7 Jan 5 05:09:16 Tower kernel: mdcmd (210459): spindown 8 Jan 5 05:09:17 Tower kernel: mdcmd (210460): spindown 9 Jan 5 12:45:12 Tower dhcpcd[1476]: sending DHCP_REQUEST for 192.168.1.67 to 192.168.1.254 Jan 5 12:45:12 Tower dhcpcd[1476]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 5 12:45:12 Tower dhcpcd[1476]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 5 12:45:12 Tower dhcpcd[1476]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 5 12:45:12 Tower dhcpcd[1476]: DHCP_ACK received from (192.168.1.254) Link to comment
kizer Posted January 6, 2011 Share Posted January 6, 2011 I didn't read thru the log much, but I always go static simply because I like to know the exact address of any of my servers if I need to trouble shoot. Link to comment
joshpond Posted January 6, 2011 Share Posted January 6, 2011 I generally set to static as well so that I always know what the server is. You can try to set the lease time on the router for longer and that may help if you want to leave it as DHCP. Also someone correct me if I'm wrong but the easiest is to have you DNS address the same as your router (which having a quick flash over seems to be 192.168.1.254) Josh Link to comment
opentoe Posted January 6, 2011 Share Posted January 6, 2011 No sense in playing around with computer/server addresses when you can just reserve an IP address in your router per MAC address. Link to comment
joe90 Posted January 6, 2011 Share Posted January 6, 2011 I have the same issue but I'm running Pfsense : Jan 5 07:16:16 Cube dhcpcd[16110]: DHCP_ACK received from (192.168.1.1) Jan 5 07:34:03 Cube kernel: mdcmd (29): spindown 0 Jan 5 08:16:15 Cube dhcpcd[16110]: sending DHCP_REQUEST for 192.168.1.2 to 192.168.1.1 Jan 5 08:16:15 Cube dhcpcd[16110]: dhcpIPaddrLeaseTime=7200 in DHCP server response. Jan 5 08:16:16 Cube dhcpcd[16110]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec Jan 5 08:16:16 Cube dhcpcd[16110]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec Jan 5 08:16:16 Cube dhcpcd[16110]: DHCP_ACK received from (192.168.1.1) Jan 5 09:16:15 Cube dhcpcd[16110]: sending DHCP_REQUEST for 192.168.1.2 to 192.168.1.1 Jan 5 09:16:16 Cube dhcpcd[16110]: dhcpIPaddrLeaseTime=7200 in DHCP server response. Jan 5 09:16:16 Cube dhcpcd[16110]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec Jan 5 09:16:16 Cube dhcpcd[16110]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec Jan 5 09:16:16 Cube dhcpcd[16110]: DHCP_ACK received from (192.168.1.1) Jan 5 10:16:15 Cube dhcpcd[16110]: sending DHCP_REQUEST for 192.168.1.2 to 192.168.1.1 Jan 5 10:16:16 Cube dhcpcd[16110]: dhcpIPaddrLeaseTime=7200 in DHCP server response. Jan 5 10:16:16 Cube dhcpcd[16110]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec Jan 5 10:16:16 Cube dhcpcd[16110]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec Jan 5 10:16:16 Cube dhcpcd[16110]: DHCP_ACK received from (192.168.1.1) Jan 5 11:16:15 Cube dhcpcd[16110]: sending DHCP_REQUEST for 192.168.1.2 to 192.168.1.1 Jan 5 11:16:16 Cube dhcpcd[16110]: dhcpIPaddrLeaseTime=7200 in DHCP server response. Jan 5 11:16:16 Cube dhcpcd[16110]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec Jan 5 11:16:16 Cube dhcpcd[16110]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec Jan 5 11:16:16 Cube dhcpcd[16110]: DHCP_ACK received from (192.168.1.1) Jan 5 12:16:16 Cube dhcpcd[16110]: sending DHCP_REQUEST for 192.168.1.2 to 192.168.1.1 Jan 5 12:16:16 Cube dhcpcd[16110]: dhcpIPaddrLeaseTime=7200 in DHCP server response. Jan 5 12:16:16 Cube dhcpcd[16110]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec Jan 5 12:16:16 Cube dhcpcd[16110]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec Jan 5 12:16:16 Cube dhcpcd[16110]: DHCP_ACK received from (192.168.1.1) Jan 5 13:16:16 Cube dhcpcd[16110]: sending DHCP_REQUEST for 192.168.1.2 to 192.168.1.1 Jan 5 13:16:16 Cube dhcpcd[16110]: dhcpIPaddrLeaseTime=7200 in DHCP server response. Jan 5 13:16:16 Cube dhcpcd[16110]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec Jan 5 13:16:16 Cube dhcpcd[16110]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec Jan 5 13:16:16 Cube dhcpcd[16110]: DHCP_ACK received from (192.168.1.1) Jan 5 14:16:16 Cube dhcpcd[16110]: sending DHCP_REQUEST for 192.168.1.2 to 192.168.1.1 Jan 5 14:16:16 Cube dhcpcd[16110]: dhcpIPaddrLeaseTime=7200 in DHCP server response. Jan 5 14:16:16 Cube dhcpcd[16110]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec Jan 5 14:16:16 Cube dhcpcd[16110]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec Jan 5 14:16:16 Cube dhcpcd[16110]: DHCP_ACK received from (192.168.1.1) Jan 5 14:18:49 Cube kernel: mdcmd (30): spindown 6 Jan 5 15:16:16 Cube dhcpcd[16110]: sending DHCP_REQUEST for 192.168.1.2 to 192.168.1.1 Jan 5 15:16:16 Cube dhcpcd[16110]: dhcpIPaddrLeaseTime=7200 in DHCP server response. Jan 5 15:16:16 Cube dhcpcd[16110]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec Jan 5 15:16:16 Cube dhcpcd[16110]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec Jan 5 15:16:16 Cube dhcpcd[16110]: DHCP_ACK received from (192.168.1.1) Jan 5 16:07:47 Cube kernel: mdcmd (31): spindown 0 Jan 5 16:16:16 Cube dhcpcd[16110]: sending DHCP_REQUEST for 192.168.1.2 to 192.168.1.1 Jan 5 16:16:16 Cube dhcpcd[16110]: dhcpIPaddrLeaseTime=7200 in DHCP server response. Jan 5 16:16:16 Cube dhcpcd[16110]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec Jan 5 16:16:16 Cube dhcpcd[16110]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec Jan 5 16:16:16 Cube dhcpcd[16110]: DHCP_ACK received from (192.168.1.1) Jan 5 17:16:16 Cube dhcpcd[16110]: sending DHCP_REQUEST for 192.168.1.2 to 192.168.1.1 Jan 5 17:16:16 Cube dhcpcd[16110]: dhcpIPaddrLeaseTime=7200 in DHCP server response. Jan 5 17:16:16 Cube dhcpcd[16110]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec Jan 5 17:16:16 Cube dhcpcd[16110]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec Jan 5 17:16:16 Cube dhcpcd[16110]: DHCP_ACK received from (192.168.1.1) Jan 5 18:16:16 Cube dhcpcd[16110]: sending DHCP_REQUEST for 192.168.1.2 to 192.168.1.1 Jan 5 18:16:16 Cube dhcpcd[16110]: dhcpIPaddrLeaseTime=7200 in DHCP server response. Jan 5 18:16:16 Cube dhcpcd[16110]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec Jan 5 18:16:16 Cube dhcpcd[16110]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec Jan 5 18:16:16 Cube dhcpcd[16110]: DHCP_ACK received from (192.168.1.1) Link to comment
spinbot Posted January 6, 2011 Author Share Posted January 6, 2011 If I know my router hands out DHCP from 192.168.1.100 - 192.168.1.149 , is it even necessary to reserve IP's by MAC address or is the easiest way to be just selecting Static IP's from 192.168.1.150 and higher? My router IP is 192.168.1.1 , so I would set that as my gateway and dns I believe. Link to comment
dgaschk Posted January 6, 2011 Share Posted January 6, 2011 If I know my router hands out DHCP from 192.168.1.100 - 192.168.1.149 , is it even necessary to reserve IP's by MAC address or is the easiest way to be just selecting Static IP's from 192.168.1.150 and higher? My router IP is 192.168.1.1 , so I would set that as my gateway and dns I believe. As long as your router has a subnet mask of 255.255.255.0 you can use any address in 192.168.1.2 - 192.168.1.254. Except ones that are currently assigned by your router. If you assign one in 192.168.1.100 - 192.168.1.149 your router will not use it. You can be certain that your not using an assigned address by not using 192.168.1.100 - 192.168.1.149. 255.255.255.0 should be the default subnet mask in your router. So, yes. Yes, use 192.168.1.1 as gateway and dns. Also add 192.168.1.1 as the first ntp server if your router proxies ntp. I found it slightly easier to configure a static address by reserving it in my router and leaving unRaid set to auto except for the ntp addition. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.