HECnet

hecnet@lists.dfupdate.se

3 participants
15583 discussions

by bqt＠softjar.se

Time for a new release announcement of TCP/IP for RSX-11M-PLUS. Highlights: This release have some rather significant work done on the mail system. There have also been some minor improvements on TCP, HTTPD, FTP and libraries. Detailed information on things that have been done since the last release: TCP: . Improved retransmission handling at Fin Wait 2. . Correct keepalive handling at Fin Wait 2. . Improved processing at socket close. TCP sockets should do keepalives, and not probes when in Fin Wait 2. Libraries: . Corrected program section attributes on some modules in BQTLIB, so that they work correctly also on overlaid programs. . Bugfix in BQTC library. Recent changes to quadtime to string conversion had introduced a potential buffer overflow error. FTPD: . Change FTPD read command processing to avoid a race condition. HTTPD: . Reworked logging routines to fix some performance issues. . Bugfix in IND forms library for CGI scripts. MAILD: . Changed mailbox format for better performance. . Changed location for mail spool file. . Added checking for /NOBRO for new mail announcements. . Increased stack size since the task sometimes ran out of stack. . Reduced static data memory use. . Changed overlay scheme to make more memory available. . Added various error checks in the code. . Changed usage so all queue operations requires a user with privileges. . Added label handling for mails. . Added copying of sent mails to self. . Improved error mail generation in MAILD. . Added mail size information to mails. . Added conversion tool for old mailboxes. *** Important notice about MAILD *** The changes to MAILD are not seamless. When installing the new version, the mailbox update program should be run, in order to upgrade all user mailboxes to the new mailbox format. The task for this is MBXUPD.TSK. There are no issues with running this task several times. A mailbox that has already been updates will not be modified anymore by the update task. The location of the mail queue file have moved. After installation, you could just move the mail queue file over to the new place, or else re-initialize the mail system. The mail queue file name is MAILQUEUE.DAT, and it was previously located at MAIL$:, but it should be moved to LB:[1,7] instead. Once the mailboxes have been updated, and the mail queue file have been moved/recreated, the mail system have been updated, and you are ready to use the new mail system. *** Important notice about MAILD *** 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. While there are no really critical issues that have been solved, I still recommend people to update, since this new version do contain improvements that are beneficial and as far as I know there are no issues or problems updating to this newest version. 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

6 years, 4 months

HECnet and LCM+L

by Keith.Halewood＠pitbulluk.org

Hi, Just a quick question - has anybody (else) approached the Living Computers Museum and Labs (in Seattle) with regard to getting their VAX (Rosie) and/or other DECnet-capable kit onto HECnet? Not so long ago, they 'hid' their systems behind a ssh gateway because of the number of attacks they were suffering via telnet. It makes it rather difficult to move code onto Rosie... well, perhaps more inconvenient than difficult, especially if all I want to copy are binaries. Just asking... Keith

6 years, 4 months

Decnet on RSX-11

by kurt＠hamm.me

So, I added this command to the startup.cmd: @LB:[IPNET]INS.CMD. I didn't modify the file yet. I wanted to see what it would do The result after rebooting was this: >INS LB:[IPNET]MLTCOM/UIC=[1,54]/PRO=[RW,RW,,] >INS LB:[IPNET]MLTNET >INS LB:[IPNET]MLTCFG >NCP SET PROC IP TOP NCP -- Set failed, unrecognized component, Process >NCP SET LIN IP-0-* ALL NCP -- Set failed, invalid identification format, Line >MNC SHO VER Initialize common NT.IP not found. Exiting... >MNC SET CIR IP-0-0 TCA HOST MIM.UPDATE.UU.SE:7705 PORT 0 Initialize common NT.IP not found. Exiting... >NCP SET CIR IP-0-0 STA ON NCP -- Set failed, invalid identification format, Circuit There are lots of errors, so I am not sure where to start. Any advice would be appreciated. Kurt

6 years, 4 months

Multinet Mail

by kurt＠hamm.me

I wasn't sure where to post this question, so I thought I would start here. I have two simh vax3900 machines. Larry and Moe. Larry is the HECNet router for Moe. When I send email from Larry (via SMTP), the *return *email address is correct (SYSTEM at LARRY.MYDOMAIN.COM. When I send email from Moe (to LARRY::SMTP%"user at domain.com"), the return email address is: SYSTEM at SCSSYSTEMID.MYDOMAIN.COM. Why is Moe using the SCSSYSTEMID instead of the system name? *I am missing something.* *Kurt*

6 years, 4 months

GRE Peering

by tomas＠prybil.se

Dear fellow HECNETers I?ve been using Johnnys bridge for a year or so, (thank you Johnny!) and wanted do some additional networking. Before going full gre peering is there anyone out there that could act as intermediate peer to do some testing while I try not to break anything (!) On my side I have good network connectivity, but unfortunately no static IP :/ The box I?m using is a 2610XM with ios ver 12.4 Happy if anyone is willing to share their connectivity BR /t

6 years, 5 months

Linux-DecNet and DecNet for DOS

by gregg.drwho8＠gmail.com

Hello! Right now I am busily trying to get an installation of the Linux for DecNet code to work on Slackware-11.0 Linux. The end result there would be to have it talk to a terminal server, a Model 90L design in fact. The last time I tried this out it was on a dedicated card wearing a COAX connector, and in a different machine, again running Slackware-11.0. It was being uncooperative then. The terminal server that is. However I have here both versions of DecNet for DOS that were released via BitSavers, would any of you know if these individuals running inside DOSBox would besides working, want to connect to the previously described Linux application? I figure if I can get that to work, I can sort out the details for the currently related problem. Incidentally I am also seeing if I can get that stuff to build properly on this laptop inside the WSL instance of SLES12SP3. That way I can take my problems to my hacker community meetings. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again."

