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 E5AF9329F30 for ; Tue, 19 Oct 2004 23:13:52 +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 31286-10 for ; Tue, 19 Oct 2004 22:13:45 +0000 (GMT) Received: from bayswater1.ymogen.net (host-154-240-27-217.pobox.net.uk [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id C9406329F4C for ; Tue, 19 Oct 2004 23:13:46 +0100 (BST) Received: from [82.68.132.233] (82-68-132-233.dsl.in-addr.zen.co.uk [82.68.132.233]) by bayswater1.ymogen.net (Postfix) with ESMTP id 04570A3D18; Tue, 19 Oct 2004 23:13:44 +0100 (BST) Message-ID: <41759198.4070505@ymogen.net> Date: Tue, 19 Oct 2004 23:13:44 +0100 From: Matt Clark User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruno Wolff III Cc: 'Kent Anderson' , "'Pgsql-Admin@Postgresql. Org'" Subject: Re: NIC to NIC connection References: <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> In-Reply-To: <20041019220133.GA2957@wolff.to> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/250 X-Sequence-Number: 15243 >Switches are not security devices. While it is harder to sniff packets on >switches, you can't count on them to prevent hostile machines on the >switch from playing games with the arp protocol. Also I believe that if >a switch doesn't remember where a particular mac address is it will send >the packet to all of the attached ports. > > If you have 6 app servers it's just daft to stick 6 NICs in your DB server. If absolute privacy is a concern (not mentioned by the OP), then use a dedicated switch (or switches) for the 'private' subnet. Even better, use SSH. But all this is over the top for 99.9% of uses anyway. A VLAN is as private as anything else, so you can just create a VLAN on your current switch fabric and use that. No kind of traffic on a VLAN will hit any other VLAN. Unless of course someone has hacked your switch, set up a mirror port, attached a sniffer or other hacked machine to it, and is assiduously reading your traffic, in which case you have bigger problems.... M