User manual

OS X

$ ls –l /dev/bpf*

crw-rw---- 1 root pcaprw 23, 0 Jul 10 09:37 /dev/bpf0

crw-rw---- 1 root pcaprw 23, 1 Jul 9 21:37 /dev/bpf1

crw-rw---- 1 root pcaprw 23, 2 Jul 9 21:37 /dev/bpf2

crw-rw---- 1 root pcaprw 23, 3 Jul 9 21:37 /dev/bpf3

Then follow instructions in tcpdump.org documents at links mentioned above to set up chmod_bpf for

automatic execution each time the system restarts.

Assuming your host machine’s Ethernet interface is en0, add the following lines to your VAX MP startup

script:

set xq enabled

set xq mac=08-00-2b-aa-bb-c1

set xq type=delqa

attach xq en0

Only Ethernet NICs and virtual Ethernet adapters such as TAP adapters can be attached to XQ or XQB for

mapping virtual DEQNA or DELQA adapter. Host WiFi interfaces might superficially look similar to

Ethernet interfaces but they are actually not Ethernet and cannot be used for VAX MP or SIMH Ethernet

networking.

Assuming for the sake of example that your host machine’s IP address is 192.168.1.100, you can

configure OpenVMS TCP/IP Services QE0 interface with IP address 192.168.1.110 or any other address

either in the same subnet or in another subnet, for instance:

$ TCPIP SET INTERFACE QE0 /HOST=192.168.1.110

$ TCPIP SET CONFIGURATION INTERFACE QE0 /HOST=192.168.1.110

Depending on exact value of network addresses being used and network topology it may be necessary

to additionally specify options

/NETWORK_MASK=x.y.z.w and /BROADCAST_MASK=m.m.m.m.

Under OS X

libpcap bound to host NIC allows VAX MP to communicate only with other computers, but

not with the host computer itself.

Libpcap captures Ethernet packets arriving to the NIC from external

nodes and forwards them to both VAX MP and the host machine, but OS X network kernel does not fully

interchange packets between the host machine and VAX MP. Packets sent by VAX MP via NIC are not

made visible to the host machine by OS X network stack. Thus

libpcap bound to host machine’s NIC

allows VAX MP to communicate with other machines on the network but establishes no usable link

between host machine and VAX MP.

To enable network connection between the host machine and VAX MP one can optionally configure TAP

interface. This requires installation of open-source 3

party component: tuntaposx by Mattias Nissler.

The use of this component requires running VAX MP as root.

To install

tuntaposx navigate to http://tuntaposx.sourceforge.net, click “Download” and then click the

link to download current release. As of time writing this, this link leads to

http://downloads.sourceforge.net/tuntaposx/tuntap_20111101.tar.gz. After downloading the tar file,

decompress and expand tar file to a temporary directory. Double-click on file tuntap_yyyymmdd.pkg