pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Matt Clark <matt@ymogen.net>
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 17:33:45 -0500
Message-ID: <20041019223345.GA3753@wolff.to> (raw)
In-Reply-To: <41759198.4070505@ymogen.net>
References: <LPENJIOOLAIJBFKIBDKOAEJHFMAD.kenta@ezyield.com>
	<00d001c4b5f9$f4d63660$8300a8c0@solent>
	<20041019220133.GA2957@wolff.to>
	<41759198.4070505@ymogen.net>

On Tue, Oct 19, 2004 at 23:13:44 +0100,
  Matt Clark <matt@ymogen.net> 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.



view thread (20+ messages)  latest in thread

Message-ID: <20041019223345.GA3753@wolff.to>
Permalink:  ../20041019223345.GA3753@wolff.to/
Also on:    postgresql.org/message-id/20041019223345.GA3753@wolff.to

 · 

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: bruno@wolff.to, matt@ymogen.net, kenta@ezyield.com
  Subject: Re: NIC to NIC connection
  In-Reply-To: <20041019223345.GA3753@wolff.to>
  References: <LPENJIOOLAIJBFKIBDKOAEJHFMAD.kenta@ezyield.com> <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41759198.4070505@ymogen.net> <20041019223345.GA3753@wolff.to>

* 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