[NCLUG] dhcp and @home

[Chris Wolney]

Same here.  A month or so after I had @home installed, I installed a Linksys
BEFSR41 in between my machines and the cable modem, and didn't have any
problems.  Just had to set the hostname of the Linksys to match the
"c-xxxxxx" number that was on on my work order.  Before I did that, my home
network was an island.

-Chris

----- Original Message -----
From: "Daniel Herrington" <daniel.herrington at home.com>
To: <nclug at nclug.org>
Sent: Friday, March 16, 2001 9:59 AM
Subject: Re: [NCLUG] dhcp and @home


> I don't think this is the case with @ Home, because when they
> installed my cable modem, they installed it directly to my Windows
> box.  After they left, I switched the cable modem connection to my
> Coyote Linux box, with DHCP, and saw no problems.
>
> Daniel
>
>
>
> => Replying to J. Paul Reed's message, "Re: [NCLUG] dhcp and @home" (Mar
16):
>  > On Fri, 16 Mar 2001, Charles Clarke wrote:
>  > Out of curiousity, does @home know or care anything about your ethernet
>  > card's MAC address?
>  >
>  > Charter Communications cable modem service actually binds to the MAC
>  > address of the first ethernet card it hears chiming in on the
network...
>  > you have to call the NOC to get them to reset it.
> _______________________________________________
> NCLUG mailing list
> NCLUG at nclug.org
> http://www.nclug.org/mailman/listinfo/nclug
>