sending DHCP_REQUEST every half hour, why please

glorsplitz · 11-30-2007, 11:14 PM

my networking skill is light

comcast isp, cable modem connected to linux pc

I have USE_DHCP[0]="yes" for eth0 in /etc/rc.d/rc.inet1.conf

in /var/log/debug the past few days I've been getting the following every half hour

Nov 30 23:04:40 dhcpcd[73]: sending DHCP_REQUEST for xx.xxx.xxx.xxx to xx.xx.xx.xx
Nov 30 23:04:40 dhcpcd[73]: dhcpIPaddrLeaseTime=3600 in DHCP server response.
Nov 30 23:04:40 dhcpcd[73]: dhcpT1value is missing in DHCP server response. Assuming 1800 sec
Nov 30 23:04:40 dhcpcd[73]: dhcpT2value is missing in DHCP server response. Assuming 3150 sec
Nov 30 23:04:40 dhcpcd[73]: DHCP_ACK received from (xx.xx.xx.xx)

it was never like this before, internet is working ok, I know internet and cable was messed up a couple days ago, seems like comcast may have been doing some network upgrades/maintenance

thank you

MQMan · 12-01-2007, 02:43 AM

Quote:

Originally Posted by glorsplitz

seems like comcast may have been doing some network upgrades/maintenance

Yep.

If you look at the lease Comcast is giving you, it's 3600 seconds, or 1 hour. The way DHCP works, is that the client will try and renew the lease half way through it's life, which is the 30 minutes you're seeing.

I'd guess Comcast are planning on making some network changes, and want to keep the leases short while they are doing that, to reduce any outages when they make the change. If they changed the network, and you had a 4 day lease, you might be "dead" for up to 2 days, until you're client tried to renew. At the moment, the most you'd be out is 30 minutes.

Nothing to really worry about. Unless they "accidentally" cut the cable. LOL

Cheers.

glorsplitz · 12-01-2007, 03:02 PM

thanks for your help MQMan

I connected xp box, did obtain, got same dhcp/dns ip addresses as linux box, lease time for 1 hour

I know I didn't changed anything, was hoping it was something comcastic

glorsplitz · 12-04-2007, 09:11 PM

follow up, dhcp requests are back to normal

Dec 3 23:06:29 dhcpcd[73]: sending DHCP_REQUEST for xx.xx.xx.xx to xx.xx.xx.xx
Dec 3 23:06:29 dhcpcd[73]: dhcpIPaddrLeaseTime=3600 in DHCP server response.
Dec 3 23:06:29 dhcpcd[73]: dhcpT1value is missing in DHCP server response. Assuming 1800 sec
Dec 3 23:06:29 dhcpcd[73]: dhcpT2value is missing in DHCP server response. Assuming 3150 sec
Dec 3 23:06:29 dhcpcd[73]: DHCP_ACK received from (xx.xx.xx.xx)
Dec 3 23:36:29 dhcpcd[73]: sending DHCP_REQUEST for xx.xx.xx.xx to xx.xx.xx.xx
Dec 3 23:36:29 dhcpcd[73]: dhcpIPaddrLeaseTime=7200 in DHCP server response.
Dec 3 23:36:29 dhcpcd[73]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec
Dec 3 23:36:29 dhcpcd[73]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec
Dec 3 23:36:29 dhcpcd[73]: DHCP_ACK received from (xx.xx.xx.xx)
Dec 4 00:36:29 dhcpcd[73]: sending DHCP_REQUEST for xx.xx.xx.xx to xx.xx.xx.xx
Dec 4 00:36:29 dhcpcd[73]: dhcpIPaddrLeaseTime=345600 in DHCP server response.
Dec 4 00:36:29 dhcpcd[73]: dhcpT1value is missing in DHCP server response. Assuming 172800 sec
Dec 4 00:36:29 dhcpcd[73]: dhcpT2value is missing in DHCP server response. Assuming 302400 sec
Dec 4 00:36:29 dhcpcd[73]: DHCP_ACK received from (xx.xx.xx.xx)