From owner-freebsd-net Tue Dec 15 19:43:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14378 for freebsd-net-outgoing; Tue, 15 Dec 1998 19:43:45 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from n4hhe.ampr.org (tnt3-33.HiWAAY.net [208.147.146.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14356 for ; Tue, 15 Dec 1998 19:43:42 -0800 (PST) (envelope-from dkelly@n4hhe.ampr.org) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by n4hhe.ampr.org (8.9.1/8.9.1) with ESMTP id VAA69947; Tue, 15 Dec 1998 21:21:09 -0600 (CST) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199812160321.VAA69947@n4hhe.ampr.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Parker, David K" cc: freebsd-net@FreeBSD.ORG From: David Kelly Subject: Re: FreeBSD & CableModem In-reply-to: Message from "Parker, David K" of "Tue, 15 Dec 1998 12:14:52 CST." <6C94DFBFD20ED211A8E3006097A1760F02A136@xs.ci.bryan.tx.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 21:21:09 -0600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Parker, David K" writes: > I hope I'm posting this to the correct list... > I have a PC setup with FreeBSD version 3.0. > My problem is with the TCP/IP Configuration and CableModem. > > If I place the PC on my internal network using an IP Address/SM/GW for a > Class C network, it works fine. I can resolve other host names, ping, etc... > > When I configure for our ISP using a cablemodem I have no such luck. Here is > the IP info... > IP: 208.162.121.228 > SM: 255.255.254.0 > GW: 208.162.120.1 > > I can ping the loopback and 208.162.121.228 but nothing else. > This same configuration works fine when I use an NT Box. You are running FreeBSD and NT different systems, right? I have been told that most cable modem boxes have a very limited IP protocol stack and are not intended to be placed on a multihost ethernet. After reset they grab the first hardware ethernet address and lock on to it. And will not talk to any other host until the next reset. If this is the case then your cable modem locked onto the NT box. Make a direct connection to your FreeBSD system from the cable modem. Then power cycle the cable modem. See if that works. Based on your discription I'd guess you are plugging your cable modem into a hub? Probably the Right Thing To Do would be to put two ethernet cards in your FreeBSD system and let FreeBSD be a NAT gateway and firewall for your other systems. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message