From owner-freebsd-questions Wed Apr 5 17:22:59 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtp01do.de.uu.net (smtp01do.de.uu.net [192.76.144.61]) by hub.freebsd.org (Postfix) with ESMTP id 4ED1637B66E for ; Wed, 5 Apr 2000 17:22:38 -0700 (PDT) (envelope-from rehsack@informatik.uni-halle.de) Received: from informatik.uni-halle.de ([195.124.230.62]) by smtp01do.de.uu.net (5.5.5/5.5.5) with ESMTP id CAA14657; Thu, 6 Apr 2000 02:22:30 +0200 (MET DST) Message-ID: <38EBD7DF.4307F55E@informatik.uni-halle.de> Date: Thu, 06 Apr 2000 02:18:39 +0200 From: Jens Rehsack Organization: LiWing X-Mailer: Mozilla 4.7 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: Mike Tancsa Cc: freebsd-questions@FreeBSD.ORG Subject: Re: connection problem: FreeBSD Computer does not respond References: <38EA7F40.FE128093@informatik.uni-halle.de> <20000404172309.V20770@fw.wintelcom.net> <38eab248.7085097@mail.sentex.net> <4.2.2.20000405074454.0368cdf8@mail.sentex.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Tancsa schrieb: > > At 11:33 AM 4/5/2000 +0200, Jens Rehsack wrote: > > > If you type dmesg, is there anything about the network interface going > >No. Last message after all that comes after boot messages was > >"promiscous > >mode enabled" - this must be from tcpdump. > >But the computer doesn't even answer directly after is was booted, but > >it answers when I send out packets. > > Do you have ipfw or ipfilter defined in the kernel ? No. a really simple kernel with no specialities. > Actually, do you have a different network card you can try ? Also is the I'm ordered a new one today. I will say more when it arrives. > switch Auto-Neg ? Try setting it to half duplex only. It's set to half duplex by default (the switch says it). But since today morning I let the machine ping it's right neighbor(?). It works uninterrupted. But yesterday I tries to ping the machine if it doesn't send packets out by itself and it does not response. To say it again: 1) If I boot the machine, it will not answer, but the NIC gets/recognizes the packets. 2) If I send some data out (f.e. echo request, ns lookup), the machine answers packets for ca. 3 hours. 3) Then it seems to be dead from world, but a look to the console shows: it's alive. 4) GoTo 2 ':-) Ciao and thanks for help and patience -- Jens Rehsack --- http://www.informatik.uni-halle.de/~rehsack/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message