Paul,
I did have a (rented) LANcity modem initially ( which, I was told, was which
built by a car stereo company!), but Cox replaced it with a Toshiba modem
after _many_ problems with the LANcity boat anchor. After a few months with
the Toshiba, I bought one and turned theirs back in. I was running with a
fixed IP address at that point, but a few months later, they told me I had
to switch to dhcp. After I tracked down a version of Matterhorn that
supported dhcp, I downloaded it, added my local mods and all was well.
We were moved to a new subnet when we went from the LANcity to the Toshiba,
but not when we went from a rented Toshiba to a purchased one. Since going
to dhcp (vs. fixed IP) we've only changed IP addresses once (I keep a
history file that shows all changes). In fact, the initial IP lease was for
the same fixed address we had previously!
Not sure if there's any conclusions that can be drwan, but it's sure nice to
have found some folks with similar/related experiences to bounce ideas off
of.
--Bob
----- Original Message -----
From: Paul M. Wright, Jr. <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, June 16, 2001 3:00 PM
Subject: LEAF posting re: DHCP client
> Bob -
>
> I've been following your posts to the LEAF mailing list about the DHCP
> problems you had. I also use an LRP router with an @Home cable connection
> in the Phoenix area so I thought I would share my experience and
suspicions.
>
> I first got my @Home cable modem in April of 1999 using a rented LANCity
> cable modem. I implemented an LRP router with no problem once I figured
out
> that you had to configure the DHCP client to send the hostname in order to
> receive an IP. For about the first year and a half, the system was really
> quite stable but then I began having problems with connectivity that were
> fixed (several times) by having Cox "re-provision" the circuit. By the
time
> the standards-compliant Motorola and Toshiba cable modems were released
late
> last Fall, I was convinced that the modem was part of the problem so I
> purchased a Motorola cable modem. When I called Cox to get the circuit
> re-provisioned for the new modem and make arrangements to turn in the
rented
> cable modem, the technician shared the information that they were having a
> fair amount of problems with the LANCity modems and inferred that they had
> sequestered them on a few subnets because the problems were DHCP-related.
> Sure enough, the subnet of my connection had changed when I brought the
> circuit back up with the new modem (but DHCP was still being served by the
> same server and, in fact, is the same server from which you receive your
IP
> lease).
>
> Since the technician told me that as the numbers of modems of each type
> changed they would change the subnets, my suspicion is that what happened
> is that the DHCP scope for your subnet was re-configured from the
"LANCity"
> configuration to that supporting the new modems and that the change was
just
> enough to cause problems for the version of the DHCP client you were
using.
>
> It's just a theory and whether you will ever be able to get anyone to
> confirm or deny that...
>
>
> paul
>
> Paul M. Wright, Jr. MCSE, CCNA, CNE
> McKay Technologies
> "making technology play nice...."
> Mesa, AZ
>
>
>
>
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-user
