HECnet

hecnet@lists.dfupdate.se

5 participants
15580 discussions

by bob＠jfcl.com

I have switched from using LEGATO as the area 2 router to using Paul's pyDECnet router instead. I'm very impressed - it doesn't run under VMS, but other than that pyDECnet does pretty much everything you could want to do with DECnet or HECnet all in a single package. It only took me a couple of hours to get it all set up, and it can manage all the Multinet links and the one "Bilquist Bridge" link that were formerly attached to LEGATO. The new router for area 2 is (what else?) A2RTR, 2.1023. Johnny, please add this node name to your database. LEGATO is still there, but it's been demoted to an L1 router and it doesn't do anything now except route between HECnet and the real, physical, machines in my house. For the people who were/are connected to LEGATO there should be no real difference except that you'll now see A2RTR on the other end of the link instead. Everything else should work as before. Let me know if you find some problem. And a special thanks to Paul and Supratim for answering my silly questions and helping me set it up. Bob

5 years, 6 months

Decnet over internet

by roll＠Stupi.SE

I would not recomend DDCMP over TCP, as you have no idea what the TCP implementaion does for timers etc and TCP is streams, you need to identify the packet boundaries. DDCMP over UDP gives DDCMP full control over retransmit timers etc for making the connection reliable and what the actual netwrk is doing is visible to the DDCMP layer. -P

5 years, 6 months

Decnet over internet

by roll＠Stupi.SE

May I suggest sometng ugly, but not violating any layers, DDCMP over UDP. -P

5 years, 6 months

Decnet over internet

by wilson＠dbit.com

From: Peter Lothberg <roll at Stupi.SE> >May I suggest sometng ugly, but not violating any layers, >DDCMP over UDP. For what it's worth, Ersatz-11 (my PDP-11 emulator) also supports DDCMP over UDP, and I don't consider it ugly at all -- it's a very neat fit. (E11 can also use TCP, or actual real async DDCMP over serial lines, and there are the beginnings of support for DDCMP on sync lines too but usable hardware for that is rare.) John Wilson D Bit

5 years, 6 months

pydecnet zero counters

by wboerhout＠gmail.com

I am happily running an instance of pydecnet (1.0-486) to connect my simh VAX cluster and various other stuff to HECnet (ONAPI4 29.206) For management purposes, I'd like to periodically zero the line/circuit/node counters on ONAPI4, but the node does not respond to the "NCP tell ONAPI4 zero <xxx> counters" commands. Looking at the python code, I saw some hints bit I can't get my head around how to do this, either using the pydecnet api or remote NCP Any help here? *Wilm*

5 years, 7 months

Bridge

by bqt＠softjar.se

I just wanted to alert people that I rewrote parts of the bridge code recently. The code was very old, and it started to have problems on some platforms because of the very ancient way it made use of the pcap library. So I finally bit the bullet and rewrote it to make use of the pcap library it is supposed to be used these days. This not only removed some bugs/issues, but it also allowed me to remove some conditional code for different OSes. In addition I also introduced some other changes that others have contributed, making it hopefully a little nicer to use. The bridge tarball can be found on: http://mim.update.uu.se/hecnet or http://psilo.update.uu.se/~bqt/hecnet Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

5 years, 7 months

ISO Jnet NJE Manager's Guide

by supratim＠riseup.net

Hi all, Does anyone happen to have a digitized copy of "Jnet NJE Manager's Guide" from Wingra Technologies? This applies to Wingra's JNET for VMS product, version 3.6 (or 3.5 or 3.7) which connects VAX/VMS systems to IBM Mainframe networks using NJE over DECnet or TCPIP. Thanks, Supratim -- Supratim Sanyal, W1XMT 39.19151 N, 77.23432 W QCOCAL::SANYAL via HECnet

5 years, 7 months

Announcing TCP/IP for RSX-11M-PLUS

by bqt＠softjar.se

