pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matt Clark <matt@ymogen.net>
To: Bruno Wolff III <bruno@wolff.to>
Cc: Kent Anderson <kenta@ezyield.com>
Cc: 'Pgsql-Admin@Postgresql. Org' <pgsql-admin@postgresql.org>
Subject: Re: NIC to NIC connection
Date: Tue, 19 Oct 2004 23:13:44 +0100
Message-ID: <41759198.4070505@ymogen.net> (raw)
In-Reply-To: <20041019220133.GA2957@wolff.to>
References: <LPENJIOOLAIJBFKIBDKOAEJHFMAD.kenta@ezyield.com>
	<00d001c4b5f9$f4d63660$8300a8c0@solent>
	<20041019220133.GA2957@wolff.to>


>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



view thread (20+ messages)  latest in thread

Message-ID: <41759198.4070505@ymogen.net>
Permalink:  ../41759198.4070505@ymogen.net/
Also on:    postgresql.org/message-id/41759198.4070505@ymogen.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: matt@ymogen.net, bruno@wolff.to, kenta@ezyield.com
  Subject: Re: NIC to NIC connection
  In-Reply-To: <41759198.4070505@ymogen.net>
  References: <LPENJIOOLAIJBFKIBDKOAEJHFMAD.kenta@ezyield.com> <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41759198.4070505@ymogen.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox