I'm not sure if the HECnet list is the best place to ask this, but hopefully it's not too far off topic.
Let's say that I want to run a full-time SIMH emulation of a VAX running VMS (because I do). This would be my full-time DECnet presence on my local network, my primary means of moving things between my DECnet-speaking computers and my modern machines, and my full-time HECnet presence if I ever find a good way to have persistent internet access at my rural home. The SIMH emulation would be hosted on a Linux server.
It's easy enough to set up the host server to automatically launch a SIMH emulation at boot time, but I don't know yet how to deal with automatically and cleanly shutting down the emulation when the host server needs to shut down. In particular, I'd want to somehow trigger an orderly VMS shutdown when the host server needs to perform an unattended shutdown, such as when the UPS signals a power failure. If there's a way to checkpoint the entire emulation and then restore it later, that might also be a good option, as long as I can prevent corrupting the emulated system's filesystems by suddenly yanking the virtual power plug.
Is there any prior art for setting up an unattended SIMH-based VAX/VMS emulation like this?
--
Mark J. Blair <nf6x at nf6x.net>
http://www.nf6x.net/
Can somebory try to login via Hecnet to RVDSXL
(3.47) please and report the result? There is no
GUEST account on it, as far as I know.
The machine is responding to ping, but telnet and
SSH time out.
--
Regards, Rok
Hi folks. I've found something that I'm looking for listed in the
SIGTAPES.SUM file in the rsx freeware CD v2, but I can't find the actual
software anywhere. It's from the European 1984 RSX SIG Tape, Amsterdam.
Maybe I'm being dense but I can't find that stuff anywhere. The
specific software I'm looking for is called CCDRV; if you search for
that in SIGTAPES.SUM it's listed there.
Can anyone help?
Thanks,
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Time for a new release announcement of TCP/IP for RSX-11M-PLUS.
I usually try to avoid spamming lists with release announcements,
and the previous announcement was only a month ago, so I apologize
in advance for the noise.
However, I have a really good reason for this announcement. In the last
few days I identified a bug within RSX, that has been latent for
many years, but which gets activated when TCP/IP is installed.
Because of this, I've cut a new distribution of BQTCP, which now also
includes some patches to RSX, which I really implore everyone to
install.
Highlights:
- Stability and reliability improvements in RSX.
- Improved stability of Multinet.
- Improved stability of MAILD.
Detailed information on things that have been done since the last release:
RSX:
- The MCR REMOVE command have an interaction with the IP: device driver,
which have a bug. Traditionally, the IP: device driver was for the
IP11 device, which I doubt anyone have used in many years, so this
bug have probably been around a long time without detection.
The result of it is that low core and pool will get corrupted when
giving the REMOVE command, and IP: exists.
BQTCP now includes an optional "patch RSX" section in IPGEN, which
will install a new version of MCR on the system. This is only needed
to be run once, as the patching is installing new tasks, and
changing the bootable image to use these new tasks, which is a more
permanent change.
Along with the fix for the memory corruption issues, the new version
of MCR will also fix a few other issues that people might or might
not have noticed. There is some more details in the BQTCP
documentation.
Multinet:
- Some transmit errors should restart the link, but this was not done.
Fixed now.
MAILD:
- Added paging to mail reader.
- Improved remote node system type detection for DECnet.
- Improved the memory layout of MAILD, to avoid some crash situation.
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
I have seen this elsewhere but I see no reference to a fix to the problem
on Multinet. I have a Multinet SSHD agent running and when I attempt to do
a connection the connection does succeed but it can take 90 seconds. I put a
Sniffer on the line and the SSHD agent is attempting to do reverse DNS
lookup on the incoming address. This is normal, but it is doing 6 IPv6
resolution attempts (3 to each of the 2 DNS servers) before it makes the
first IPv4 request. I do not have IPv6 configured on the interface (or any
interface) and I need to find a way to suppress all IPv6 DNS queries( PTR or
AAAA) is here a magic incantation or a logical name that makes this happen?
Dave
Guys. I figure I should try to get a more formalized handling of
connections to HECnet.
With my bridge, it's mostly just people connecting to me, but this is
not a solution that scales very well, so in general I now try to
discourage people from this option. When possible, I prefer to move
people away from it.
Multinet on the other hand scales well. And is possible to use directly
both in VMS and RSX. However, it is silly and inefficient if all
multinet links are to go to me. So I'm thinking about identifying a few
people/places elsewhere in the world, which can be used for connections
where it makes more sense for a somewhat closer point of connection.
So, I would go on dealing with Europe. Might at some point be that we'd
like a second point in the south of Europe, but that is not a high
priority right now.
However, for the US, it would be nice if we could identify a location on
each coast, which have a capable system, and normally is always online,
and which have a good bandwidth, and would be willing to setup
connections to new machines that want to come online.
So, are there any takers? I'll continue to be the first point of contact
when people come asking, but I'd be happy if I could redirect them to
the appropriate person once we have figured out a few basic details.
And then these two persons can work on establishing the actual link.
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
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
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)
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
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
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
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
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
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
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
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
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 HTTPD
- Improved MAILD
Magica.Update.UU.SE, which is a real PDP-11/70, have now run with the
latest release for over 3 weeks without any issues, so I think it's safe
to say that this product is now very stable. Mim.Update.UU.SE (an
emulated 11/74) have in the same time served over 7Gb of data over FTP,
HTTP and other lower volume channels. (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:
- Improved handling of received TCP push packets.
- Improved TCP ACK handling under lost packet recovery.
- Improved TCP window update handling.
- Bugfix for the condition that a socket was closed while there was
outstanding sends and the remaining window was 0 and the transmission
was not ACKed. This would cause the socket to get stuck in a pending state.
- Improved TCP write handling. The second IOSB word was previously not
set to reflect how much data was written.
- Added new TCP option for sockets to optionally return available data
at read if push was set.
- Bugfix in TCP. An internal data structure was sometimes modified when
it should not be, which could cause a system crash under rare circumstances.
HTTPD:
- Improved error handling for CGI pages.
- Improved subprocess handling for CGI module.
MAILD:
- Improved MAILD to handle broken Linux MAIL11 server.
- Improved MAILD error handling.
- Bugfix in MAIL. When composing mails, the temporary file is now
created under SYS$LOGIN.
- Added timeouts for various parts of MAIL11 processing.
Libraries:
- Improved subprocess handling in BASIC+2 library.
- Updated F77 library and documentation.
Multinet:
- Improved performance.
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
I'm posting this here in the hopes that there are other KLH10 emulator
users on HECnet.
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.
Thanks,
Mark
Hi,
I?m running the bridge with the following bridge.conf:
?? SNIP ---
local eth0
update psilo.update.uu.se:4711
hilanet 84.231.64.229:4711
maguro 38.130.230.105:4711
[decnet]
local
update
hilanet
maguro
[lat]
local
update
hilanet
maguro
? SNIP ?
But when I run the bridge using ?./bridge 4711? I keep getting these weird errors:
Dumped packet from 38.130.230.105 (1024).
Any ideas?
Sampsa
Yes I am interested in that. Let me know when done. Also you can send
scanned docs to bitsavers.
I put each package funetnje and hujinje into git together and uploaded it
into my github account.
For decent for Linux, I converted CVS repo into git repo and uploaded it
into my github too. So you can now apply fixes to that repo.
If you find JNet 2.x software, please let me know. There is programming
guide doc in JNet package through 3.2. It was removed on 3.3 or above. No
they are not in funet and can?t find them through google so far.
Does anyone have JNet for Alpha? I have only JNet 3.5 to 3.7 for VAX.
Tim
On Sat, Feb 17, 2018 at 3:39 AM Erik Olofsen <e.olofsen at xs4all.nl> wrote:
> Tim,
>
> I have the JNet Network Manager's and User's guides, no programming guide,
> for version 2.0$
>
> Let me know if I can look up something for you.
>
> Actually I don't have the software - so you found it at funet?
>
> Erik
>
>
I come from a mostly-UNIX, mostly-TCP/IP background. I don't understand DECnet well yet, but I want to learn more! Much of my interest in joining HECnet and playing around is because I largely skipped over DECnet in its original airing, and now it seems like a weird foreign land that I feel an irrational need to grok in fullness.
What are/were the conventions for providing public services over DECnet Phase IV networks, to remote users without their own local user accounts? I.e., let's say that I had a node on a large DECnet-only network back in the before time, and I wanted to share a file repository in a manner comparable to anonymous FTP on a TCP/IP network. How would I have done that? Were there conventions for doing that sort of thing back then, or was that a foreign concept on large DECnet networks at the time?
Were there any examples of BBS-like servers living on DECnet networks? Online multi-player games such as MUDs? Early DECnet-based examples of "log into the coffee pot to see if the brew is fresh"? DECnet-based analogs to Archie for discovering stuff? DECnet-based USENET-like communities?
I don't know if any of these concepts even made sense in the DECnet world at the time. In addition to only understanding the networks of the 80s from a UNIX-centric, TCP/IP-centric worldview, I'm also having a hard time un-thinking the newer concepts I'm used to after so many years of steeping in a broth of HTTP and social media. I have somewhat conflicting urges to both learn how to think like a 1980s DECnet user, and to retcon modern concepts into an alternate reality where TCP/IP never took off.
--
Mark J. Blair, NF6X <nf6x at nf6x.net>
http://www.nf6x.net/
For those interested in running the updated DECnet kernel module
under Ubuntu rather than Slackware, I gave it a go by updating my
machine running 16.04 following the steps at:
>From https://www.maketecheasier.com/build-custom-kernel-ubuntu/
And it was quite easy indeed. [But have plenty of free disk
space, say >20 GB. If the make fails, and you have to start over,
it does a 'clean' first. So even when doing make...]
Of course, after the step to have the kernel source ready,
for example in 'kernelbuild', cd to 'kernelbuild/net' and unzip
the dflkm.zip file, which may be found at RULLFS::
One of my nodes fell off Hecnet (actually a while ago).
I finally got around to reboot it in order to get it back.
The problem? Too much uptime.
Monitor Atle - DEC-10 at work
System uptime 10483:52:41
Current date/time Thursday 8-Feb-2018 8:00:14
Thats what you get for running stable hardware. On the other hand,
this is/was a known problem:
MCO: 12935 Name: WXD Date: 22-May-86:14:12:35
[Symptom]
DECnet stops working correctly. The -10 sees all the nodes
on the ethernet, but isn't seen by any of the nodes.
[Diagnosis]
The -10 has stopped sending ethernet hello messages. This
is caused by the -10 getting an overflow when calculating the DECnet
time (milliseconds of uptime), which is then used to determine when
to send the next message. The algorithm is:
MOVE T1,SYSUPT
IMULI T1,1000.
IDIVI T1,JIFSEC
This overflows at 159 hours, 4 minutes, 22 seconds, and 19. ticks (60hz).
[Cure]
Change IMULI -> MULI, and IDIVI -> DIVI
This algorithm won't overflow until 9544 hours of uptime (395+ days).
--Johnny (the other one)
/\_/\
( *.* )
> ^ <
On a virtual machine with lubuntu 12.04, kernel 3.2.0, I have
DECnet for Linux V.2.5.68s working, with dnprogs version 2.65.
It is node RULLFL.
The daemons and utilities use decnet.conf with node information,
so something useful would be to create it from mim::nodenames.dat.
On a VAX, TYPEing it works well, but on the Linux machine, dntype
hangs after giving parts of the file; dndir mim:: works well.
Does anyone have dntype mim::nodenames.dat working properly (with
perhaps different versions of the above)?
Thanks!
Johnny,
Using your [IPF77]TEST2.FTN, I made a very simple network printing routine that I can begin to modify for a Brother Laser printer which
will have its own escapes codes for portrait, landscape etc. and pull file names from the command line. I show it below in case any one wants to do something similar. I used your MKE and MAKEFILE,; to handle getting the libraries and switches correct.
PROGRAM NETPRT
INCLUDE 'INET'
CHARACTER*40 HOST, URL, FIL
CHARACTER*1 TXT(132)
CHARACTER*6 EP
INTEGER*2 LPO, I, L, K, PORT
HOST='192.168.0.27'
PORT=9100
LPO = TCP(1,0)
IF (HOST2I(EP,6,HOST,40,PORT) .NE. 0) THEN
TYPE *,'Failed to convert hostname.'
CALL EXIT(1)
END IF
IF (CONNEC(1,EP,6,PUTXT,60) .NE. 0) THEN
TYPE *,'Connect error: ',NETERR
CALL EXIT(1)
END IF
CALL GEP(1,EP,6)
IF (IP2HOS(EP,6,RNADR+RPORT,HOST,40) .NE. 0) THEN
TYPE *,'IP2HOST error: ',NETERR
CALL EXIT(1)
END IF
TYPE *,'Got connection - ',HOST
WRITE(5,30)
30 FORMAT('$FILE:')
READ (5,20) FIL
20 FORMAT(A40)
L = INDEX(FIL,' ')-1
OPEN (UNIT=2, FILE=FIL(1:L), STATUS='OLD', FORM='FORMATTED',
+ CARRIAGECONTROL='LIST', READONLY)
40 READ (2,45,END=100) K, (TXT(I),I=1,K)
45 FORMAT(Q,132A1)
D WRITE (5,50) (TXT(I),I=1,K)
WRITE (1,50) (TXT(I),I=1,K)
50 FORMAT(1X,132A1)
GOTO 40
100 CONTINUE
CALL PCRLF(1)
CALL PUSH(1)
CALL SCLOSE(1)
CLOSE (UNIT=2)
TYPE *,'Net Print Done.'
END
Thanks and Best regards,
Mark