From owner-freebsd-stable@FreeBSD.ORG Thu Sep 8 01:29:27 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAFC316A41F for ; Thu, 8 Sep 2005 01:29:27 +0000 (GMT) (envelope-from stephen@math.missouri.edu) Received: from sccmmhc91.asp.att.net (sccmmhc91.asp.att.net [204.127.203.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id E888743D77 for ; Thu, 8 Sep 2005 01:29:22 +0000 (GMT) (envelope-from stephen@math.missouri.edu) Received: from [10.0.0.4] (12-207-25-104.client.mchsi.com[12.207.25.104]) by sccmmhc91.asp.att.net (sccmmhc91) with ESMTP id <20050908012921m9100g7dege>; Thu, 8 Sep 2005 01:29:21 +0000 Message-ID: <431F93F0.5090401@math.missouri.edu> Date: Wed, 07 Sep 2005 20:29:20 -0500 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.11) Gecko/20050905 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Problem with thernet card and dhclient X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2005 01:29:27 -0000 My computer running a very recent FreeBSD release 5 is connected to the internet with "3Com 3c980C Fast Etherlink XL" to a cable modem connected to Mediacom. I connect with the command "dhclient xl0". The problem I have is that every so often the mediacom connection goes down, and when it comes up again, the computer seems unable to connect with the outside world. Yet if I do "killall dhclient;dhclient xl0" it happily connects sufficiently well to get itself an IP address from the mediacom dhcp server, but it does not seem able to pass any other kind of internet info, e.g. ping, nameserver, ssh, etc. However rebooting the computer completely solves the problem. It is as if the IP software gets stuck in some weird mode, and seems unable to get out of it. Anyone got any ideas? I'll provide more details about the system if that will help. Thanks, Stephen