HECnet August 2022

hecnet@lists.dfupdate.se

13 participants
6 discussions

by Paul Koning

Gents, It's been a while since I sent out the T1.1 beta 2. I had collected a number of cleanups and bugfixes as well as some doc updates. I don't know how many are using this release; I see one in the mapper but there might be more for all I know. Earlier today I committed those pending improvements and created a new "T1.1 third beta" kit. You can get that code from the Subversion server: svn://akdesign.dyndns.org/pydecnet/branches/t1.1/pydecnet or alternatively from the Downloads link on the mapper website: http://akdesign.dyndns.org:8080/resources/public/index.html I'd like to do the V1.1 release reasonably soon, so I'd appreciate any feedback from people who have tried the beta (the earlier version or this one). paul

2 years, 1 month

HOWTO for VAX/VMS DECnet-Plus open_simh HDLC support and P.S.I.

by Trevor Warwick

I recently added HDLC framing support to the DUP11 and DPV11 devices in open_simh. This has only so far been tested with DECnet-Plus on VMS. I wrote up another couple of examples, showing how to use HDLC as a DECnet datalink, and also how to try a basic configuration of VAX P.S.I. for X.25 communication. They're here: https://notlikethatlikethis.blogspot.com/

2 years, 3 months

Linux NRT configuration message

by Thomas DeBellis

In my changes to Kermit-20 and SETHOST, I check the configuration byte to make sure that I'm communicating with either a Tops-10 or Tops-20 system. If it's not one of those, then I want to give a nifty, informative error message, such as: Kermit-20>connect APOLLO:: ?VMS type systems do not support Tops-10/20 NRT communications. Kermit-20>connect MIM:: ?RSX-11M type systems do not support Tops-10/20 NRT communications. Kermit-20>connect TRON:: ?RSTS/E type systems do not support Tops-10/20 NRT communications. Pretty nifty. I do this by doing a lookup into a handy table, indexed by the OS type, viz: hsttyp: eascii <RSTS> ;^d0 eascii <RT-11> ;^d1 eascii <RSTS/E> ;^d2 eascii <RSX-11S> ;^d3 eascii <RSX-11M> ;^d4 eascii <RSX-11D> ;^d5 eascii <IAS> ;^d6 eascii <VMS> ;^d7 eascii <TOPS-20> ;^d8 (TOPS20) eascii <TOPS-10> ;^d9 (TOPS10) eascii <RTS-8> ;^d10 eascii <OS-8> ;^d11 (!!) eascii <RSX-11M+> ;^d12 eascii <MCB> ;^d13 (the DN20!!) hsttyn=.-hsttyp-1 ; Number of defined operating system types So if the number I get is outside of this range, I give an unknown error, such as: Kermit-20>connect ZITI:: ?Remote system sent an illegal configuration message ZITI:: shows as a Linux system. Does anyone know what its configuration byte would be? How about Windows? Ultrix? Any others? I don't recall whether we used NRT or CTERM to get into our Ultrix machine (it was an 8650, consequently upgraded to an 8700). I think we used TCP/IP TELNET.

2 years, 4 months

issues with stupi's email gateway...

by Mark Abene

Hey Johnny, I recently installed DECmail-11 on RSTS the other evening, and I'm noticing some undesirable behavior with the mim.stupi.net email gateway going out from inside HECnet. Firstly, it's worth mentioning that gmail won't accept a recipient address with colons in it, unless you put double quotes around it. For example: MARDUK::PHIBER@mim.stupi.net ...won't be accepted as a recipient, and the message is immediately red-flagged in gmail. However, if you do the following: "MARDUK::PHIBER"@mim.stupi.net ...gmail accepts and delivers it, MIM relays it correctly, and I receive the email in RSTS. Nice. Unfortunately, the reverse is failing. If I respond or send mail out from DECmail, mim.stupi.net's sender address rules reject the message: This is Postmaster <MIM::POSTMASTER> at MIM::. I'm sorry, but I could not deliver your mail. An error occured while trying to send it, and I cannot recover. Orignal recipient was "PHIBER(a)PHIBER.COM" Actual error is: Fatal address error. Additional information: 5.1.7 The sender address <MARDUK::PHIBER@mim.stupi.net> is not a valid 5.1.7 RFC-5321 address. h19-20020a05651c125300b0025e725ef592si33185ljh.300 - gsm tp Please let us know if you can correct the sender address restrictions on mim. I tried with quotes, but that didn't help either. :) Thanks, Mark

2 years, 4 months

Fwd: DECnet to be dropped from Linux

by John H. Reinhardt

Possibly already known, but just in case... -------- Forwarded Message -------- Subject: [cctalk] DECnet to be dropped from Linux Date: Tue, 2 Aug 2022 12:39:21 +0200 From: Liam Proven via cctalk <cctalk(a)classiccmp.org> Reply-To: General Discussion: On-Topic and Off-Topic Posts <cctalk(a)classiccmp.org> To: General Discussion: On-Topic and Off-Topic Posts <cctalk(a)classiccmp.org> https://www.phoronix.com/news/Linux-DECnet-2022-Removal https://lore.kernel.org/lkml/20220731190646.97039-1-stephen@networkplumber.… -- Liam Proven ~ Profile: https://about.me/liamproven Email: lproven(a)cix.co.uk ~ gMail/gTalk/FB: lproven(a)gmail.com Twitter/LinkedIn: lproven ~ Skype: liamproven UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053

2 years, 4 months

Re: DECNET-Plus and X.500

by Mark Abene

Hi Jordi, I've been using your BITXOZ as my DECdns HECNET nodename resolution server for OpenVMS for at least eight years (since you put it up), but it seems that area 7 went offline fairly recently. Is everything ok? Regards, -Mark On Sat, Apr 26, 2014 at 2:56 PM Jordi Guillaumes i Pons < jg(a)jordi.guillaumes.name> wrote: > Hello, > > I'm playing again a little bit with DECNET/OSI. Does anybody have the X500 > directory server install kit at hand? The PAKs are included in the hobbyist > set, but the CSD I have is the 1992 one so I guess there has to be a more > recent one (for VAX, by the way). The DECDns stuff changed from 6.X to 7.X > so I'm pretty sure the version I have in my CDs won't work. > > By the way, BITXOZ is configured as a DECDns server, and "owns" the > HECNET: namespace. All HECNET nodes are loaded in the form HECNET:.NAME. I > toyed previously with a schema like HECNET:.AREAn.NAME but I have ditched > it. My internet domain (jguillaumes.dyndns.org or jordi.guillaumes.name) > has also opened the access to BITXOZ via rfc1006, so anyone with a > DECNET/OSI stack shoud be able to do a $SET HOST jguillaumes.dyndns.org > or a $DIR/APP=FTAM jguillaumes.dyndns.org:: and access that system even > without a working HECNET link. > > Jordi Guillaumes i Pons > jg(a)jordi.guillaumes.name > HECnet: BITXOV::JGUILLAUMES > > > > >

2 years, 4 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet August 2022