From owner-freebsd-net Tue Dec 5 11:31:52 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 11:31:46 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mailman.thenap.com (mailman.thenap.com [209.190.0.10]) by hub.freebsd.org (Postfix) with ESMTP id 5F02E37B400 for ; Tue, 5 Dec 2000 11:31:46 -0800 (PST) Received: by mailman.thenap.com with Internet Mail Service (5.5.2650.21) id ; Tue, 5 Dec 2000 14:42:01 -0500 Message-ID: From: "Drew J. Weaver" To: 'Julian Elischer' Cc: "'freebsd-net@freebsd.org'" Subject: RE: Really odd problem Date: Tue, 5 Dec 2000 14:42:01 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C05EF3.700E0AEA" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C05EF3.700E0AEA Content-Type: text/plain; charset="iso-8859-1" I *could* do that, whats the hostname of your mail server? I'll have it ping that =p No messages on the console at all, and again i've tried two seperate NIC cards both the (onboard intel) and the offboard PCI Intel 10/100 -Drew -----Original Message----- From: Julian Elischer [mailto:julian@elischer.org] Sent: Tuesday, December 05, 2000 2:30 PM To: Drew J. Weaver Cc: 'freebsd-net@freebsd.org' Subject: Re: Really odd problem > "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. Are you getting messages on the console? possibly the card is bad and dies after a while.. the transmit timeout for many drivers will try reinitialise the chip. Which may bring it back to life... (for a while) you could always add 'ping -i 120 [some address]' to some startup script :-) > > Thanks, > -Drew -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v ------_=_NextPart_001_01C05EF3.700E0AEA Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Really odd problem

I *could* do that, whats the hostname of your mail = server? I'll have it ping that =3Dp No messages on the console at all, = and again i've tried two seperate NIC cards both the (onboard intel) = and the offboard PCI Intel 10/100

-Drew


-----Original Message-----
From: Julian Elischer [mailto:julian@elischer.org]
Sent: Tuesday, December 05, 2000 2:30 PM
To: Drew J. Weaver
Cc: 'freebsd-net@freebsd.org'
Subject: Re: Really odd problem


> "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.

Are you getting messages on the console?

possibly the card is bad and dies after a = while..
the transmit timeout for many drivers will try = reinitialise the chip.
Which may bring it back to life... (for a = while)

you could always add 'ping -i 120 [some address]' =
to some startup script 

:-)


>
> Thanks,
> -Drew

--
      __--_|\  Julian = Elischer
     = /       \ julian@elischer.org
    (   = OZ    ) World tour 2000
---> X_.---._/  presently in:  = Budapest
          &nb= sp; v

------_=_NextPart_001_01C05EF3.700E0AEA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message