HECnet

hecnet@lists.dfupdate.se

15559 discussions

by Supratim Sanyal

I asked Bard to “Write a song about digital equipment corporation’s DECnet network”. The AI is surprising, the ending surreal. (Verse 1) Digital Equipment Corporation, DECnet was your creation. A suite of network protocols, To connect your computers. (Chorus) DECnet, DECnet, It was the best network around. DECnet, DECnet, It connected us all. (Verse 2) You could connect your PDP-11s, To your VAX/VMS machines. You could share files and printers, And communicate with ease. (Chorus) DECnet, DECnet, It was the best network around. DECnet, DECnet, It connected us all. (Bridge) But then the internet came along, And DECnet fell out of favor. But it will always be remembered, As the network that connected us all. (Chorus) DECnet, DECnet, It was the best network around. DECnet, DECnet, It connected us all.

2 years, 2 months

Copying known nodes command.

by Brian Roth

Hello all, Just added a simh vax 11/780 to HECnet node 31.270 (FATTY) . Circuit is up. Using the copy known nodes command I get "unable to connect to listener" error. Any thoughts on this? Thank you, Brian.

2 years, 2 months

Re: DECnet/8 (was: Re: Copying known nodes command.) --> Mail to Paul @18-nov-2021> RE: Decnet8 and Pydecnet met Pdp8 --> update 8

by R. Voorhorst

