HECnet

hecnet@lists.dfupdate.se

6 participants
15595 discussions

by Johnny Billquist

I've been busy with my silly things as usual, and lately implemented a FINGER client and server for RSX, and I realized there are a couple of things to maybe check with other people on HECnet. First of all - finger as such is a (sortof) well known tool/service on the TCP/IP internet. And I've had a finger server and client for TCP/IP under RSX for a long time, but have never really shared it, since it was a bit "odd". But even before this, I knew of a FINGER implementation available from DECUS for RSX. I've known that I wanted to make FINGER available for others for a long time, but recently I started thinking of also adding in DECnet capability in my finger implementation. So the last few weeks I've been tinkering with this, and I've finally completed the work and made my new finger implementation available as a package. The FINGER from DECUS mentions the following: FINGER is a utility to display information about a selected user or group of users. It can be invoked for users on the local node or on a remote node over DECnet, and is com- patible with the VMS implimentation of FINGER. Full function- ality requires an RSX-11M+ system with resource accounting and DECnet. So, not only have there been this RSX implementation from DECUS, there apparently also exist(ed) an implementation from somewhere for VMS. FINGER over TCP uses the well known TCP port 79, while the DECUS RSX (and I assume VMS) DECnet implementation uses object number 117. My implementation then responds to both these access paths, as well as being able to query locally, and also try to connect to remote systems using either of these methods. And I now have this running on MIM:: So my questions are: . Do anyone else have any finger service running on any HECnet node? . Do anyone else know what other implementations even exist, and for which OSes? I do think FINGER is somewhat useful to find who might be logged in and active, as well as finding out more information about people on different systems in general. On the internet, finger servers are nowadays unusual to see, since privacy and security concerned people just feel that finger gives out way too much information anonymously. So I am not encouraging people to run this if they have such concerns. But like I said, personally, I do find it useful, and will keep it available on any RSX system that I am running. Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt(a)softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

1 year, 8 months

Tops-20 Kermit Version 5.3(255)-5 Maintenance Release Announcement

by Thomas DeBellis

Version 5.3(255)-5 incorporates additional features, enhancements and fixes since the minor release of 5.3(248)-5 in November 2023. These are as follows and can be identified in the code with the edit number as the prefix of a comment. [249] Implement relative directory connect [251] Emit new directory name when either wildcarded structure or directory changes [252] Fix some of the directory parsing logic to properly handle .CMDEV and .CMDIR [253] Fix ^A to print the number of pages sent and the total; was always omitting total [254] Implement CDUP, generic 'G' [255] Make CWD accept ".." as token for Unix, DOS, Windows, and OS/2 CDUP The changes were mainly driven to simulator relative directory connection as Tops-20 directory punctuation (I.E., '<' and '>') can too easily be confused with piping requests on some Kermit clients. On some, it proved impossible to convince them otherwise... Generic 'G' is an addition to the Kermit protocol. C-Kermit currently implements this in addition to Tops-20 Available for ANONYMOUS NFT from VENTI2:: and from https://www.kermitproject.org/kermit-20.html.

1 year, 8 months

Re: hii guys..tops20 expert needed

by Anders Andersson

"merlyn drforbin" <kropotkin(a)gmx.com> wrote: >Any way to set endpoint buffer size on panda decnet phase IV Could some of this (in SYSTEM:7-CONFIG.CMD) be what you are looking for? This is from RARITY (not PANDA, but DEC vanilla distribution,kind of), I'm not sure I have the correct values myself, been experimenting. ; DECnet parameters: ;default is DECNET BUFFER-SIZE 576 decnet buffer-size 1476 ;default is DECNET MAXIMUM-BUFFERS 80 ;decnet maximum-buffers 40 -- Anders Andersson, Uppsala, Sweden

1 year, 8 months

PyDECnet V1.1.0 released

by Paul Koning

Gentlepeople, The regular release of V1.1.0 is now published. You can download it from http://akdesign.dyndns.org:8080/resources/public/index.html . The code in Github is up to date, and the "main" branch has been updated to the V1.1.0 code. The "t1.1" branch is now retired. For those of you who have used the beta and/or release candidate releases: nothing much changed since then apart from bugfixes. If you're upgrading from V1.0, please be sure to read the documentation, in particular the CHANGES.txt file. A notable change that may affect your configuration files: f. The --api and --insecure-api switches on the "http" configuration line have been removed. Instead, API control is via a new "api" line. See doc/config.txt for details. paul

1 year, 8 months

hii guys..tops20 expert needed

by merlyn drforbin

Any way to set endpoint buffer size on panda decnet phase IV

1 year, 8 months

tops10 decnet

by merlyn drforbin

Hey guys. just got tops10 7.03 kinda working on hecnet. I'm still not able to set host to rsts and communication to from the node is spotty! Any suggests. Thank you in advance

1 year, 8 months

PyDECnet release candidate 2

by Paul Koning

I just released PyDECnet 1.1 rc2. You can find kits at http://akdesign.dyndns.org:8080/resources/public/index.html (the "V1.1 release candidate 2" lines are it). This contains a few bugfixes; a notable one makes HTTPS for the embedded web server work if you're running Python 3.12 or later. (Thanks Wilm!) I did a major rewrite of the "api-connecors.txt" documentation file, so now the recommended "Connectors" mechanism for writing PyDECnet applications and accessing its API should be a lot more useable. Barring surprises I'll probably issue the final V1.1 release in a week or so. paul

1 year, 8 months

auto launching pydecnet at boot?

by Mike Kostersitz

I am running my pydecnet router on a Raspberry Pi Zero W2 After switching to the beta/preview version the daemon does not start automatically when the Pi boots Do I need to make additional changes to enable that again? I don't remember from setting up the stable version anymore. Mike

