Date: Mon, 17 May 1999 14:16:49 -0400 (EDT) From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: dan@dpcsys.com (Dan Busarow) Cc: insane@lunatic.oneinsane.net, freebsd-questions@FreeBSD.ORG Subject: Re: Cox @Home and FreeBSD Message-ID: <199905171816.OAA29345@cc942873-a.ewndsr1.nj.home.com> In-Reply-To: <Pine.BSF.3.96.990517093518.7542B-100000@java.dpcsys.com> from Dan Busarow at "May 17, 99 09:37:18 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Busarow wrote, > On Mon, 17 May 1999, Ron 'The InSaNe One' Rosson wrote: > > I have been working on getting FreeBSD to use Cox @Home's Cable modem > > service. I have configured the box to use isc-dhcp2 like most of the > > FreeBSD links say to. The only issue is that it seems that they are all > > using Road Runner or equivalents. So with that said what is the equivalent > > off the rrlogin program for Cox @HOME? > > Cox doesn't use a login. > > I never tried real hard to get DHCP working on my home PC, I just entered > the IP address that windows was assigned and used that. > > I've had the same IP address since we started the service about a year > ago. As another data point about coax cable IS, I have Comcast @Home, and we have static IPs at my location. No DHCP at all. This is not true of all Comcast @Home locations. It might vary with location for Cox as well. The service might not bother to deal with DHCP while ( subscriber_base < number_IPs ) in the local network. This could of course change. You really need to find out what protocol you are or are not using from your provider or from the setup on your other, supported OS. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905171816.OAA29345>