L.S. ( & Paul), I sent the mail below (in Dutch) to Paul regarding Decnet-8. In short the conclusions translated: 1. I ironed out some minor bugs and got it running on a Simh Pdp8A simulator with KT8 in Km8 mode with 32 kW memory on Rts8-V2b and with Os8 in 12 kW in background. It has working basic Tlk/Lsn and Nip functionality (see display of Nip below) based on serial lines Ttix/Ttox and with/without Kg8 crc support. It is not very useful beyond that, unless provided with customer programming, and the ddcmp communication can easily be disrupted/poisoned by introducing incomprehensible net traffic packages from Pydecnet (routing messages); the error recovery is not well enough or absent and will kill the line communications leading to a software reboot. Within the Pdp8 framework it is stable (enough?) though. Decnet8 should also work with Dp01/Dp8E sync lines but these are not (yet) implemented and with the DKC8-A parallel interface (also not implemented) 2. This config could be reconfigured and made runnable on a standard Simh Pdp8. As only Decnet8 packet exchange is looked for, the original setup will do. 3. For future expansion the standard max 32 kW memory will not be enough and for Pdp8a Kt8 with up to 128 kW support, Decnet-8 has to be converted to Macrel/Link code within Rts8-V3. It could run with Os8 background in 342 kW and with a bank-contained Fpp8 in another 32 kW it leaves 65 kW for Rts8 and Decnet8. That conversion is not difficult to do but a job which has to be (and will be) done soon enough. 4. To make it more usable, Decnet8 will have to be lifted to Phase-II which is somewhat :( more work. Not too much differences in Ddcmp but much more in Nsp It is all a matter of available resources. 5. I can provide Paul with the basic config that still runs over here so that he can play around. Best regards, Reindert -----Original Message----- From: Robert Armstrong [mailto:bob@jfcl.com] Sent: Monday, 13 March, 2023 20:12 To: 'The Hobbyist DECnet mailing list' <hecnet(a)lists.dfupdate.se> Subject: [HECnet] Re: DECnet/8 (was: Re: Copying known nodes command.) >Paul Koning <paulkoning(a)comcast.net> wrote: >I just went back to the "decnet8.doc" file which is a DECnet for RTS-8 >user manual and internals document. Among other things, it describes >the protocol (DDCMP and NSP). > >I don't know much about PDP-8 software, but if someone manages to get >that code running I'll take a stab at PyDECnet support for talking to it. Can pyDECnet do asynchronous DECnet over a telnet port? I'm thinking the easiest way to set this up for debugging/testing would be to use simh for the PDP-8 and a virtual KL8-E connected to pyDECnet. Ultimately it would be nice to run it on real hardware with a real async DDCMP connection, but that's for later. Bob _______________________________________________ HECnet mailing list -- hecnet(a)lists.dfupdate.se To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se **************************************************************************** ******************************** Dag Paul, Er is inmiddels weer wat water door de rivieren gestroomd en ik heb basis decnet8 werkend gekregen: ****************** NETWORK INFORMATION PROGRAM V1D PHYSICAL LINE STATUS [DDCMP V1A] LINE NODNAM (#) STATE DRIVER VRSN UP SINCE 0 SWBZ04 (161) ON-LINE KL8J 1A 0:46:13 17-NOV-76 1 SWBZ02 (157) OFF-LINE KL8J 1A LOGICAL LINK STATUS [NSP V1C] CHAN STATE LINE TASK SRCE-NAME[PPN] TYPE LINK DEST-NAME[PPN] TYPE LINK 1 UNUSED 0 35 TLK [1,3] 0 6 2 UNUSED 0 36 TLK [1,2] 0 2 PHYSICAL LINE ERROR STATUS LINE 0: NO ERRORS 16 MESSAGES TRANSMITTED 12 MESSAGES RECEIVED LINE 1: NO ERRORS 0 MESSAGES TRANSMITTED 0 MESSAGES RECEIVED ******************* Het bleek nog niet eens zo moeilijk te zijn meer een zaak hoe de decnet configuratie volgens de lokale spelregels met eigenaardigheden om te zetten in assembler parameters en dan het rts-8 systeem te bouwen. De onderlaag lijkt (voorlopig) goed genoeg te werken, maar de cliënten TLK/LSN voldoen niet compleet aan hun specs. Maar ook de selectie van node naam blijkt niet afdoende; een pakket naar een node die niet adjacent is wordt gewoon door de adjacent node als bestemming geaccepteerd terwijl de bestemming node naam niet de juist is. Met name het zenden van berichten naar de eigen node werkt niet en dus ook de default commando's niet waar de eigen node naam wordt geëvalueerd. Het lijkt dat decnet8 de mogelijkheid van een alias definitie niet ondersteunt. Ook lijkt 0:: niet een optie te zijn als alias maar zou misschien wel moeten. Wat betreft de verdere weg is het duidelijk dat Decnet8 alleen zal werken binnen de niche Pdp8 en dat communicatie met andere types decnet nodes uitgesloten is. Dit betekent m.i. dat voor afdoende Decnet8 functionaliteit het product naar Phase-II moet worden opgetild met eventueel verzwakte functionaliteit door het weglaten van niet benodigde deel functies (Ddcmp MOP boot?). Dat betekent dat een Phase-II compatibele Decnet8 kan communiceren met de andere Phase-II nodes zoals al in aanleg aanwezig moet zijn geweest vlak voordat het product afgedankt werd. Zouden er nog ergens kopieën van rondzwerven? Enig idee? In elk geval betekent dit geen wijzigingen voor Pydecnet aangezien ik aanneem dat er verder geen Phase-I/? ondersteuningswensen voor Pydecnet aanwezig zullen zijn? Ik ga ervan uit dat Pydecnet wel de Phase-II intercept ondersteunt, anders moet er een Dec variant bestaan die dat kan invullen. Zijn er nog wetenwaardigheden die in acht moeten worden genomen voor het (eventuele) omzetten naar Phase-II? Decnet8 intercept zal m.i. niet tot het aangeboden palet gaan behoren. Kan Pydecnet omgaan met async lijnen die naar Tcp/ip sockets i.p.v. com poorten afgebeeld zijn? Nu lijkt het erop dat alleen synchrone lijnverbindingen werken in die modus wat een beperking inhoudt. Reindert **************************************************************************** ****************************

2 years, 2 months

Another "joining HECnet" request

by Mike Shields

Hello all - long time member of the list, and about time for me to get a machine connected. I have a PiDP-11 running RSX-11M-PLUS 4.6 and BQTCP/IP. It's emulated, but is up 24/7 and I'm interested in allowing guest logins or other remote use of the machine. (Even if only to keep those sweet blinkenlights moving around in more interesting patterns than the idle loop!) I'm in Northern Virginia, USA and see that there are two areas in my neighborhood, 59 and 31. Who would I reach out to regarding connection to either area? Also - I'm no RSX-11m wizard (still learning), so I'd be interested in any pointers to the incantations necessary to forge the Multinet connection from RSX-11M-PLUS (if this is indeed the recommended approach). Thanks all - looking forward to getting packets flowing. - Mike

2 years, 2 months

Re: A milestone

by Johnny Billquist

Yes, LEO was #1000. :-) Johnny On 2023-03-09 02:32, Brian Roth wrote: > Wow, very cool. I was just looking at my Directory of computer networks > at lunch the other day and scanning over the SPAN network from 1990.Its > hard to believe just 30 years ago there was a worldwide DECnet network > with over 17,000 computers, real machines doing real work. Its pretty > cool to actually see in detail every machine type on SPAN (almost > entirely DEC) , machine names, VMS version and even phone numbers. BTW > was my machine LEO the 1000th? > > > On Wednesday, March 8, 2023 at 03:47:26 PM EST, Johnny Billquist > <bqt(a)softjar.se> wrote: > > > I have been planning for a long time to post a small reflection when I > reached 1000 nodes registered in the hecnet nodename database. > > This happened tonight. I think it is a pretty cool thing. There are now > 1000 nodenames registered in this small hobby DECnet. I guess you could > say it's actually not that small. > > However, I know that rather few machines are actually online, and it > might even be that the majority of nodes registered have never been > online. My guess is that maybe 5% of the registered machines are usually > online. But I do not have any hard data to back this up. > > HECnet started out about 20 years ago from a desire I had to hook up a > PDP-11 I had at home, to some machines at my university, using DECnet. > At the time, I didn't have any TCP/IP for RSX, and the only way to get > any kind of networking was to try and come up with some way of getting > DECnet up. > > My first implementation basically just forwarded a serial port > communication between two Unix machines. And on each end I then hooked > that serial port into a PDP-11 running RSX, and used DDCMP for the > actual DECnet link. > > This worked, but was obviously not that fast, as the serial ports were > limited to 9600 bps. > > After a year or so, I figured I could instead write a small program that > would forward ethernet packets. Using UDP I basically had the same > property as a local ethernet, but it could be located somewhere pretty > far away. From a DECnet point of view, it would appear as if they were > on the same ethernet segment, while in reality they were nowhere near. > As DECnet have pretty long timeouts on things, it turned out this worked > without a hitch, and I could achieve much better throughput. > > Not long after that, the first other users were hooked up to HECnet as > well. This was maybe around 2003 or so. > > Another data point is that there are 113 different persons that have one > or more nodenames registered. > > Happy milestone, everyone, and thanks for being around. > > Johnny > > -- > Johnny Billquist || "I'm on a bus > || on a psychedelic trip > email: bqt(a)softjar.se <mailto:bqt@softjar.se> || Reading > murder books > pdp is alive! || tryin' to stay hip" - B. Idol > _______________________________________________ > HECnet mailing list -- hecnet(a)lists.dfupdate.se > <mailto:hecnet@lists.dfupdate.se> > To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se > <mailto:hecnet-leave@lists.dfupdate.se> > > _______________________________________________ > HECnet mailing list -- hecnet(a)lists.dfupdate.se > To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se -- 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

2 years, 2 months

Some area 29 stuff

by Keith Halewood

Hi, I've just noticed that nodes 29.600-699 had been allocated to someone and they've since disappeared from the HECnet node database... or possibly I imagined the whole thing... except for the fact that I had an inbound multinet circuit for nodes in that range. I've just removed the circuit and the firewall ACL for incoming on TCP port 9604. The circuit hadn't been used in some time. In no other particular order of peers: 29.400-403 (Ales Petan) has been gone a while. 29.450-469 (Trevor Warwick) similarly. 46.1-9 (Douglas Hall) has been gone for quite a long time. 52.* (Brian Hechinger) has been down for a few weeks... and has changed incoming IP address once or twice too. I'm not complaining, just wondering. Known areas are going dark at a rate greater than 0 too. Oh, and ANKE (1.1023) went >BANG< a few days ago. Regards Keith

2 years, 3 months

A couple of minor issues with RSX BQ-IP apps

by peter＠whisker.org.uk

Hi, I have a couple of strange issues on RSX-11M-PLUS with the latest TCP/IP stack (build 14-FEB-2023 00:19). 1) If I create a LB{1,2]SYSLOGIN.CMD with a couple of entries such as: set /named set /vt2xx=ti: when I login, it executes the commands but then I can type nothing at all into the terminal screen, it is completely frozen. 2) When I try to send an e-mail (I think it is set up OK), it gives the following error: >SEN To: PETER.WHISKER(a)GMAIL.COM Connection to local node:: failed, CONN STATUS= 2 STATUS2= 0 SENT0 -- STOP ERROR The [IPLOG]MAILD.LOG shows: Sun, 19 Feb 2023 09:47:58 (MAI.0) MAIL11 got connection from CLIONA:: (Unknown M AIL11 V3.0) Sun, 19 Feb 2023 09:47:58 (MAI.0) Connection lost I'm a bit lost as to how to debug this further - has anyone else encountered it or can Johnny shed any light? Thanks Peter Whisker

