[Simh] Network interfaces under Windows

[Sergey Oboguev]

If you want to communicate between Windows host machine and SIMH, the easiest 
setup is Windows Loopback Adaptor (yes, with "o"). To avoid confusion by name, 
it is not an adapter that is associated with address 127.0.0.1, but a virtual 
Ethernet card driver that creates a subnet connected on one side to the Windows 
host machine, and on other side to applications, pretty much like TAP/TUN, but 
without the hassle.

Loopback Adaptor can be installed from Device Manager (on Windows 7, Action -> 
Add Legacy Hardware -> manually -> Network -> Microsoft -> Microsoft Loopback 
Adaptor, and there is similar sequence in XP).

Once the adapter is installed, assign its host-side address in Control Panel 
(something like 192.168.3.1/255.255.255.0), restart the machine to get PCAP to 
recognize it, then bind it on SIMH side the usual way, just as you would bind a 
physical adapter, and configure it inside VMS.

Note that there is a bug in SIMH 3.8.1 autoconfigure that causes mis-assignment 
of QBus device vectors when there are two XQ devices present and that may cause 
some other devices such as DHV stop working. I forwarded the fix some time ago 
to Robert Supnik, so if you run into the problem perhaps he could advise how to 
obtain the codebase that incorporates the fix.




________________________________
From: Timothe Litt <litt at ieee.org>
To: Stafford Winters <stafford.winters at gmail.com>
Cc: simh at trailing-edge.com
Sent: Wed, December 21, 2011 11:03:36 AM
Subject: Re: [Simh] Network interfaces under Windows

Your second interface probably doesn't have an IP address assigned (under
windoze); annoyingly, libpcap doesn't return interfaces without addresses.

Be careful picking a subnet.

Alternatively, you don't actually need a dedicated interface.  I use OpenVPN
(just install the TAP adapter & bridge it to your primary ethernet card).
You don't need the whole OpenVPN package.  Don't forget to set the Media
Status of the TAP to Always Connected, and things just work.


---------------------------------------------------------
This communication may not represent my employer's views,
if any, on the matters discussed. 

-----Original Message-----
From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-edge.com]
On Behalf Of Stafford Winters
Sent: Wednesday, December 21, 2011 13:48
To: simh at trailing-edge.com
Subject: [Simh] Network interfaces under Windows

I've had SimH for several months, running VAX (including ethernet
support) with OpenVMS installed.  (WinPcap is installed.)  I decided I
wanted to add a second network card so that I could telnet in from the same
computer to the OpenVMS system.  I had a Dynex DX-E102 available, so I stuck
it in the computer, but I don't see it as an available network interface
under SimH.  The primary network interface is an integrated NVIDIA nForce
10/100/1000.  To complicate matters, I have old VMware Player software
installed (version 1.0.2.xxxx) that allows me to run some necessary software
for a client.  The host computer is running Windows XP Professional x64
Edition.  Under SimH:
sim> show xq eth
ETH devices:
   0  \Device\NPF_{4EBEA91C-BB4D-4EB4-A3D0-D44914480A2F} (Local Area
Connection)
   1  \Device\NPF_{237514F4-8533-43C8-A69E-E94618353E5F} (VMware Network
Adapter VMnet8)
sim>
The Local Area Connection is the NVIDIA NIC.  Am I not able to additional
network interfaces because of VMware, or is the Dynex NIC not usable for
this, or is it something else altogether?

I realize this is a bit on the fringe for SimH discussion, but I haven't
been able to find anything that seems promising in my internet searches.
Thanks for any pointers you can provide.
_______________________________________________
Simh mailing list
Simh at trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

_______________________________________________
Simh mailing list
Simh at trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20111221/d5e108fd/attachment-0002.html>