From owner-freebsd-questions Sun Sep 2 15:22:55 2001 Delivered-To: freebsd-questions@freebsd.org Received: from pioneernet.net (mail.pioneernet.net [207.115.64.224]) by hub.freebsd.org (Postfix) with ESMTP id 9113837B401 for ; Sun, 2 Sep 2001 15:22:51 -0700 (PDT) Received: from chip.wiegand.org [66.114.152.128] by pioneernet.net (SMTPD32-6.06) id A1C420F00E4; Sun, 02 Sep 2001 15:25:08 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Chip To: "Ted Mittelstaedt" , "Joe Clarke" Subject: Re: replacing a cisco router with a fbsd box Date: Sun, 2 Sep 2001 15:23:29 -0700 X-Mailer: KMail [version 1.2] Cc: References: <009f01c1339d$941264c0$1401a8c0@tedm.placo.com> In-Reply-To: <009f01c1339d$941264c0$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Message-Id: <01090215232906.44697@chip.wiegand.org> Content-Transfer-Encoding: 8bit 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 On Sunday 02 September 2001 03:54, Ted Mittelstaedt wrote: > >-----Original Message----- > Offloading NAT from a > > >router with a small amount of RAM will improve packet flow to be sure. In > >fact, if you're experiencing lock-ups, I'd try that. It may help you > >isolate the problem. FreeBSD's NAT is pretty good for most standard > >protocols. I've found it's relatively easy to add support to. > > But it doesen't so the DNS trick that you guys do which is very useful. :-( > > >Also, if you do find yourself having to reload, see if you're getting any > >tracebacks. Do a show ver or show stack, and see what you can see. Those > >memory addresses can be useful for tracking down bugs. > > He was saying that when the router got hosed that they had to power-cycle > which I take it to mean the device froze. It sounds suspiciously like > flakey hardware to me. Maybe someone upgraded the ram with some random PC > memory they had lying around? Naw, it is as it was when it was purchased. I've always been of the opinion that it is flakey hardware, just not getting anywhere in getting it dealt with. (Dang that blister is in a bad spot, :(, right on the tip of my middle finger.) The reason why we have to power-cycle it is it will just stop allowing connections, any ol time, just quits. We power-cycle the unit and a few minutes later it's working okay. It's gotten to the point where I have to connect to the site from home every day just to make sure it is still working. -- Chip > > Ted Mittelstaedt > tedm@toybox.placo.com Author of: The FreeBSD > Corporate Networker's Guide Book website: > http://www.freebsd-corp-net-guide.com -- -- Chip W. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message