This is a multi-part message in MIME format.

------=____1063040774065_3SDIK'6rOk
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I found instructions on to make a recieve only cable.  I believe I might be able to use this between the staging server and the live web server, any suggestions other than the ones below.  Has anyone used a cable like this?


http://www.geocities.com/samngms/sniffing_cable/

Jim
> 
> From: Bill Jonas <bill@billjonas.com>
> Date: 2003/09/08 Mon PM 12:46:49 EDT
> To: plug-discuss@lists.plug.phoenix.az.us
> Subject: Re: Updating web server (apache) in a DMZ
> 
> On Mon, Sep 08, 2003 at 12:25:18PM -0400, elemint@cox.net wrote:
> > Would a recieve only cable be a good idea so the server on a seperate
> > nic would have a cable where it could recieve only  recieve the
> > updated files and then implement them?
> 
> Not a good idea -- you really need two-way communication for any
> standard TCP-based protocol to work.  (If the other server can't
> respond, how can it complete the three-way handshake, for example?)

> 
> I suppose you could go the UDP route and use something like TFTP, but
> you'll be left without error correction.
> 
> -- 
> Bill Jonas    *    bill@billjonas.com    *    http://www.billjonas.com/
> "It's a dangerous business, Frodo, going out your front door.  You step
> into the Road,  and if you don't keep your feet,  there  is  no knowing
> where you might be swept off to."  --  Bilbo Baggins
> 
> 

------=____1063040774065_3SDIK'6rOk
Content-Transfer-Encoding: base64
Content-Type: application/pgp-signature;
	name="replyAll"
Content-Disposition: inline;
	filename="replyAll"

LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NClZlcnNpb246IEdudVBHIHYxLjAuNyAo
R05VL0xpbnV4KQ0KDQppRDhEQlFFL1hMSjNkbUhjVXhGdkRMMFJBZ1JsQUpzRzRNYlRqMW5s
MytZK1BOUGpudWlHV1FCQlpBQ2ZXZjNJDQp4bDNRWWJMSldPem5zSHZsSHJyN21Bdz0NCj1k
a3NpDQotLS0tLUVORCBQR1AgU0lHTkFUVVJFLS0tLS0NCg0K
------=____1063040774065_3SDIK'6rOk--