1 year, 8 months

tops20

by kropotkin

Anyone help me get tops20 panda up on decnet(hecnet)?

1 year, 8 months

Announcing TCP/IP V2.15 for RSX-11M-PLUS

by Johnny Billquist

Time for a new release announcement of TCP/IP for RSX-11M-PLUS. This is version 2.16 of BQTCP/IP. Highlights: . Fixed an issue in TCP, where if the system is severely loaded, a TCP socket could get stuck. . Fixed DNS resolver issues that could create problems at boot time, if DHCP was taking time to get a configuration. . Fixed various issues in MAIL/MAILD. . Improved logging in many daemons. Detailed information on things that have been done since the last release: UDP: . Improved UDDRV IO timeout handling. TCP: . Bugfix. If we run out of IPPOOL when doing a TCP transmit, that socket can get stuck. We need to retry allocation later. DNS: . Change resolver to just handle if no IP is known to have DNS resolving fail, and each time requested, try and figure it out. . If resolver starts up and we do not have an IP addres, make sure resolver exits again. BQTLIB: . Updated BQTLIB documentation, PDP-11 C AIO functions. . Added asynchronous I/O handling to PDP-11 C in bqtlib. . Reworked DECnet access in PDP-11 C significantly. . Bugfix in C DECnet library. Connection block setup used the wrong format codings, leading to connection failures to some operating systems. This affected MAILD. MAIL/MAILD: . Fixed mail reader handling when at end or beginning of mails. . Bugfixes in DECnet mail handling. . Rewritten DECnet handling in MAILD to use new API from BQTLIB. . Improved MAILD error handling for many situations. . Added session id in locally received mail logs. . If MAILD sends mails using SMTP, and the remote side close the connection during a session, we should reopen the connection for the next mail to be delivered. . Improved MAILD logging. In some situations, the wrong network error code was logged. LPT: . Added the ability to select what is the default form for LPT despooler via the queue form parameter. MLTNET: . Changed MLTNET to do immediate ACKs, to improve performance if other end is using nagle. FTPD: . Added task name to FTPD console log entries. . Improved FTP/FTPD file handling to ensure created files always have at least RD protection for user and system. HTTPD: . Trim out binary data from HTTPD error log. TELNETD: . Added TELNET$LOG logical for if telnetd should be logging. . Improved TNC2 task to also understand result from RT: . Improved TNC2 task to also understand result from HT: IFCONFIG: . Added allocation fail statistics to IPPOOL. IPGEN: . Bugfix in IPGEN. C header files should be installed to PDP11C$INCLUDE: if it exists. NTP: . Bugfix in NTP building. It was referring to $TMADJ, which might be a non-existing symbol. Some additional notes: As usual, I would recommend people to update as soon as possible. The changes are somewhat critical, but will also lead to a much better experience. The patches to the TT: driver cannot be applied automatically, but requires users to apply the patches themselves, and then run SYSGEN to generate a new system. Once added, the TNC2 task can be run at login, and will define logical names for the user telling where he is connected from, if using telnet or LAT. TNC2 can get information about remote connections over DECnet as well, but this requires updates to DECnet. Such patches are not available separately at this time, but are included in the RSX image provided from Johnny Billquist. The TT: driver patches also allows the updated MCR to give more information with the DEV command (SHOW TERMINAL in DCL). The patched TT: driver also makes is possible to get telnetd fully vectorized, as this version provides two more addresses that are required by telnetd to access information in the kernel. The other patches to RSX can be applied automatically by IPGEN, either if used interactively when answering YES to the question about applying RSX patches, or by running IPGEN explicitly to do the patches, with the command: @IPGEN PATCH Specific information about the patches: LAT: Fixes a memory leak, and adds the ability to read where a terminal connection comes from when using LAT, using SF.GMC. RMSDAP: Fixes a bug in getting the file protection, so the XAB gets filled in correctly for remote files. RMSDSP: Fixes that some numbers were displayed in signed octal, which should have been displayed in decimal or unsigned octal, depending on number. DCL: Added terminal attributes for COLOR. MCR: Too many fixes to be listed here... INS: Fixes that users cannot circumvent protection on common regions. HEL: Fix that users can login with session ID, or with directory, in addition to name and UIC. ACNT: Add no password change attribute to accounts. PSW: Add no password change handling. SYL (SYSLOG): Add terminal idle tracking on accounts without idle logout. ECL: If the receiving machine is very slow, and the sending machine is very fast, and the receiver announce several large buffers available, ECL cannot keep up, and drops packets. This is a problem with the DECnet flow control, as it is used in RSX. The simple solution is to allow more outstanding buffers when receiving. A more complex solution would be to change how RSX DECnet do flow control, but that would require rewriting a fair chunk of the ECL module. NMVACP: Fix handling of "show known nodes" command, which could skip some nodes. NVP: Add ability to use session ID or directory name for user identity in DECnet nodename specifications. EPM: Fix handling of ethernet multicast. NTDEMO: Fix that hosts without names should display DECnet address. NCP: Parse of additional information types in NICE messages. As usual, the distribution is available from: ftp://mim.stupi.net/bqtcp.dsk ftp://mim.stupi.net/bqtcp.tap !!! BQTCP is also available through RPM !!! (As an additional note, if there are any problems communicating with Mim using port 21, the ftp service is also available at port 10021) The documentation is also available through ftp on Mim, or also at http://mim.stupi.net/tcpipdoc I hope people find this update useful. Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt(a)softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

1 year, 8 months

← Newer
1
...
4
5
6
7
8
9
10
...
1560
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet