From owner-freebsd-chat Wed Dec 16 10:48:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24155 for freebsd-chat-outgoing; Wed, 16 Dec 1998 10:48:01 -0800 (PST) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24131 for ; Wed, 16 Dec 1998 10:47:59 -0800 (PST) (envelope-from jooji@webnology.com) Received: from localhost (jooji@localhost) by mercury.webnology.com (8.9.1/8.8.8) with SMTP id NAA31017; Wed, 16 Dec 1998 13:55:40 -0600 (envelope-from jooji@webnology.com) Date: Wed, 16 Dec 1998 13:55:39 -0600 (CST) From: "Jasper O'Malley" To: Bill Paul cc: freebsd-chat@FreeBSD.ORG Subject: Re: Some good press for FreeBSD (I guess...) In-Reply-To: <199812160550.AAA05843@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 16 Dec 1998, Bill Paul wrote: > The reviewers gave the best overall rating to the Fort Knox system, > which, according to the 'features' listing on page 71, runs a modified > version of FreeBSD. I figured this out when I noticed that the network interfaces were named "vx0", "vx1", and "vx2" in the first model I was unfortunate enough to install, and "fxp0", "fxp1", and "fxp2" in the later models. I had to twist Internet Devices' arm to admit it, too, which pissed me off on general principle. > I've actually had the displeasure of using the SonicWall device. Some > of the things that struck me were: > > - While the device is meant to be configured by a web browser, it has > to be one that supports just the right version of java. The manual > recommends netscape, and sure enough, when we tried to use Internet > Exploder with it, results were less than perfect (things didn't always > display properly; no, I didn't try tweaking it: it's a stinking web > browser and I have better things to do). Ditto for the Fort Knox. Takes forever for the classes to load, and once they do it's nothing to write home about. > - The device can _only_ be configured through a web browser. There is > no serial port to which you can attach a dumb terminal in an emergency. > This really bothered me: it's incredibly easy to shoot yourself in the > foot with the browser interface and get the thing into a state where > you can't connect to it via the network. I can't see how you're supposed > to fix such a problem without a directly wired console. Ditto again, for the Fort Knox. You can slap a phone line into it and have Internet Devices' 9-5, M-F tech support department dial in to fix if it you've hosed the thing. You're not allowed to do it yourself, though. > - There's no way to reset the device back to the factory default > configuration. This is technically possible with the Fort Knox box, though I've never actually tried it. They provide a serial port dongle you can slap on the back and power up the machine with, which is supposed to set it back to the defaults. I guess it's not a horrible device for the technically uninclined, but I've seen better. Unless I have to, I won't be working with another. It's not the box itself that sucks, it's the bloody user interface...I might reconsider my opinion of it, though, if they put some serious effort into improving the graphical interface, and provided a command line interface, even if on a limited basis. Cheers, Mick The Reverend Jasper P. O'Malley dotdot:jooji@webnology.com Systems Administrator ringring:asktheadmiral Webnology, LLC woowoo:http://www.webnology.com/~jooji To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message