This is what Mark configured on his RSX11M system. It's duplicated several times for other incoming connections. I assume they work.On Mar 2, 2026, at 12:46 PM, John H. Reinhardt <johnhreinhardt@thereinhardts.org> wrote: On 3/2/2026 10:44 AM, Johnny Billquist wrote: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. JohnnyThat 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? JohnnyBecause 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.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 _______________________________________________ HECnet mailing list -- hecnet@lists.dfupdate.se To unsubscribe send an email to hecnet-leave@lists.dfupdate.se
-- John H. Reinhardt PRRT&HS #8909 C&O HS #11530 NRail (NTrak) #54979044 (7566)