From owner-freebsd-questions Tue Jun 11 14: 8:52 2002 Delivered-To: freebsd-questions@freebsd.org Received: from yertle.kciLink.com (yertle.kcilink.com [216.194.193.105]) by hub.freebsd.org (Postfix) with ESMTP id 4809D37B406 for ; Tue, 11 Jun 2002 14:08:32 -0700 (PDT) Received: by yertle.kciLink.com (Postfix, from userid 100) id E6E4A2178D; Tue, 11 Jun 2002 17:08:31 -0400 (EDT) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Vivek Khera To: freebsd-questions@freebsd.org Subject: Re: Help with Cox cable modem on FreeBSD 4.5 Newsgroups: ml.freebsd.questions References: <20020602125549.A16596@permanently.misplaced.net> X-Trace: lorax.kciLink.com 1023827245 8798 216.194.193.105 (11 Jun 2002 20:27:25 GMT) X-Complaints-To: daemon@kciLink.com X-Virus-Scanned: by AMaViS snapshot-20020517 (@kci) X-Razor-id: fe6989b26db8ee55715be17886e46a852474fbb5 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> "CD" == Chad Day writes: CD> Hello.. I have a COX cable modem (northern virginia), and I'm kind of stuck now. I've done a lot of reading of documentation about getting the cable modem to work, and some of it has helped.. but.. here's where I'm at now. Wrap your lines, man... Anyhow, perhaps a sideways solution would be to buy something like the Netgear RP114 "firewall". I use it with Comcast. Basically it does the DHCP talking to your cable modem, and supports your internal network via DHCP using 192.168.0.* addresses and NAT. You can port forward from it to your internal server if you need public inbound access. Look for best buy to have them on sale with rebates for as low as $40. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message