From owner-freebsd-isp Tue Dec 5 21:15:19 2000 From owner-freebsd-isp@FreeBSD.ORG Tue Dec 5 21:15:17 2000 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id A78E537B400 for ; Tue, 5 Dec 2000 21:15:15 -0800 (PST) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 143WF6-00052Q-00; Tue, 5 Dec 2000 20:31:44 -0800 Date: Tue, 5 Dec 2000 20:31:41 -0800 (PST) From: Tom Samplonius To: "Drew J. Weaver" Cc: "'freebsd-isp@freebsd.org'" Subject: Re: Really odd problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 5 Dec 2000, Drew J. Weaver wrote: > We have a Freebsd 4.2 box on our network, after the box boots, it > brings up the network and everything is great, I can telnet into it.. > everything good, but about 30-60 minutes later no incoming traffic is > getting to the server. If i ping the machine, or telnet to it, I get > nothing. If I go to the terminal and ping anything then it "wakes up" does > anyone have any idea what would cause it to stop "listening" to incoming > network requests? This is becoming very tiresome and i've done everything > known to me. Well, if you rule any issues on the host, it could be a network issue. If you are using a ethernet switch, make sure the switch is broadcasting unknown traffic to the port your server is connected to. That is the default mode of operation on all switches, but it can be disabled on some. The switch uses a table of MAC -> port mappings that it builds by examining traffic. It ages entries out of the table (ie. 30 to 60 minutes). Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message