Comcast: Changing ip's

[David A. Bandel]

On Sun, 7 Jul 2002 22:44:39 -0400
begin  Joel Hammer <Joel at hammershome.com> spewed forth:

> Just to share a frustrating experience and maybe gather enthusiasm for a
> class action lawsuit or something.

Don't think you have anything that will hold water in court.

[snip]

> I used dhcpcd to get my dynamically assigned ip address. The last time
> (in fact every time) I have gotten an address from comcast, the lease
> has been infinite, at least I think that a lease time of:
> 
> LEASETIME=4294967295
> RENEWALTIME=259200
> REBINDTIME=3758096383
> 
> is infinite in the unix world.
> 
> As a result, dhcpcd, instead of starting and staying a daemon, watching
> for the server to reassign the number, always exits after getting this
> lease time, saying that the lease was infinite, and so why bother
> running.
> 

Well, I use dhclient (but I've also used dhcpxd with similar results), and
mine doesn't exit even though my lease runs until 19 Jan 2038 (rebind 2
Feb 2011):
(extract from /var/lib/dhcp/dhclient.leases):
  option domain-name "cwpanama.net";
  renew 2 2038/1/19 03:14:07;
  rebind 0 2011/1/2 22:07:11;
  expire 2 2038/1/19 03:14:07;


 2016 ?        S      0:00 /sbin/dhclient eth1

[david at tole dhcp]$ uptime
  6:04am  up 36 days, 14:02, 12 users,  load average: 0.00, 0.01, 0.00

so dhclient has been running for 36 days faithfully counting down.

I had a long lease in January, but C&W changed all the dynamic IPs.  Mine
changed too.

I suggest you change dhcp clients.  dhcpcd is known to have problems,
looks like you found one of them.

Ciao,

David A. Bandel
-- 
Focus on the dream, not the competition.
		-- Nemesis Racing Team motto