From owner-freebsd-net Tue Dec 5 12:12:47 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 12:12:44 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from measurement-factory.com (unknown [204.144.128.85]) by hub.freebsd.org (Postfix) with ESMTP id 9F4D337B400 for ; Tue, 5 Dec 2000 12:12:44 -0800 (PST) Received: from localhost (rousskov@localhost) by measurement-factory.com (8.9.3/8.9.3) with ESMTP id NAA01217; Tue, 5 Dec 2000 13:12:38 -0700 (MST) (envelope-from rousskov@measurement-factory.com) Date: Tue, 5 Dec 2000 13:12:38 -0700 (MST) From: Alex Rousskov To: "Drew J. Weaver" Cc: freebsd-net@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-net@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. Drew, We have seen similar (and worse) effects with the combination of "wake-up on LAN" and "power-save mode" BIOS features. Make sure that your [BIOS] settings disable funky features that FreeBSD does not support [well]. Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message