From: Eric Rossiter (rossiter@discoverynet.com)
Date: 12/19/01


Message-ID: <3C20F613.BB46D876@discoverynet.com>
Date: Wed, 19 Dec 2001 14:17:47 -0600
From: Eric Rossiter <rossiter@discoverynet.com>
Subject: Re: @Home and DHCP

Brian Densmore wrote:
>
> Seasons Greetings all,
>
> Could someone tell me again how they did it?

Hello fellow tux-ites,

To my knowledge Comcast@Home authenticates by machine name. I was told
there are no static IP's, however, they must have machine names mapped
to IP's somewhere, because I have always gotten the same IP, no matter
what, Win or Lin, in over a year.

So, that said, this is how I make it work. Set the hostname to whatever
Comcast gave you, i.e., aa######-a (cb987654-a, for example.) I don't
set any other parameters, DNS, etc. I do enable DHCP for eth0.

You need to hack /sbin/ifup to make this work also.

In RH 6.x, you need to change the following line in /sbin/ifup

        if /sbin/pump -i $DEVICE; then

Change to:

        if /sbin/pump -i $DEVICE -h aa######-a; then

Where: aa######-a = your hostname (cb987654-a, for example.)

/sbin/ifup changed alot in RH 7.x and I haven't figured out the hack for
that yet. In 7.x eth0 init fails @ boot up, but after logging in I
issue "/sbin/pump -h aa######-a -i eth0" and I authenticate to @Home
fine, and get the same IP every time. If anyone figures out the hack
for /sbin/ifup in RH 7.x, PLEASE let me know, as logging into root and
using pump every time I boot into Linux gets old.

HTH & TIA,
Eric