Time for a new release announcement of TCP/IP for RSX-11M-PLUS. Highlights: . The installation and configuration tools have been totally rewritten to make it easier to use for novice people, while at the same time making updating and customization easier to to do. (*** IMPORTANT, READ NOTE AT BOTTOM OF MAIL ***) . MAIL now have an API for access from programs both to read and send mail, and also hooks to have a program run when new mail is received. Detailed information on things that have been done since the last release: Installation and configuration: . Totally rewritten scripts to configure and install BQTCP. (*** IMPORTANT, READ NOTE AT BOTTOM OF MAIL ***) TCP: . Improved TCP ACK handling. Fast to slow machine caused excessive ACK packets to be generated. . Correct TCP daemon accept so that two different requests with the same source and destination, but different sequence numbers don't end up creating two sockets. . Correct ACK # if doing an RST to a SYN, which could be wrong. . Improve handling of duplicate Syn in Syn Recv state. . Improved TCP receive window update strategy. . Bugfix in TCP ICMP error handling reception. Improved handling of problems during TCP Syn Sent state. . Rewritten TCP retransmit and congestion avoidance logic to better match RFC 5681. . Improved TCP retransmit and FIN logic. . Improve TCP Nagle. Under some circumstances, it failed to perform. SPOOF: . Added address exception handling for spoof. MAILD: . Improved MAILD local list handling and SMTP DNS lookup error handling . Correct MAIL address rewriting rules when transitioning between protocols. . Added in MAIL that just a number as command means read that mail. . Improved MAILD address rewrite logic, and smtp sending to better handle various error situations. . Bugfix in MAILD. CC could accidentally be set for mails under some circumstances. . Added handling of in-reply-to and references in MAIL. . MAIL have been split into a mail queue manager (MQM) and a mail reader (MAI). . Bugfix in MAILD. Unprivileged users did not work right. . Bugfix. MAILD didn't enable privs before trying to send notifications, causing them to sometimes fail. . MAILD didn't turn on privs before entering mails in the mail queue, causing this to sometimes fail. . Added API for user programs to easily access mail box. . Added API for programs to be run when mail is received. . Added API for programs to send mails. LPT: . Bugfix in LPT. Symbiont did not respond to start and stop messages from queue manager. C library: . Bugfix in BQTC. RCVDW function was not working right. HTTPD: . Correct URL matching in HTTPD to not overly match wildcards. *** IMPORTANT - NEW INSTALLATION AND CONFIGURATION *** The installation and configuration scripts have been totally rewritten for this release. The main reasons are to simplify configuration for novice users, to simplify future updates, to simplify customization, and to also make it easier for expert users to change things as needed. IPINS.CMD and IPAPPL.CMD have been rewritten, and are now installed and used from the distribution. If any local customization have been done on these file in the past, they will not be applied any more. The old version of these files are kept, so you can go back and look at them and see what customization you had done. But going forward, no editing should be done to these two files. Instead there are hooks for customization available from these scripts, which should be used for any special configuration on a host. However, most normal configuration should happen through the IPCONFIG mechanism instead. Any current installation should do an update as usual by fetching and installing the new version, after which IPGEN should be run. IPGEN now will only ask a few questions, even if doing a "full" installation. At the end of IPGEN, a check is made if a configuration exists, and if not, IPCONFIG is also run. At the first update, this will be the case, so expect to have to redefine your system's TCP/IP configuration again. Any subsequent update should not require any further configuration work to be done. However, if any new configuration values are introduced, this will also be indicated at this point, and optionally, IPCONFIG will be run to correct the assumed defaults for these new values. If IPCONFIG have not been run before trying to bring the TCP/IP services up, IPCONFIG will be automatically invoked at this point as well, and if configuration is not done then, TCP/IP will not start. This also means that a system for distributing to others can be done while leaving the TCP/IP configuration undone, and it will be done at startup. As before, there is two scripts that should be invoked at system startup. IPINS, which should be invoked early in startup, but after DECnet, if DECnet is also installed, and IPAPPL, which should be invoked close to the end of the startup process. If required, configuration of TCP/IP can be redone at any time by just running LB:[IP]IPCONFIG.CMD. The current configuration will be provided as the default answers to all questions. If required, an existing config can be removed by just renaming or deleting LB:[1,2]IPPARAM.CMD. More details, as well as information about customization, can be found in the manual. *** IMPORTANT - NEW INSTALLATION AND CONFIGURATION *** As usual, the distribution is available from: ftp://mim.update.uu.se/bqtcp.dsk ftp://mim.update.uu.se/bqtcp.tap ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk The documentation is also available through ftp on Mim, or also at http://mim.update.uu.se/tcpipdoc I hope people find this update useful. Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

