Date: Thu, 25 Jan 2001 12:02:28 -0600 From: Stephen Montgomery-Smith <stephen@math.missouri.edu> To: Luc Morin <luc_m@videotron.ca> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Network stops working Message-ID: <3A706A34.E5F1C502@math.missouri.edu> References: <001001c08628$8db16180$9d8fc918@videotron.ca> <20010124164125.A12612@home.com> <01012500480800.01077@jamestown.enteract.com> <3A6FD545.3D329446@quake.com.au> <002b01c086e4$2c843060$9d8fc918@videotron.ca> <3A705EAA.23BD59B4@quake.com.au> <005a01c086f7$337f51c0$9d8fc918@videotron.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
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 -- Stephen Montgomery-Smith stephen@math.missouri.edu http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A706A34.E5F1C502>