Emaculation.com

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
wireless_appletalk_ss_bii_osx [2014/05/31 18:42] – nucarwireless_appletalk_ss_bii_osx [2014/05/31 18:43] – nucar
Line 29: Line 29:
 Remote clients over the Internet must use the private IP addresses for the OpenVPN server side's LAN, not addresses for their own LAN, in the TCP/IP or MacTCP control panels. Note that bridge1 is used instead of bridge0 because OS X 10.9 Mavericks sets up a "Thunderbolt Bridge" interface that uses bridge0. You can use bridge1 without having a bridge0 interface. Remote clients over the Internet must use the private IP addresses for the OpenVPN server side's LAN, not addresses for their own LAN, in the TCP/IP or MacTCP control panels. Note that bridge1 is used instead of bridge0 because OS X 10.9 Mavericks sets up a "Thunderbolt Bridge" interface that uses bridge0. You can use bridge1 without having a bridge0 interface.
  
-In order to run the Linux VM and a networked emulator in the host OS simultaneously, the host must connect to the OpenVPN server as a client, and connect the emulator using the method below.  The regular method of bridging the ethernet interface with the emulator's TAP interface cannot be used because a single ethernet interface cannot be a member of a bridge interface in the host and a bridge interface in the VM simultaneously.  The second bridge to go up may not work properly.+In order to run the Linux VM and a networked emulator in the host OS simultaneously, the host must connect to the OpenVPN server as a client, and connect the emulator using the method above.  The regular method of bridging the ethernet interface with the emulator's TAP interface cannot be used because a single ethernet interface cannot be a member of a bridge interface in the host and a bridge interface in the VM simultaneously.  The second bridge to go up may not work properly.
  
 You can run multiple networked emulated machines simultaneously on the same computer.  For example, you could run multiple .sheepvm files and/or Basilisk II.  To do this, use tap2, tap3, etc., instead of tap1 for every additional emulated machine, all added to the same bridge interface.  You can simply use a separate script like the one above for each emulated machine, with "tap1" changed accordingly.  Don't forget that each emulated machine must be given a unique IP address. You can run multiple networked emulated machines simultaneously on the same computer.  For example, you could run multiple .sheepvm files and/or Basilisk II.  To do this, use tap2, tap3, etc., instead of tap1 for every additional emulated machine, all added to the same bridge interface.  You can simply use a separate script like the one above for each emulated machine, with "tap1" changed accordingly.  Don't forget that each emulated machine must be given a unique IP address.