Posted by under Emulation,Networking,OpenVMS,SIMH,TCP/IP,VAX on June 1 2012, 0 comments

It is time to get TCP/IP up and running on the PIVAX. So once again I’m cribbing this from Phil Wherry’s guide to running VMS on SIMH and Linux.

(Note, from now on PIVAX is the simulated VMS machine, and vax-pi is the Raspberry Pi on which it runs.)

The fake MAC address of PIVAX is 08:00:2B:AA:BB:CC, and its’ IP address will be vax-pi lives at (cabled) and (wifi).

Side note: I’m a bit OCD about my network addresses. I’ve allocated blocks of ten for various types of computers. Hence Desktop start at 100, Laptops (wifi) at 110, Laptops (wired) at 120, Raspberries at 130, Virtual machines at 140, Phones etc at 150, 160-199 is reserved for the various machines of the other people in the house, 200+ for servers. Yes, I know its sad. So is drawing a map of where the machines are (both logically and physically), but it really helps when something goes wrong.

Anyway, we’re going to need more system resources, so:

$ set proc/priv=all
$ set def sys$system
$ edit modparams.dat

Add these lines to the file:


Now run AUTOGEN to update the system

$ set def sys$update
$ @autogen getdata shutdown nofeedback

After all that is done, we’ll need another boot cpu and some more twiddling:

$ set proc/priv=all
$ r sys$system:sysgen
$ @sys$system:shutdown

And another shutdown/boot cycle.

Now finally the time has come to get TCP/IP installed, so:

$ set proc/priv=all
$ mount/over=id dua3:
$ set def dua3:[tcpip_vax051.kit]

If you need to install your UCX license (ie, you didn’t do it when I told you to in the last post, do it now), then:

$ product install *

and accept the defaults. Then go and have a sleep, or watch an entire episode of Chuck. It really might take that long.

So, after Adam Baldwin has grunted a few times and probably shot someone, and Yvonne Strahovski has pranced about in her skivvies:

$ @sys$manager:tcpip$config

Most of this stuff should be obvious, so I’m not going to go through it, except to say that I always use something like wopr.loc as the domain name for machine that don’t actually connect directly to the Internet. This allows me to run a local nameserver to deal with the vast collection of knackered machines in the house. If you really want a walkthrough, see Phil Wherry’s site.

You know your own IP address, gateway, BIND server etc.

Next, you’ll want to enable FTP, TELNET (client and server) etc from the menu system. I wouldn’t bother with SMTP yet, as I’ve never got it to work correctly. I may try it later.

I enabled the FINGER service just so that I could redirect port 79 through my router to the PIVAX (along with port 23 – telnet).

Now edit sys$ and add this at the end:


.. and all should be good. FTP and TELNET should work fine (if you’re cabled up). If you’re using a WiFi network interface, things are a bit different. I’ll go in to that some other time.

Note: at this point you cannot directly communicate between the vax-pi and PIVAX, even if you have an ethernet cable plugged in and a WiFi thingummy fitted. This doesn’t bother me, as the whole purpose of vax-pi on my network is to host PIVAX. Oh, and run AberMUD. And maybe emulate some other Old Iron.