HECnet

hecnet@lists.dfupdate.se

15586 discussions

by supratim＠riseup.net

On 5/4/18 6:16 PM, Johnny Billquist wrote >>> I have a candidate... ;-) >>> >>> ? Johnny Johnny - can we ask this person to try a Multinet connection to 45.62.248.66 port 60001 and see if HECnet can be reached? If running OpenVMS, MULTINET:DECNET-CIRCUITS.COM should contain (needs editing by hand after MULTINET CONFIGURE /DECNET creates the skeleton without /TCP): $ multinet set /decnet /remote=45.62.248.66 /port=60001 /device=tcpa0: /connect /tcp=connect /buffers=24 I tested it successfully. Others can be added too (on different port numbers to be assigned). Thanks, Supratim -- Sent via Thunderbird/macOS High Sierra on Lenovo Legion Y720/Windows 10/VirtualBox

7 years, 7 months

Connections?

by bygg＠cafax.se

The other Johnny wrote: > Just realized I should maybe make another comment here. > I don't fully know how Multinet under VMS is managed, or what > limitations there might be. > My Multinet compatible implementation under RSX might have some issues > communicating with VMS nodes, but in general it seems to be working just > fine. > The setup under RSX do not really have any problems with dynamic IP > addresses. But it does introduce a bit of exposure, since when the other > end has a dynamic address, Multinet will have to be able to accept > connections from anywhere. I have been pondering whether to enable > passwords on those links. But until now, it's not been a real problem, > since people scanning and probing ports have no clue about DECnet over > IP to start with. Shameless plug or something here: I have a program called anftunnel which as the name suggests initially was used to handle ANF-10 packets. It has grown a bit from that, and can do other things as well now. Amongst what it can do is: * Set up a tunnel between two machines, with optional crypto and auth. The passive (listening) end needs a static address, the other don't. * Talk to an ethernet interface (via libpcap) and tunnel ethernet frames. * Terminate a (virtual) sync line and tunnel the frames. Handle TCP and UDP encapsulated DDCMP lines of the SIMH variety. * Terminate a MULTINET DECnet-over-IP link. (untested, but given how simple the encapsulation is...) * For ANF-10, it can connect an ethernet to a sync line. This requires slightly molesting the packets involved. It should be possible to use this to tunnel DECnet/Multinet between two nodes and keep the Multinet part local to each host. A slight perversion would be to connect a Multinet link to a DDCMP one... Source tarball can be found at: https://www.pdc.kth.se/~bygg/tops/anftunnel.tar > Johnny --Johnny (another one of them)

7 years, 7 months

RSX software...

by bqt＠softjar.se

Someone asked a while ago about DECUS software for RSX. I've now set things up on Mim. So pretty much all DECUS software can be found at MIM::DECUS: While I was at it I also decided that I might as well make some of the DEC software available as well to people on HECnet. So, there is also MIM::KITS:, which have various layered products I have tape images for. I would actually suggest people fetch things through TCP/IP and not DECnet when possible, since TCP/IP is both more efficient, and also preserves meta information better on transferred files. (But both ways will work.) So, have fun installing all kind of stuff. Also, for most things I also have manuals at http://mim.update.uu.se/manuals I have some more manuals that I have not scanned yet, and I know that some of the manuals in there are not really well scanned, and might lack a page or two. Let me know if you have any issues, and I'll try to help. 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

7 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. This release contains a lot of fixes and improvements in many areas. There are a couple of very serious bugs in TCP that is fixed in this release which is why I really encourage people to upgrade. (They do not happen often, but if they happen, they have a high chance of crashing the system.) Highlights: - Stability and reliability improvements in TCP. - Improved logic for TCP probing, keepalive and retransmits. Magica (a real PDP-11/70) and Mim (an emulated PDP-11/74) have been serving traffic for several weeks without any issues, and I think I have finally found and fixed a very obscure problem that occasionally could crash the system. (And both of these machines are more or less fully exposed to the internet, so they see a *lot* of connections and random attempts to compromise them all the time.) Detailed information on things that have been done since the last release: TCP: - Correct TCP reception. It could stop the retransmit timer even if there was still data outstanding under some circumstances. - Bugfix in data resend in TCP. Under some circumstances the retransmit timer stopped even though there was data to send. - Improved TCP retransmit timers to better handle probing and keepalive. - Improved TCP keepalive timer handling. - Improved TCP timeout handling for closing sockets. - Improved TCP retransmit timer restart logic in received TCP ACK processing. - General rework of TCP retransmit logic. - Bugfix. In TCP TimeWait state, received FIN packets did not result in an RST packet. - Changed TCP FinwWait2 to use keepalive timer to probe connections. - Improvement to TCP reception to dedup received packets also for packets that are pending. - Bugfix in TCP packet sending. If we ran out of IP POOL, memory got corrupted. - Improved handling of TCP receive window if TCP receive size is shrunk. - Add probing of socket during closing stages, since we have no other way to tell if the remote end is still around. - Change how TCP decides if it should probe a connection. - Bugfix in TCP. If a socket had no window but outstanding data, and was closed, and other end never opened up a window (for example if the remote end is gone), then the socket would get stuck in Fin-Wait-1. - Changed TC driver so that user ASTs are generated immediately if there is data to be read and the AST address is changed. - Improve TCP options processing. Some badly formatted tcp options packets could crash the system. - Improved TCP handling of ICMP error packets. UDP: - Bugfix in UDP. If several error packets were received for a socket, several ASTs were queued, but only one error is saved, meaning the additional ASTs could make code try to read several times, when all except the first would not have anything to actually read. TELNET/TELNETD: - Improved abort handling in telnet client. - Changed TELNETD do do spoof notifications in a simpler way. - Rewritten TELNETD to handle fast input without loosing characters. - Fix mapping error under special circumstances in telnetd, which could corrupt the system. - Added more IAC options processing in telnet and telnetd. DNS: - Improved name resolution handling if no UDP available. - Improve resolver domain I/O error handling. RWHOD: - Added handling of no UDP available in RWHOD. MAILD: - Improve MAILD handling of DECnet connections. - Improved privilege handling in MAILD. - Improved maild unread message function. - Added manual holding of mails. General: - Improved ability to stop protocols from IFCONFIG. 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 The firewall for Mim have now been removed, so no need for the alternate ports, but Mim is still listening to the alternate ports as well. ftp: 10021 telnet: 10023 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

