receive only UTP cable

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Bryce C
Date:  
Subject: receive only UTP cable
--=-FE1tlsriV1abi38K/4OB
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I don't think that'd work if you were doing anything more than sniffing
a network. To get a web page (staging->web) or to access a file
(web->staging), you must first ask for it and that requires the send
ability.

And yes, I accidentally made one of these one time awhile back and yes,
it made things really difficult until I realized what had happened.

On Mon, 2003-09-08 at 10:06, wrote:
> 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?
>=20
>=20
> http://www.geocities.com/samngms/sniffing_cable/
>=20
> Jim
> >=20
> > From: Bill Jonas <>
> > Date: 2003/09/08 Mon PM 12:46:49 EDT
> > To: 
> > Subject: Re: Updating web server (apache) in a DMZ
> >=20
> > On Mon, Sep 08, 2003 at 12:25:18PM -0400,  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?
> >=20
> > 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?)
>=20
> >=20
> > I suppose you could go the UDP route and use something like TFTP, but
> > you'll be left without error correction.
> >=20
> > --=20
> > Bill Jonas    *        *    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
> >=20
> >=20

--=20
Bryce C <>
CoBryce Communications

--=-FE1tlsriV1abi38K/4OB
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA/XQ6t/wbq/C6yyPcRAo0QAJ9mXM3DIBIgE/p17uqeRJM3GR04NQCfbfjp
3cP8ymx359M0mVtPkBenCW8=
=TweQ
-----END PGP SIGNATURE-----

--=-FE1tlsriV1abi38K/4OB--