2 years, 3 months

HECnet connection error from RSX-11M-PLUS node

by peter＠whisker.org.uk

Hi, I'm attempting to connect to the area 29 node and Keith Halewood has very helpfully set me up with a listener. I've been getting a strange error on the Multinet link and updated to the latest BQ-IP from December 2022 before posting this. I continue to have the same problem after the update. My IP stack is fine - I can ping and get the NTPDATE time and I can access my RSX11M system via Telnet. The Node has the right area and number and I can access it from the other node using RMT. However when I try to bring up the link to HECNet I keep getting this error repeating: >NCP SET CIR IP-0-0 STA ON 14:29:03 COT -- Date is 13-FEB-2023 14:29:03 MLTNET V1.27 starting. > > 14:29:05 MLTNET - IP-0-0 XMIT fail. IOSB=-3 14:29:10 MLTNET - IP-0-0 XMIT fail. IOSB=-3 I can see the traffic leaving on my DSL router to the Area 29 router and the replies coming back. So I am bit mystified. I think IOSB error -3 is IE.DNR - Device not ready? Node details: >NCP SHO KNO NOD Known nodes summary as of 13-FEB-2023 14:32:39 Executor node = 29.850 (CLIONA) State = On, Identification = CLIONA RSX11M+ V4.6 Remote Active Next Node State Links Delay Circuit Node 29.1 (A29RT1) Unreachable 29.2 (A29RT2) Unreachable 29.852 (SADHBH) Reachable UNA-0 29.852 (SADHBH) Below is recent correspondence - I will post it hear as it may be helpful: Hi It’s set up as a “Level 2 router” – perhaps that is the problem? I’ve looped in Johnny in case he has an idea where the problem may be? Regards Peter >; ===================================================================== >; DEC - Section 1 - Define the target and remote nodes >; ===================================================================== >; >; Generating node 29.850 (CLIONA), Id = CLIONA RSX11M+ V4.6 >; Node type is level 2 router >; Highest node number in network is 1023 >; Highest area number in the network is 63 >; Network command terminal and layered product support will be included >; The MACRO-11 and FORTRAN/COBOL/BASIC+2 user libraries will be supplied >; >; The remote node names are: >; 29.852 (SADHBH) >; 29.2 (A29RT2) >; 29.1 (A29RT1) >; >; <EOS> Do you want to: >* <RET>-Continue, S-Skip, R-Repeat section, P-Pause, E-Exit [S]: >; >; From: Keith Halewood <Keith.Halewood(a)pitbulluk.org> The only thing I can think of is DECnet with more than 1 interface needs to be an L1 router and not an endnode. Other than that, I’m not at all familiar with RSX and Johnny’s IP stack. From: Peter Whisker [mailto:peter@whisker.org.uk] I'm getting IOSB error -3 which I think may be IE.DNR Device not ready. I can see the IP traffic going out and back on the interfaces both sides of my router. I need to check if I've missed some DECnet configuration. On Mon, 13 Feb 2023, 10:39 Keith Halewood, <Keith.Halewood(a)pitbulluk.org> wrote: I can see your connection attempts. The DECnet router 29.2 is reporting ‘unexpected packet type’, adjacent node 29.850, packet header 01 29.850