5 years, 8 months

Tops-20 ANONYMOUS FAL Preliminary Testing Results/DAP Query

by tommytimesharing＠gmail.com

I have been working with a kind volunteer who is using OpenVMS Alpha.? It's been quite productive. While I haven't run into any security exposures, yet, the experience has enabled me to find a few things to tweak up.? For example, the VMS logging and reporting was clearly superior to what was being put in the FAL log (which wasn't even timestamped and didn't have the requested file name). We ran into some interesting behavior.? When ANONYMOUS access is restricted to the stand-in user and its subdirectories, wildcard listing requests that are outside of that lexical scope do not report any errors but rather return zero files (none).? That was puzzling because the part of the code that did the access check was clearly doing the reject with appropriate return values. Further analysis showed that in the main loop for stepping wildcards, a reject causes the file in question to be skipped; nothing is actually done with the return values.? I believe this may be intended behavior for two reasons.? The first is that if the wildcard includes files to which the ANONYMOUS user does legitimately have access, it's friendlier to report those as opposed to stopping everything. The other reason I believe has to do with DAP itself; I don't think you can't return more than one return value per ACCESS request, even with a wildcarded file specification.? So perhaps this isn't a bug so much as an unintended consequence?? Does anybody know what the behavior should be? At any rate, I don't believe the current behavior is 'informative'.? What I'm thinking of doing is saving the last error code and returning that if the count of files returned in list is zero.? Otherwise, the user had something to look at. Do I have any volunteers who operate something besides VMS?? I'd be interested in RSX(+), IAS, RSTS and OS-8.? They never did DECnet on RT-11, did they?

5 years, 8 months

Tops-20 ANONYMOUS FAL/DAP Testing Update

by tommytimesharing＠gmail.com

VMS testing is largely complete and resulted in a number of tweaks.? This was particularly the case for logging as VMS appeared to be more productized in this area. ? I picked up a number of good ideas, most of which I've implemented.? I also had a rather glaring omission; I had completely forgotten to implement restrictions on PRINT...? There was also a problem of properly reporting error codes; in some cases, a wildcard request could come back from the 20 with no indication whatsoever that all the candidate files were rejected due to lexical restrictions.? The workaround gives a result, but apparently imperfectly (see below). RSX testing has been quite interesting.? It seems that the 20 doesn't appear have _ever_ reported month formats properly. The DAP 5.6 specification appears to be neutral in certain areas as to case sensitivity.? Most importantly, the case of a month is not made explicit, although the abbreviations are uppercase.? The 20 uses a monitor call (ODTIM%) to convert from the 36 bit internal format to text, yielding capitalized months.? So, instead of *DEC* for a month, you get *Dec*. RSX is sensitive to this and reports all dates and times as zero. It was an easy fix to uppercase everything.? Kudos to Johnny for an amazing guess in that area. Of more concern is the fact that certain results from the 20 can cause the RSX DAP client (NFT) to go into an Infinite Loop, necessitating an abort!? This is suspected to be incorrect error reporting on the 20's side.? So I've got some digging to do in that area.? I'll get to that in a few days; I had a few more access restrictions that I wanted to implement to give additional granularity. I'm hopeful for some RSTS results in the not too distant future.

5 years, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet