User manual

OS X

and follow the installer’s screens. After installing

tuntaposx, optionally execute command kextstat

to display a list of all loaded kernel extensions and make sure that tap and tun extensions had been

successfully loaded.

After installing tap interface, add the following lines to your VAX MP startup script:

set xqb enabled

set xqb mac=08-00-2b-aa-bb-c2

set xqb type=delqa

attach xqb tap:tun0

! ifconfig tap0 192.168.21.3 up

Note the space in the last line after “!”.

The latter line is executed by VAX MP as shell command and causes interface tap0 to be configured with

specified address. You can then configure OpenVMS TCP/IP Services interface QE1 (mapped to XQB)

with IP address let us say 192.168.21.100:

$ TCPIP SET INTERFACE QE1 /HOST=192.168.21.100

$ TCPIP SET CONFIGURATION INTERFACE QE1 /HOST=192.168.21.100

Host and VAX MP can cross-reference each other using these addresses, but they are not visible outside

of the host machine unless you set up a routing between this internal subnet and exterior network.

Described set-up follows the scheme described in network setup chapter for Windows, and the chart

from Windows chapter equally applies to the described OS X setup.

Remember that the use of TAP/TUN on OS X requires VAX MP to be run as root (e.g. via

sudo).

OS X currently does not have builtin or 3

party open-source freeware facilities for Ethernet bridging,

like in the setup suggested for Linux above. However there is a commercial product that provides

Ethernet bridging under OS X: IPNetRouterX.

It may allow to implement network set-up with single

network address for each of the host machine and VAX MP, rather than two addresses for each, but we

have not tested neither this product nor the possibility of using it for such setup under OS X.

Finally, if you are using a firewall, remember to configure the firewall so it allows required connections

to/from addresses of the added VAX instance or instances.

http://www.sustworks.com/site/prod_ipnrx_overview.html