You can simply use a separate script like the one above for each emulated machine, with “tap1” changed accordingly. To do this, use tap2, tap3, etc., instead of tap1 for every additional emulated machine, all added to the same bridge interface. You can run multiple networked emulated machines simultaneously on the same computer. The second bridge to go up may not work properly. 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. 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. You can use bridge1 without having a bridge0 interface. Note that bridge1 is used instead of bridge0 because OS X 10.9 Mavericks and up may have a “Thunderbolt Bridge” interface that uses bridge0. Remote clients over the Internet must use private IP addresses for the OpenVPN server side's LAN, not addresses for their own LAN, in the TCP/IP or MacTCP control panels. Sudo /*path to SheepShaver folder*/SheepShaver.app/Contents/MacOS/SheepShaver & sleep 10 For example, the script for starting SheepShaver in OS X 10.7 and up could look like: After connecting to the OpenVPN server, set the emulator to use tap1 as its ethernet interface, then bridge that interface as described in the AppleTalk guide with OpenVPN's tap0 interface instead of your ethernet interface.
0 kommentar(er)
