From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 3 May 2002 09:31:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 3 May 2002 09:31:15 -0400 Received: from smtp.comcast.net ([24.153.64.2]:24142 "EHLO mtaout05") by vger.kernel.org with ESMTP id ; Fri, 3 May 2002 09:31:14 -0400 Date: Fri, 03 May 2002 09:25:12 -0400 From: Russell Leighton Subject: Linux 2.4 as a router, when is it appropriate? To: linux-kernel@vger.kernel.org Message-id: <3CD28FB8.40204@elegant-software.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Could someone please tell me (or refer me to docs) on when using the Linux on PC hardware as a router is an appropriate solution and when one should consider a "real" router (e.g., Cisco)? I have heard that performance wise, if you have a fast CPU, much memory and good NICs that Linux can be as good all but the high end routers. Are there important missing features or realiability issues that make using Linux not suitable for "enterprise" use? Thanks. Russ