The biggest issue I don't understand here is why.
If you tunnel a serial port, you tunnel a serial port. DDCMP is totally invisible to you.
You will not learn, or need to understand anything about DDCMP for this. A serial port
sends bytes. You pass those bytes one. Everyone is happy.
What kind of protocol is implemented, using those bytes, are very invisible and irrelevant
to the tunnel, just as it is to a cable.
You might as well tunnel SLIP, or PPP. It will work just the same.
They are all just implementing a network layer on top of a serial connection.
What are you really trying to accomplish?
Johnny
On 2012-01-01 01.57, The Presence wrote:
Bob,
I really am wanting to use DDCMP for learning purposes. I want to build
a decnet phase IV network with DDCMP, however, I want to also have the
ability to pass traffic through to connect to additional nodes that are
net connected.
Kevin
------------------------------------------------------------------------
To: hecnet at Update.UU.SE
Date: Sat, 31 Dec 2011 16:41:02 -0800
Subject: Re: SV: RE: [HECnet] Hecnet and DDCMP
From: bob at
jfcl.com
What is it that you actually want to connect? For the most part, a
Multinet link simulates the "user experience" of a DDCMP connection
tunneled over IP. Multinet is a point-to-point DECnet circuit which,
except for the device names, is functionally identical to any DDCMP link.
The only reason I can see for using a real DDCMP serial connection
(either sync or async) would be to connect a machine that didn't support
an Ethernet interface.
Bob