Date: Tue, 17 Jun 2003 14:41:19 -0500 From: sweetleaf <sweetleaf@myrealbox.com> To: "Derrick Ryalls" <ryallsd@datasphereweb.com> Cc: questions@freebsd.org Subject: Re: television cable internet service Message-ID: <20030617144119.0aebf7db.sweetleaf@myrealbox.com> In-Reply-To: <009e01c334fa$0bde1d00$0200a8c0@bartxp> References: <OF5334D70F.8A3ED68C-ON88256D48.005F1417@dot.ca.gov> <009e01c334fa$0bde1d00$0200a8c0@bartxp>
next in thread | previous in thread | raw e-mail | index | archive | help
I am using openbsd on comcast. Like some other, i too had a windows box ready for the technician,with a nic already there, once he was able to get a live connection and left i just switched to my openbsd/pf router. There is some stuff you need to do, such as punching a hole through your filter to allow the router itsealf to broadcast bootp request and accept them from the comcast dhcp server. Change your /etc/resolv.conf to include the comcast dns server or other internet root servers. set the nic going to the cable modem to use dhcp. good luck. On Tue, 17 Jun 2003 10:58:18 -0700 "Derrick Ryalls" <ryallsd@datasphereweb.com> wrote: > > Greetings fellow B.S.D. enthusiasts. Recently, I requested > > installation > > of a television cable at my home in Sacramento, California. > > The cable operator is Comcast. I requested connection of the > > television cable to my computer, which is a service that the > > operator advertises profusely. The telephone sales > > representative assured me that all things are possible, > > including both a Unix operating system, and an in-house > > L.A.N. The installation technician spent some time > > installing the cable, then attached it through a Motorola > > DOCSYS modem to the NIC board on the computer. The computer > > saw the cable network, but the cable refused to accept a > > To make life easy, I had a windows box laying around for the technician > to verify a live line with. Once it was live and he was gone, I > switched to using a BSD router on the connection. > > > logon request from the computer. The technician said that he > > believed that neither B.S.D. nor any other Unix, nor any > > Microsoft product that could be programmed to act as a server > > was acceptable. Has any other person had the same problem? > > Yeah, they are paranoid about servers, but never do anything about them > until it starts to cost them money. If they were really strict on the > no servers policy, they would be able to allow any windows box to > connect to their network. > > > How did you solve it? If I insist on a B.S.D. connection, > > how do I locate a B.S.D. friendly internet service provider > > in Sacramento? If I insist on B.S.D., am I confined to a 56 > > kb Hayes-type telephone modem? Any comments or advice is > > appreciated. Lee_Shackelford@dot.ca.gov > > > > BSD should work fine with Comcast. I am not sure how comcast in your > area differs from the seattle area, but they should all be BSD friendly. > The big trouble is that initial service with cable/dsl is rather flaky. > It usually takes the ISP a month or so to figure out how a network is to > be expanded or something. > > In any case, step 1 is to verify connection. Try going to this website: > > http://192.168.100.1 which is commonly cable modem's ips. > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030617144119.0aebf7db.sweetleaf>