From owner-freebsd-isp Mon Oct 18 4:49:33 1999 Delivered-To: freebsd-isp@freebsd.org Received: from bunker.noc.nl.demon.net (bunker.noc.nl.demon.net [194.159.72.217]) by hub.freebsd.org (Postfix) with ESMTP id 9F5D014C4F for ; Mon, 18 Oct 1999 04:49:30 -0700 (PDT) (envelope-from arjan@nl.demon.net) Received: from localhost (arjan@localhost) by bunker.noc.nl.demon.net (8.9.3/8.9.3) with ESMTP id NAA48354; Mon, 18 Oct 1999 13:54:03 +0200 (CEST) (envelope-from arjan@nl.demon.net) X-Authentication-Warning: bunker.noc.nl.demon.net: arjan owned process doing -bs Date: Mon, 18 Oct 1999 13:54:03 +0200 (CEST) From: Arjan van der Oest X-Sender: arjan@bunker.noc.nl.demon.net To: "Daniel O'Callaghan" Cc: freebsd-isp@freebsd.org Subject: Re: cable modems and FreeBSD In-Reply-To: Message-ID: X-no-archive: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 18 Oct 1999, Daniel O'Callaghan wrote: > How hard is it to connect to a cable modem service with FreeBSD? > I'm thinking of getting a Foxtel connection, which uses the Motorola > 10Mbps/768kbps system. I'm using a FreeBSD 3.1-r machine, connected to UPC cable services here in Amsterdam. The LANCity connects directly to a 10 Mbit/h NIC. According to UPC I need to DHCP my NIC but after doing this once manually, my IP never changed and I hardcoded this in rc.conf. I believe 3.3-r supports DHCP by default from floppyboot. Btw: I'm NAT'ting on this FreeBSD machine to a small local net for a windows machine and my laptop. Works excellent, although I hope UPC is not subscribed to this list :) I'm not sure how this Foxtel connects to your machine, but if it's via a NIC, you're safe. I don't have any experience with a serial cablemodem. Cheers, ao -- arjan van der oest - systems administrator - arjan@nl.demon.net Demon Internet NOC, Amsterdam. www.demon.nl Thus (tm): Simplicity, boldness & speed. www.let-it-be-thus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message