Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.netspace.net.au!news.mel.connect.com.au!news.syd.connect.com.au!news.bri.connect.com.au!corolla.OntheNet.com.au!not-for-mail From: Tony Griffiths <tonyg@OntheNet.com.au> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Buffer OVERLOAD? Date: Tue, 27 May 1997 11:29:43 +1000 Organization: On the Net (ISP on the Gold Coast, Australia) Lines: 43 Message-ID: <338A3907.376E@OntheNet.com.au> References: <01bc6520$798d6640$ca180ed0@default> Reply-To: tonyg@OntheNet.com.au NNTP-Posting-Host: swanee.nt.com.au Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mozilla 3.0 (WinNT; I) To: Immortal <webmaster@global-impact.com> Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:41647 Immortal wrote: > > ---The Problem: > > I run a FreeBSD 2.2.1-RELEASE still with its (GENERIC) settting. It seem > that every 1 or 2 days, the machine WIGS out, freezes of sorts. I can > TELNET to the computer via its primary IP address but all other aliased > interfaces (Virtual Domain/Web Sites), SMTP (Mail Requests), FTP, etc. Will > not function for 2-5 minutes and then almost like a miracle, it back better > then ever! You wouldn't be running 'routed' by any chance? If so, KILL IT IMMEDIATELY!!! Unless you have a "properly setup" routing environment (ie. routers that are broadcasting RIP packets), routed will screw your machine's routing table by deleting things that it 'thinks' are stale. The only other thing that I think of is another machine booting with the same IP address on it's ethernet interface. It will broadcast it's availability at a certain MAC address which will cause all other hosts/routers to no point there. I believe that the entries in the ARP table timeout so it is possible that when they so, a particular host now re-arps for the IP address and gets a response from the original system. > > ---What research has been done: > processes to no availe. Which leads me to believe that it was not a > process problem. It must be a TCP/IP aliased interface problem of some > sorts. > > MAYBE… a buffer gets FULL and them after (X number of minutes) dumps Doesn't sound to plausible to me. I'd check the routing and arp tables first- # netstat -r # arp -a to see where things are pointing. Tony