[mod.protocols.tcp-ip] Proteon vs Arpanet query

DIXON-R%OSU-20@OHIO-STATE.ARPA.UUCP (02/17/87)

We purchased a Proteon P4200 gateway with an Arpanet card to serve as our campus
gateway to Arpanet. We were told that the gateway card supports 1822 DH, so
we specified that to the Arpanet people and have been awaiting arrival of the
Arpanet connection. Now the Arpanet people tell us we must change to 1822 HDH,
and to work that out with our vendor. Proteon says they do not support
1822 HDH.  Now what do we do? Throw out the Proteon box? Forget Arpanet?
Is this a catch-22 situation?

                                      Bob Dixon
                                      Ohio State University

-------
-------

hsw@TYCHO.ARPA.UUCP (02/18/87)

One pertinent piece of information you left out of your message is where
is the PSN (aka IMP) you are connecting to....  If the PSN is local
to you then DH should be more than adequate.  If you are having
problems getting a DH interface for the PSN then you should go back
to your sponsoring organization and raise your collective organizational
voice.  On the other hand, if the PSN is NOT local and you trying
to connect to one miles away (or more than 2K feet away), then you
really do need HDH.  The only other alternative is to put ECU boxes
on each end of the connection (one at the gateway and one at the
PSN).  This will work just fine (we have lots of ECUs here), but
DDN would rather you didn't throw extra boxes on the line that they
can't remotely diagnose.

Howard Weiss
National Computer Security Center
-------

brescia@CCV.BBN.COM.UUCP (02/19/87)

     
     We purchased a Proteon P4200 gateway with an Arpanet card to serve as our campu
     s
     gateway to Arpanet. We were told that the gateway card supports 1822 DH, so
     we specified that to the Arpanet people and have been awaiting arrival of the
     Arpanet connection. Now the Arpanet people tell us we must change to 1822 HDH,
     and to work that out with our vendor. Proteon says they do not support
     1822 HDH.  Now what do we do? Throw out the Proteon box? Forget Arpanet?
     Is this a catch-22 situation?

                                           Bob Dixon
                                           Ohio State University

     -------
     -------

brescia@CCV.BBN.COM.UUCP (02/19/87)

First, let me apologize to the whole list for sending out the previous
message.  It slipped through my fingers while trying to reply.  (An apology is
a bad thing to begin a letter with.)

Bob,
There are two main ways to connect to a PSN at 'level 1', the electrical level.
There is 1822 DH, which is good up to about 1000 feet, and there is 'modem'
which may be RS232, V.35, RS422, and possibly others.

If the arpanet PSN is not in your building, and you cannot get one installed
in your building, you will need some sort of modem connection.  As H.Weiss
pointed out, you could use ECU's to turn the modem line into a DH connection
at your end and at the PSN, but ECU's are impossible for DDN to monitor and
the modem line is also hidden from monitoring also.  

The PSN modem connections are based on HDLC, and can use HDH or X.25 ("DDN
Standard X.25").  You want to see if Proteon will support either of those
protocols.  

Disclaimer:
This is a statement from a PSN user; I run gateways, not PSNs.  I do not
speak for DDN or the PSN support group.

    Mike

Mills@UDEL.EDU.UUCP (02/19/87)

Bob,

Faced with a similar problem, we feel the strategy of choice is to use
Standard X.25 and beat up Proteon for its support. Rumor is circulating
that Proteon may have support for that in beta test maybe in a month.
However, you may wish to buck your problem upstairs via your ARPANET
sponsor and squeal like stuck pig.

Dave