From: Jay A. Kreibich <jak@uiuc.edu>
To: Scott Marlowe <smarlowe@qwest.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 12:18:57 -0500
Message-ID: <20041019171857.GB17857@uiuc.edu> (raw)
In-Reply-To: <1098205351.21035.33.camel@localhost.localdomain>
References: <LPENJIOOLAIJBFKIBDKOAEJHFMAD.kenta@ezyield.com>
<1098205351.21035.33.camel@localhost.localdomain>
On Tue, Oct 19, 2004 at 11:02:31AM -0600, Scott Marlowe scratched on the wall:
> This is more a networking issue than a PostgreSQL one. What you'll like
> want to do is to set up a nic in each box and use a "rolled" cable
> directly between them
Actually, you want a "cross-over" cable, not a "roll" cable. There is
a difference.
With many newer, high quality NICs, you don't even need that. Many
modern NICs do auto MDI/MDI-X detection, so any standard cable will do.
-j
--
Jay A. Kreibich | Comm. Technologies, R&D
jak@uiuc.edu | Campus IT & Edu. Svcs.
<http://www.uiuc.edu/~jak; | University of Illinois at U/C
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: jak@uiuc.edu, smarlowe@qwest.net, kenta@ezyield.com
Subject: Re: NIC to NIC connection
In-Reply-To: <20041019171857.GB17857@uiuc.edu>
References: <LPENJIOOLAIJBFKIBDKOAEJHFMAD.kenta@ezyield.com> <1098205351.21035.33.camel@localhost.localdomain> <20041019171857.GB17857@uiuc.edu>
* 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