Author |
Getting network access working in SIMH Vax |
Dutchman2000
Member
Posts: 2
Joined: 01.04.20 |
Posted on April 06 2020 19:54 |
|
|
I'm trying to get my windows machines to see the SIMH Vax but I can;t seem to get it working. Any tips? Ultimately I need to transfer data from the emulated VAX to my windows desktop.
What is the easiest way to do this? |
|
Author |
RE: Getting network access working in SIMH Vax |
Bruce Claremont
Member
Posts: 623
Joined: 07.01.10 |
Posted on April 07 2020 04:19 |
|
|
The easiest way is to use two NICs. Disable Windows network services on the NIC assigned to SimH VAX. |
|
Author |
RE: Getting network access working in SIMH Vax |
malmberg
Moderator
Posts: 530
Joined: 15.04.08 |
Posted on April 16 2020 13:33 |
|
|
I use virtualbox with a small linux instance and then run SimH in that Linux instance.
Allows you to have 4 NICs on the Linux VM.
Nic 1. Bridge to your primary network interface for Linux to reach your outside network.
Nic 2. Internal network for Linux VM to SimH and to Window host system.
Nic 3. Bridge to your primary network interface for SimH/VAX to reach your outside network
Nic 3. Internal network for SimH to Linux and Windows.
|
|
Author |
RE: Getting network access working in SIMH Vax |
sgcyphers
Member
Posts: 1
Joined: 25.04.20 |
Posted on July 03 2020 14:32 |
|
|
Bruce's two NIC idea works. I also use a 5-port Switch and plug the two NICs into it to reduce network traffic on the rest of my network.
I have found "cookbooks" on how to set up SIMH on Linux (and OSX and R-Pi) but nothing for setting up SIMH on Windows 10 (Windows 10 removed the NDIS5 drivers, so you need npcap instead of WinPcap).
When I get a couple of solutions figured out, I hope to write a SIMH/Windows10 Cookbook and post it somewhere useful.
I've been banging my head long enough, I'm even considering mr. malmberg's option! |
|
Author |
RE: Getting network access working in SIMH Vax |
malmberg
Moderator
Posts: 530
Joined: 15.04.08 |
Posted on August 29 2020 09:37 |
|
|
I run SimH/VAX in an LxD container, where the LXD handles all the networking.
Somewhere on the Sourceforge VMSPORTS project WIKI are more details.
Ubuntu 16 originally broke LXD for privileged containers. I do not know if they fixed it.
Will be trying soon Lxd on a Raspberry PI. |
|