From owner-freebsd-stable Mon Oct 4 13:24:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from destiny.erols.com (destiny.erols.com [207.96.73.65]) by hub.freebsd.org (Postfix) with ESMTP id 642D81528C for ; Mon, 4 Oct 1999 13:24:33 -0700 (PDT) (envelope-from jdowdal@destiny.erols.com) Received: from destiny.erols.com (someone@destiny.erols.com [207.96.73.65]) by destiny.erols.com (8.9.3/8.6.12) with ESMTP id QAA15448; Mon, 4 Oct 1999 16:24:16 -0400 (EDT) Date: Mon, 4 Oct 1999 16:24:16 -0400 (EDT) From: John Dowdal To: David Kott Cc: High Voltage , FreeBSD-Stable Subject: Re: @Home Connect. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 3 Oct 1999, David Kott wrote: > That seems odd to me. My roommate and I share the same cable modem. We > are not proxied as each of us have a distinct, and static IP. @Home > allows us to purchase additional IPs (up to 3 per household) to add > additional computers. > The modem is a Mot. Cybersurfer Wave. Both times I set up cable modems on unix, they had a single IP. The power cycle rule applied for the single-IP config on the old (big) motorola, and the new (small) motorola on Comcast cable system in Baltimore County, MD, and to the system in Norfolk VA. In both cases, we set up a BSD machine with two ethernet cards. One connected to teh cable modem directly, the other connected to the LAN (LAN side is 100mbit too). The unix machine took on the real IP, and the 100mbit network was configured with NATD (illegally for @home, but who cares). John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message