2 years, 3 months

Joining HECnet

by peter＠whisker.org.uk

Hi, I have 20 years experience of PDP-11s and RSX-11M in particular which I haven't used much since 2000, so I have decided to brush up again and have spun up a couple of RSX-11M-PLUS 4.6 nodes in simh. They are happily chatting away over BQ-IP and LAT and I guess the next stage is to request a connection to HECnet. My two geographically nearest node areas are Northolt (UK) and London (UK) - both within 30km of me. It looks like Northolt area 29 (Keith Halewood) might have a main routing node. London is in area 8 with admin Sampsa Laine. I'm just wondering if either of these areas allow new connections ot what is the best way to go? Many thanks Peter Whisker Addlestone, Surrey UK.

2 years, 3 months

A2RTR down for 2 hours on 2/27

by Robert Armstrong

FYI - AWS is doing maintenance on 2/27/2023 at 8AM GMT so A2RTR will be down. That's the middle of the night/very early morning for us here in the USA. Bob -----Original Message----- From: Amazon Web Services, Inc. [mailto:no-reply-aws@amazon.com] Sent: Friday, February 10, 2023 2:03 PM To: bob(a)sparetimegizmos.com Subject: Scheduled maintenance for Amazon Lightsail instances on Mon, 27 Feb 2023 08:00:00 GMT Dear Amazon Lightsail Customer, One or more of your Amazon Lightsail instances is scheduled for maintenance in a 2 hour window starting on Mon, 27 Feb 2023 08:00:00 GMT. Maintenance activity will result in the following Lightsail instance(s) in the us-west-2 region to be unavailable and then rebooted: HECnet If you have any questions or concerns please contact the AWS Support Team on the community forums and via AWS Premium Support at: http://aws.amazon.com/support Sincerely, Amazon Lightsail Team Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210

2 years, 3 months

← Newer
1
...
8
9
10
11
12
13
14
...
1556
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet