X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id F1B2032A85F for ; Tue, 19 Oct 2004 23:23:13 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 37884-05 for ; Tue, 19 Oct 2004 22:23:04 +0000 (GMT) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id B8D1D32A6DC for ; Tue, 19 Oct 2004 23:23:05 +0100 (BST) Received: (qmail 3994 invoked by uid 500); 19 Oct 2004 22:33:45 -0000 Date: Tue, 19 Oct 2004 17:33:45 -0500 From: Bruno Wolff III To: Matt Clark Cc: 'Kent Anderson' , "'Pgsql-Admin@Postgresql. Org'" Subject: Re: NIC to NIC connection Message-ID: <20041019223345.GA3753@wolff.to> Mail-Followup-To: Matt Clark , 'Kent Anderson' , "'Pgsql-Admin@Postgresql. Org'" References: <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41759198.4070505@ymogen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41759198.4070505@ymogen.net> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/251 X-Sequence-Number: 15244 On Tue, Oct 19, 2004 at 23:13:44 +0100, Matt Clark wrote: > > If you have 6 app servers it's just daft to stick 6 NICs in your DB > server. While there might be some cases where that makes sense most likely it isn't something you would want to do. I believe the original motivation was to solve bandwidth congestion rather than security. Most likely the systems were already connected to switches. If the nic to the web server(s) were really swamped (which seems unlikely, but could be the case), then adding a second nic and connecting to another port on the switch they are already using would probably work as well as running cables directly from the web server(s) to the database. They would need to adjust the routing tables so that some traffic went over each nic. An easy change would be to specify that traffic destined for the database server IP address is to go over the new nic and all other traffic is to go over the old nic.