I have only been able to statically configure the @Home address in Linux.
In Windows, it works with either DHCP or static configuration. @Home's
address management and routing configuration is poorly done - I would
assume the reason being is too much demand for service, too few skilled
technicians to maintain the equipment and account information.
Another little-known factoid about @Home is that their address management
is so shallowly monitored, that if you statically configure the DHCP
address that they give you, you can pretty much stop paying for the
service and continue using the address. <i> NOT </i> that I have done
that, of course. :)
On Tue, 5 Oct 1999, Ken Wilson wrote:
> That is really too broad a statement to make about @Home's ip leasing.
> Here in Victoria @Home is provided through Shaw Cable. Their leases
> rotate on a 48 hour cycle. If your machine is not connected when your
> lease is automatically renewed you could quite possibly get a new ip.
> In fact, I have on 3 or 4 occasions already.
>
> Ken Wilson
> First Law of Optimisation: The speed of a non-working program is
> irrelevant
> (Steve Heller, 'Efficient C/C++ Programming')
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Tim Lewis
> Sent: Monday, October 04, 1999 11:10 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] Anyone been able to get their cable modems to
> work?
>
> <snip>
>
> As a matter of fact, when I setup my cable modem with @home, I was not
> required to use DHCP. They tell you you need it, but the tech who
> installed
> my modem said the use of DHCP was irrelevant, and told me to set a
> static
> IP. This is due to the fact that they re-lease the same IP address back
> to
> you every week.
>
> <snip>
>