7 years, 7 months

Strange unit of time

by ian＠platinum.net

Excuse the noise, but I?ve got a fragmented recollection of a strange unit of time, and my faulty memory seems to equate this with VAX and/or VMS. My google-fu has failed me (or confirmed that this is some sort of fake memory) however I thought I?d run it past the experts in here. Does anyone know of anything strange about the unit of time, or possibly the epoch, or something else associated with time measurement (or the TOY clock or basically anything to do with time) in the DEC world? Sorry for the vagueness of the question, but hopefully someone can help :) Ian

7 years, 7 months

Asymmetric connectivity in a cluster

by dwe-6006＠philtest.org

I'm not sure that asymmetric is the correct description but I can't think of a better term. I am using SIMH and I have a two node cluster (with a quorum disk) the two nodes have a common system disk. The two nodes are RODNEL (1.1) booting from SYS0 and ADV2 (1.3) booting from SYS2. Both are running DECnet Plus both are running Multinet for the IP stack. At one time there was also a node (never actually a member of the cluster called HCBVAX (1.2) it booted from SYS1 but it no longer exists. The nodes are connected over an Ethernet and the MAC addresses are the ones that I would expect AA-00-04-00-01-04 (1.1) and AA-00-04-00-03-04 (1.3) HCBVAX was AA-00-04-00-02-04 (1.2) I can login to RODNEL and "set host adv2" with no problem, I can login to ADV2 and "set host rondel" with no problem. On each of the nodes I can "show cluster" and I see what I expect to see with no errors. While logged in to RODNEL the command "moni cluster" works fine. While logged in to ADV2 the wheels seem to fall off the bus - "show cluster" is fine but "moni cluster" isn't Any help would be appreciated. This is the information that I have gathered so far (I am not happy with the forwarding address in the error message from "moni proc" on ADV2 which seems to arise from RODNEL --Dave View of Cluster from system ID 1027 node: ADV2 22-APR-2018 22:24:50 +-----------------------------+ | SYSTEMS | MEMBERS | +-------------------+---------| | NODE | SOFTWARE | STATUS | +--------+----------+---------| | ADV2 | VMS V7.3 | MEMBER | | RODNEL | VMS V7.3 | MEMBER | +-----------------------------+ ^Z $ $ moni cluster %MONITOR-I-ESTABCON, establishing connection to remote node(s)... %%%%%%%%%%% OPCOM 22-APR-2018 22:24:56.75 %%%%%%%%%%% Message from user SYSTEM on RODNEL Event: Address Unreachable PDU Discard from: Node LOCAL:.RODNEL Routing, at: 2018-04-22-23:24:56.740-04:00Iinf Discard Reason=Destination Addrs Unknown, Source Address=49::00-01:AA-00-04-00-03-04:21, Forwarding Address=49::00-01:AA-00-04-00-02-04:21 eventUid FC95D640-467B-11E8-99E1-AA0004000104 entityUid 5683CC80-467B-11E8-8004-AA0004000104 streamUid 5A113900-467B-11E8-8004-AA0004000104 Still on ADV2 - NCP is odd as well: $ mcr ncp NCP>sho exec char Node Volatile Characteristics as of 22-APR-2018 22:31:17 Executor node = 1.3 (ADV2) Identification = DECnet-OSI for OpenVMS Management version = V4.0.0 Incoming timer = 0 Outgoing timer = 0 NSP version = V4.1.0 Maximum links = 0 Delay factor = 0 Delay weight = 0 Inactivity timer = 0 Retransmit factor = 0 Routing version = V2.0.0 Type = nonrouting IV Routing timer = 0 Subaddresses = 0 Broadcast routing timer = 0 Maximum address = 0 Maximum circuits = 0 Maximum cost = 0 Maximum hops = 0 Maximum visits = 0 Maximum area = 0 Max broadcast nonrouters = 0 Max broadcast routers = 0 Maximum path splits = 0 Area maximum cost = 0 Area maximum hops = 0 Maximum buffers = 0 Segment buffer size = 0 Buffer size = 0 Pipeline quota = 0 Alias maximum links = 0 Path split policy = Normal Maximum Declared Objects = 0 NCP>show know nodes Known Node Volatile Summary as of 22-APR-2018 22:31:29 Executor node = 1.3 (ADV2) State = on Identification = DECnet-OSI for OpenVMS NCP>def node rodnel Node address (1.1-63.1023): 1.1 Node name (1-6 characters): rodnel NCP>set node rodnel all %NCP-W-UNRCMP, Unrecognized component NCP>set node rodnel Node address (1.1-63.1023): 1.1 Node name (1-6 characters): rodnel %NCP-W-UNRCMP, Unrecognized component , Node NCP>exit Whereas RODNEL seems happier: NCP>sho exec char Node Volatile Characteristics as of 22-APR-2018 20:15:29 Executor node = 1.1 (RODNEL) Identification = DECnet-OSI for OpenVMS Management version = V4.0.0 Incoming timer = 0 Outgoing timer = 0 NSP version = V4.1.0 Maximum links = 0 Delay factor = 0 Delay weight = 0 Inactivity timer = 0 Retransmit factor = 0 Routing version = V2.0.0 Type = nonrouting IV Routing timer = 0 Subaddresses = 0 Broadcast routing timer = 0 Maximum address = 0 Maximum circuits = 0 Maximum cost = 0 Maximum hops = 0 Maximum visits = 0 Maximum area = 0 Max broadcast nonrouters = 0 Max broadcast routers = 0 Maximum path splits = 0 Area maximum cost = 0 Area maximum hops = 0 Maximum buffers = 0 Segment buffer size = 0 Buffer size = 0 Pipeline quota = 0 Alias maximum links = 0 Path split policy = Normal Maximum Declared Objects = 0 NCP>sho kno node Known Node Volatile Summary as of 22-APR-2018 20:15:37 Executor node = 1.1 (RODNEL) State = on Identification = DECnet-OSI for OpenVMS Node State Active Delay Circuit Next node Links 1.3 (ADV2) 1.1 (RODNEL) NCP>sho node adv2 char Node Volatile Characteristics as of 22-APR-2018 20:16:02 Remote node = 1.3 (ADV2) Service password = 0000000000000000

7 years, 7 months

Paging Steve Davidson

by bqt＠softjar.se

Have anyone heard from Steve Davidson recently, or know of a working address for him? Trying to reestablish a connection. 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

7 years, 8 months

DECUS stuff on hecnet?

by mcguire＠neurotica.com

Hey Johnny, is the DECUS RSX library up on MIM:: somewhere? Or does anyone else have it up and accessible via hecnet? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

7 years, 8 months

by supratim＠riseup.net

Hi, Any recommendations on a CISCO switch simulator that runs on Linux (Ubuntu 17.10) and supports GRE tunneling to a real CISCO switch over the internet? TIA Supratim

7 years, 9 months

KLH10 not idling host CPU

by bygg＠cafax.se

Mark Abene <phiber at phiber.com> wrote: > I'm posting this here in the hopes that there are other KLH10 emulator > users on HECnet. There are, I am one of them. > I've been using KLH10 with the tap patches for years and years, and idling > has always worked fine. At some point over the recent couple of years, > idling stopped working for me on linux (I run ubuntu 16.04.4 LTS with > latest updates as of yesterday, on a 64-bit intel machine). My CPU is stuck > at 100% utilization, without even starting an emulated OS (I run TOPS-20). > In fact, as soon as I type "GO" in KLH10 and before doing anything else, > the CPU immediately shoots to 100%. Is anyone else seeing this? In older > versions of ubuntu/linux this didn't happen. Handful of points: * the idling is done by modifying the idle loop in the guest operating system to interact with the KLH10 idler device, not by identifying the idle loop like SIMH does. * until the OS is up and running, there is no idling. In other words, while at the BOOT> prompt there will be a loop consuming 100% CPU waiting for terminal input. This is normal, and it has always been that way. * if you have had the same TOPS20 system running, with idling, earlier everything points at your host os (ubuntu) no longer cooperating with KLH10. I myself run (mostly) FreeBSD, and I have never had problems with idling the TOPSxx systems. * for TOPS10, there are a couple of more things to consider, one of them is that the idler device by default is at device code 700, which can't be accessed from the mode the -10 idle code runs in. Using 740 works. I would look for what has changed in your host os (ubuntu) regarding system timers and such. Your setup *should* work. > Thanks, > Mark --Johnny

7 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet