From owner-freebsd-stable Thu Jan 25 15:28:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from front001.cluster1.charter.net (outbound.charter.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id 688C537B6A3 for ; Thu, 25 Jan 2001 15:28:40 -0800 (PST) Received: from [24.217.145.132] (HELO dave) by front001.cluster1.charter.net (CommuniGate Pro SMTP 3.4b8) with SMTP id 16676228; Thu, 25 Jan 2001 18:28:39 -0500 From: Dave Uhring To: Stephen Montgomery-Smith , Luc Morin Subject: Re: Network stops working Date: Thu, 25 Jan 2001 17:28:32 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" Cc: freebsd-stable@FreeBSD.ORG References: <001001c08628$8db16180$9d8fc918@videotron.ca> <005a01c086f7$337f51c0$9d8fc918@videotron.ca> <3A706A34.E5F1C502@math.missouri.edu> In-Reply-To: <3A706A34.E5F1C502@math.missouri.edu> MIME-Version: 1.0 Message-Id: <01012517283203.22152@dave> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Power cycle your cable modem. Pull the power plug and reinstall it 5 minutes later. Then kill the dhclient process and restart it after the cable modem status light remains steady. On occasion I have had the same problem with my service - using 3Com Cable Modem CMX. Dave On Thursday 25 January 2001 12:02, Stephen Montgomery-Smith wrote: > That's interesting - I have a similar problem that also > just started recently (coincided with changing my power > supply but I'm sure that it is unrelated). I find that > one of three things happens: > > 1. dhcp simply does not successfully negotiate > > 2. dhcp negotiates, gets an IP number and a router, but > then I get 100% packet loss. (Never tried calling them to > see if they got through to me.) > > 3. It actually works. > > Option 2 is what usually happens, but if I restarting > dhcp enough times, I get option 3. Since I keep the > connection up all the time, I only worry about the > problem sporadically. So I have never tried to investigate > its cause. (The ISP is att@home if that is useful. My > NIC is a RealTek 8139.) > > Luc Morin wrote: > > Hi, > > > > I've been asked to clarify the topology of my system. > > > > Very simple setup. All I have is my home box connected to my ISP > > thru cable-modem. My NIC is a PCI NE2000 clone using the ed driver. > > > > My ISP uses DHCP to assign my IP, so I run dhclient at boot time > > from my rc.conf file. This setup has been running fine for me for > > over a year now. Even after my last cvsup/buildworld everything was > > still perfectly working. > > > > A few days ago, I started getting a situation where after a few > > minutes of operation (after boot), I can't reach anything, not even > > my default gateway (assigned by my ISP as part of DHCP). > > > > I've talked to my ISP's tech support rep, and he told me he could > > ping my box just fine ( 0% packet loss ), while I couldn't ping > > anything ( 100% packet loss ). I also noticed that even though > > I can't reach the outside world, I still see some syslogd messages > > about failed attempt to connect to my box (I have log_in_vain="YES" > > in rc.conf). > > > > Please see attached file for specifics of my system (kernel config > > file, dmesg output, uname -a, ps -ax etc...) > > > > I hope this clarifies the situation :-) > > > > Many thanks, > > > > Luc Morin > > > > > > ------------------------------------------------------------------- > >------------- Name: info.txt > > info.txt Type: Plain Text (text/plain) > > Encoding: quoted-printable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message