From owner-freebsd-questions Wed Jul 14 14: 0: 5 1999 Delivered-To: freebsd-questions@freebsd.org Received: from c523578-a.sttls1.wa.home.com (c523578-a.sttls1.wa.home.com [24.5.122.51]) by hub.freebsd.org (Postfix) with ESMTP id DCF6B14BCF for ; Wed, 14 Jul 1999 13:59:59 -0700 (PDT) (envelope-from todd@c523578-a.sttls1.wa.home.com) Received: from localhost (todd@localhost) by c523578-a.sttls1.wa.home.com (8.9.3/8.9.3) with ESMTP id OAA09270; Wed, 14 Jul 1999 14:07:28 -0700 (PDT) (envelope-from todd@c523578-a.sttls1.wa.home.com) Date: Wed, 14 Jul 1999 14:07:28 -0700 (PDT) From: Todd Backman To: Damien Tougas Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Getting frustrated with bizarre networking problem... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible that the NIC has some sort of "WAKE ON LAN" feature enabled on it? I had similar problems with some of my Intel cards. (the server did not have much traffic)... - Todd On Wed, 14 Jul 1999, Damien Tougas wrote: > Hello, > > I made a posting about a week or so ago about a network problem that we are > currently > experiencing with our web/mail server. I have included a copy of this > original message > below just as a reference. > > It was suggested to me to try logging packets using ipfw or tcpdump, so I > decided to use > tcpdump. The bizarre thing is that as soon as I started using tcpdump, my > problem > virtually vanished (it still occurred, but much less frequently). I have > since discovered > that whenever I notice that the server appears to be down to the outside > world, all I have > to do is start tcpdump and it comes back instantaneously. Truly a bizarre > problem. > > I have just upgraded (yesterday) to the latest version of 3.2-stable, and > have been in > dialog with our ISP as well, bu so far nothing has been uncovered. We are > using a > 3C905B-TX NIC, are there any issues with this card? I am going to try to > replace the > NIC to see if there might be a hardware problem, but I am starting to run > out of ideas. > > Any suggestions would be greatly appreciated. > > Damien Tougas > Converging Technology Solutions, Inc. > 10148 - 73 Street > Edmonton, Alberta T6A 2W9 > Phone: (780) 469-1679 > Fax: (780) 461-5127 > mailto:dtougas@converging.net > http://www.converging.net > > Original Posting (Subject was: Network problems...): > > We have been experiencing an ineteresting network problem, I'm not exactly > sure what it is rooted > in, but I thought I would ask around just in case it is related to somthing > in FreeBSD. > > We have two servers directly connected to the internet through an ADSL > connection, one is running > FreeBSD 3.1, the other is running NT Server 4.0. The FreeBSD server is our > internet http and mail > server, the NT server is acting as a gateway to our internal network running > Microsoft Proxy. > > Frequently (at least once a day) the FreeBSD server will lose contact with > the outside world. What I mean by this is that nobody ouside of our subnet > can access it, not even ping works. While this > occurs, we can still ping the NT server from the outside (verifying that the > ADSL still works), and > we can still access the FreeBSD server from within the subnet without any > problems. After an hour > or so, the problem clears itself up and the FreeBSD server goes live again. > > I have noticed this happen on several occasions while using ssh to access > the FreeBSD server from home. I would be working, lose my connection and no > longer have any contact with the > server for about an hour, then it would mysteriously reappear. > > We have also observed that when we lose outside contact with the server, if > we reboot it, it comes back immediately, indicating that the problem is > likely related to some server configuration issue. > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message