2 Mar
2026
2 Mar
'26
7:10 p.m.
On 3/2/2026 11:50 AM, Paul Koning wrote:
This is what Mark configured on his RSX11M system. It's
duplicated several times for other incoming connections. I assume they work.
.;
.; Inbound Connection for John Reinhardt
.;
MNC SET CIR IP-0-5 MODE DDCMP
MNC SET CIR IP-0-5 TCP HOST 0.0.0.0:0 PORT 7728
NCP SET CIR IP-0-5 STA ON
MNC SHO ALL
And this is what I put in my pyDECnet config file:
#
# Circuit to Mark Matlock
#
circuit DDCMP-30-1 DDCMP tcp:60001:rsx11m.com:7728 --t3=15 --cost=9
This is based on the circuit documentation plus a config file I got from Supratim last
year which has quite a few DDCMP connections.
On Mar 2, 2026, at 12:46 PM, John H.
Reinhardt<johnhreinhardt(a)thereinhardts.org> wrote:
On 3/2/2026 10:44 AM, Johnny Billquist wrote:
PyDECnet is
basically omnilingual. So you need to find out what line protocol the other end uses and
then configure PyDECnet to match. If the other side runs Multinet, you'd configure
that (making sure to set the directions correctly: one is originating, the other
incoming). And don't use Multinet over UDP unless nothing else is available, because
it is an utter crock. Hm. The command "MNC SET CIR IP-0-5 MODE
DDCMP" should have given a warning that this has been deprecated. In essence, it does
nothing.
All links are just multinet links, which is DDCMP, with a small header to just get whole
packets when using TCP.
Johnny
That explains the "MLTNET" in Marks error log. So, if I set up the
phDECnet circuit as a Multinet one is should work?
On 02/03/2026 17.38, Johnny Billquist wrote:
> I don't think I've ever tried that DDCMP mode. I don't even remember what
it does...
>
> Why are you wanting to use it?
>
> Johnny
>
Because that's what I was told needed to be done to connect to other
HECnet nodes? Mark has several set up that way and so does Supratim. I generallly suggest DDCMP because it works well, but
lots of other options have been used. Some of my preference comes from history; for
example I tend not to use Ethernet (or GRE, basicallly the same thing) for "wide
area" use because it's a LAN and back when it wouldn't work for WANs.
Nowadays the Internet is so fast that it's a reasonable option in many cases (though I
would still hesitate to run it on a trans-Atlantic circuit).
paul
_______________________________________________
HECnet mailing list --hecnet(a)lists.dfupdate.se
To unsubscribe send an email tohecnet-leave(a)lists.dfupdate.se
--
John H. Reinhardt
PRRT&HS #8909
C&O HS #11530
NRail (NTrak) #54979044 (7566)