From owner-freebsd-questions Wed Jan 29 14:43: 9 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CC8337B401 for ; Wed, 29 Jan 2003 14:43:07 -0800 (PST) Received: from mail.adelphia.net (pa-plum1b-166.pit.adelphia.net [24.53.161.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id A93DC43F75 for ; Wed, 29 Jan 2003 14:43:06 -0800 (PST) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com ([172.16.0.95]) by mail.adelphia.net (8.12.3/8.12.3) with ESMTP id h0TMiWhA000535; Wed, 29 Jan 2003 17:44:33 -0500 (EST) (envelope-from wmoran@potentialtech.com) Message-ID: <3E38588D.1000506@potentialtech.com> Date: Wed, 29 Jan 2003 17:41:17 -0500 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021127 X-Accept-Language: en-us, en MIME-Version: 1.0 To: tarmon@spamcop.net Cc: Corey.Brune@transplace.com, freebsd-questions@FreeBSD.ORG Subject: Re: References: <1043879475.3e38563375e35@webmail.spamcop.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I've been having problems with my test machines disappearing off of > the > network. When it happens, the machine does not respond to any incoming > traffic. > However, if I ping out, the connection starts working again. I'm guessing > the > card is somehow going to sleep and not responding until it sees outgoing > traffic. The ARP entry > still exists on the switch and router. I've had this problem with various > versions of FreeBSD. What kind of switch are you connecting everything together with? The only time I've ever seen this is with a switch that had an option to disable interfaces that had too much broadcast traffic. If the machine set idle too long, the ARP and other messages it was sending would cause it to be "shut off" by the switch, but as soon as you started sending some non-broadcast traffic again (such as ping), it would re-enable the port and things would work OK. I would suggest disabling that feature of the switch (if that's the problem) unless you're having problems with excessive broadcast traffic on your network. The workaround I used (because the sysadmin refused to reconfigure the switch because he didn't understand it) was to create a daemon "ping" process using & and using an -i 30 switch. For example, I had a script in /usr/local/etc/rc.d like so: #!/bin/sh /sbin/ping -i 30 192.168.5.27 & Where the IP is simply the IP of another machine on the network. This doesn't hurt much if the network is so idle that it's causing the switch to shut off ports anyway. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message