From owner-freebsd-stable@FreeBSD.ORG Fri Jan 30 15:04:09 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B323C1065697; Fri, 30 Jan 2009 15:04:09 +0000 (UTC) (envelope-from chris#@1command.com) Received: from mail.1command.com (mail.1command.com [75.160.109.226]) by mx1.freebsd.org (Postfix) with ESMTP id 687E98FC26; Fri, 30 Jan 2009 15:04:09 +0000 (UTC) (envelope-from chris#@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id n0UF41H0010429; Fri, 30 Jan 2009 07:04:07 -0800 (PST) (envelope-from chris#@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id n0UF40RC010428; Fri, 30 Jan 2009 07:04:00 -0800 (PST) (envelope-from chris#@1command.com) Received: from hitme.hitometer.net (hitme.hitometer.net [75.160.109.235]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Fri, 30 Jan 2009 07:03:59 -0800 Message-ID: <20090130070359.riaj3vq4aock4k0s@webmail.1command.com> X-Priority: 3 (Normal) Date: Fri, 30 Jan 2009 07:03:59 -0800 From: Chris H To: freebsd-stable@freebsd.org References: <20090129015034.7dxisep21w04gksg@webmail.1command.com> <0bca01c98202$a6124350$f236c9f0$@co.uk> <20090129051522.a92df0myf44gsko4@webmail.1command.com> <62b856460901290538x5d857f08ka3b2ffb5a7aa8e7f@mail.gmail.com> <20090129060243.adauuua9eokcsos8@webmail.1command.com> <00fe01c98247$d6872600$83957200$@com> <49822E90.1010306@FreeBSD.org> <20090129181838.l9cr09o0kk400gwc@webmail.1command.com> <4982EB63.50703@FreeBSD.org> In-Reply-To: <4982EB63.50703@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) 4.1 Professional (not for redistribution) / UNIX Cc: "Bruce M. Simpson" Subject: Re: Replace Cisco IOS/CBOS with freebsd - possible? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2009 15:04:10 -0000 Hello Bruce, and thank you for your reply. Quoting "Bruce M. Simpson" : > Chris H wrote: >> ... >>> >>> I know Peter Grehan was looking at getting FreeBSD onto the Cisco >>> 827 a while back. >> >> That's good news. I'll have to see if I can get more info on that. >> I just purchased a "lot" of cisco *DSL/routers on ebay, in an effort >> to push this project forward (I can experiment on these with less concern). > > IMHO pfSense beats the pants off OpenWRT from a user/deployment point > of view, and often that is ultimately what counts. I guess I'd have to agree, except if it weren't for the fact I always have a zillion things going simultaneously, I wouldn't even know what X was - I can't get enough VC's (virtual consoles), so I'm forced to use X. But, of course for most "end users" /convenience/ is everything, and most don't want to any more that how to turn it on. :) > > Thing is, it's "only" for x86-based PCs. I had the foresight to > purchase some relatively quiet 1U boxes, but they're still too noisy > to have in a room where people sleep live or socialise -- they belong > to the computer nook at the front of the apartment (I have a very odd > C-shaped apartment). Yes, the (older) cisco's CPU's were MIPS - aka - Motorola, and ran AUX. I've got the latest version of AUX, which is a newer version than they ran. In fact, it wouldn't be a bit surprised if I could load AIX on it. > > I believe something that could really make pfSense fly, would be a > viable port to mass-market, low-power consumer hardware. Then again, > old Ciscos "sort of" fit the bill. Funny you bring that up. I was thinking the very same. As a matter of fact I have been contemplating whipping something up myself, and doing just that. While psSense initially seems appealing. The more I look into it, the more I find it's laking - where a simple roll-out is concerned. There isn't anything in the way of documentation. What's there is /horribly/ unorganized. It's scattered all over the place. What's more, the front page of the wiki suggests that reading the m0n0wall documentation would probabl;y be a better choice. Make no mistake, I know how daunting and hectic an opensource project can be, and am grateful to /anyone/ whom is willing to share the fruits of their labor at no cost. But I think I could do better, that's all. > > Repurposing old vendor hardware is just as subject to engineering > process as anything else, in some cases, the varying > Bill-of-Materials may make the economic cost too high to do things on > a mass scale. I think I have a solution for that. I'll elaborate further when I can confirm that. > > If people would be reasonably expected to use such a system, they > should not have to understand the mechanisms, in great detail, of how > firmware is loaded onto a device. This is one of the main stumbling > blocks behind mass uptake -- we can't just say "fire up this tool and > click this 1 button" to extend/build new network infrastructure. > > Given the current economic and ecological situation, though, > devising systems which allow people to do this might be something > worth investigating, and funding to that effect may be available "out > there". I /quite/ agree, and intend to persue just that. I've already commissioned the artwork - and it looks GREAT. :) I'll elaborate further as things firm up. Thanks again Bruce, for taking the time to respond. --Chris > > cheers > BMS > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >