2 Mar
2026
2 Mar
'26
6:50 p.m.
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.
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
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.