6 years, 5 months

Event Announcement: DEC Legacy is back on 9th-10th Nov 2019, Windermere UK

by mark＠wickensonline.co.uk

There will be machines connected to HECnet there this year! Please visit http://wickensonline.co.uk/declegacy/ for more details. Mark.

6 years, 5 months

DECnet on Ubuntu 14.04

by bob＠jfcl.com

Can anybody tell me the secret to making DECnet work on Ubuntu 14.04 (Precise)? Yes, this release is out of date but it's the one I need to use for other compatibility reasons. I installed the dnet-common, dnet-progs and libdnet packages from the standard repository. I configured the /etc/decnet.conf and dnet.conf files (and I don't care about decnet.proxy just yet). Nothing seems to give an error, the dnetd daemon is running, and the MAC of my eth0 has been changed to match my DECnet address. dneigh shows the correct adjacent routing node on the network. But nothing can communicate. All the DECnet commands (sethost, dnping, etc) give "socket: no such device" errors, and all the other DECnet machines on the network think the Linux host is unavailable. I seem to remember that there was some problem with the DECnet startup with upstart, but I don't remember the details and Google isn't being helpful today. Thanks, Bob

6 years, 5 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: This release have some performance improvements, bugfixes, and additional functionality. It also includes a print symbiont for the queue manager, which spools files over TCP/IP to remote printers. Detailed information on things that have been done since the last release: IP: . Added routing capability. . Added command to IFCONFIG to enable/disable routing. TCP: . Reworked TCP retransmit strategy for improved performance. . Bugfix in TCP timeouts. Sometimes the wrong time was used. . Change to allow creation of a new port if there is an existing port which is in time wait. . Improve TCP probe logic. . Bugfix in CR mode. CR was not padded by NUL if followed by another CR. . Added PU.RBL option to TCP sockets, for reading without blocking. . Bugfix in daemon creation. TCP could create more daemons than it was allowed to. TELNETD: . Added a shorter timeout for TELNETD incoming connection establish. . Added proper handling of low pool situation in TELNETD. . Bugfix in option processing. "Don't binary" option was not handled right. FTP: . Bugfix in FTP. Checking for existing file to not overwrite files at MGET incorrectly caused some transfers to not proceed. . Bugfix in FTP. PASSIVE command responded with the wrong message. . Bugfix in FTP. The initial connection from command line caused FTP to enter wrong transfer mode if the remote system was RSX. . Bugfix in FTP. The keepalive command in an INIT file caused the processing of the INIT file to abort. FTPD: . Improved statistics output at connection close. MAILD: . Improved performance. . Improved robustness of SMTP receive processing. . Changed mail queue format for better efficiency. . Fixed MAIL11 sending. Nonexistent node is a fatal error. . Increased stack size of MAILD task to avoid some crashes. NTPDATE: . Bugfix. If local time offset was too far from UTC, NTPDATE failed to correctly adjust time because some arithmetic was done with 16-bit integers. LPT: . Added new LPT spooler that runs under the queue manager. XLISP: . Added another example program. Libraries: . BQTLIB - Fixed checking for disabled accounts. (This affected FTPD). . IPC - Fixed sclose(). This function leaked file descriptor. Distribution: . Added SLIPACP and DLXACP. Both are to be considered very experimental, and might crash the system. But if someone is interested in SLIP, or IP over DDCMP, please contact me for more information. . Fixed generated IPINS.CMD file to work if CLI is not MCR. . Added default for LINE question in IPGEN. . Added two forgotten files with HTTPD server. . Added [1,1]DAPSLX.ODL, which should have been on RSX distribution. . Added RSXERR.MSG to distribution. *** A special note on the routing capability in BQTCP/IP: This functionality have been added since it might be needed if more interfaces than the standard ethernet and loopback is configured. This is at the moment very experimental, in the form of SLIP and DDCMP lines. If you do not use more than ethernet for external communication, you should not enable IP routing on the RSX host, as it is considered bad practice to have hosts in general do routing. 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. While there are no really critical issues that have been solved, I still recommend people to update, since this new version do contain improvements that are beneficial and as far as I know there are no issues or problems updating to this newest version. 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

6 years, 6 months

Why does MIM not list 23.1023 as a known node?

by supratim＠riseup.net

A GRE tunnel up from 31.1023 to 23.1023; area 23 nodes are reachable through it, but 23.1023 does not show up in the known nodes list of another router (31.1, openvms 7.3) in the same local network. Both 31.1 and 31.1023 are L2; and 31.1 is connected to MIM via MULTINET. 23.1023 does not show as known to MIM either. But MIM and 31.1 do know about area 23 nodes piglet, owl, rabbit etc. How is 23.1023 going stealth? --------- |31.1 | |IMPVAX |---Multinet/TCP---HECnet --------- | | ----------------- | Bunch of | | Area 31 nodes | ----------------- | | --------- |31.1023| |IMPRTR |---GRE Tunnels to other areas --------- Tunnel from 31.1023 to 23.1023: Area Cost Hops Next Hop to Node Expires Prio *23 4 1 Tunnel23 -> 23.1023 42 64 A+

6 years, 6 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet