Emaculation.com
 

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
wireless_appletalk_ss_bii_osx [2014/05/31 18:43]
nucar
wireless_appletalk_ss_bii_osx [2015/04/04 21:42]
nucar [How It Works]
Line 1: Line 1:
 ====== Wireless AppleTalk Networking with SheepShaver & Basilisk II for OS X ====== ====== Wireless AppleTalk Networking with SheepShaver & Basilisk II for OS X ======
  
-(Last updated May 312014.  The forum thread is [[http://www.emaculation.com/forum/viewtopic.php?f=20&t=8324|here]].)+(Last updated April 52015.  The forum thread is [[http://www.emaculation.com/forum/viewtopic.php?f=20&t=8324|here]].)
  
 ===== Introduction ===== ===== Introduction =====
Line 11: Line 11:
 A bridge-mode OpenVPN server can tunnel any ethernet frame over a single port, preferably a UDP port.  Therefore, AppleTalk packets, encapsulated into UDP packets, can survive over the IP-only wireless signal.  This also implies that all ethernet activity on the network can be extended over the Internet to remote OpenVPN clients. A bridge-mode OpenVPN server can tunnel any ethernet frame over a single port, preferably a UDP port.  Therefore, AppleTalk packets, encapsulated into UDP packets, can survive over the IP-only wireless signal.  This also implies that all ethernet activity on the network can be extended over the Internet to remote OpenVPN clients.
  
-Obviously the main challenge here is to set up the OpenVPN server. A bridge-mode OpenVPN server is an extremely powerful tool that everyone should know about.  It can be run using free software only and allows you to extend all layer-2 LAN communication over wireless and over the Internet.  The guide for setting up such a server in a Linux VM is here:+Obviously the main challenge here is to set up the OpenVPN server. A bridge-mode OpenVPN server is an extremely powerful tool that everyone should know about.  It can be run using free software only and allows you to extend all layer-2 LAN communication over wireless and over the Internet.  The guide for setting up such a server in a Linux VM (on a Mac or Windows PC) is here:
  
 http://www.emaculation.com/doku.php/bridged_openvpn_server_setup http://www.emaculation.com/doku.php/bridged_openvpn_server_setup
  
 To be clear, the VPN must make use of ethernet bridging.  Most VPNs are the layer-3 routed type and will not work. To be clear, the VPN must make use of ethernet bridging.  Most VPNs are the layer-3 routed type and will not work.
- 
 ===== Connecting the Emulator to the VPN ===== ===== Connecting the Emulator to the VPN =====
  
-After connecting to the OpenVPN server, set the emulator to use tap1 as its ethernet interface, then bridge that interface as described in [[http://www.emaculation.com/doku.php/appletalk_for_sheepshaver|the AppleTalk guide]] with OpenVPN's tap0 interface instead of your ethernet interface. For example, the script for starting SheepShaver in OS X 10.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 [[http://www.emaculation.com/doku.php/appletalk_for_sheepshaver|the AppleTalk guide]] with OpenVPN's tap0 interface instead of your ethernet interface. For example, the script for starting SheepShaver in OS X 10.and up could look like:
  
 <code>sudo /*path to SheepShaver folder*/SheepShaver.app/Contents/MacOS/SheepShaver & sleep 10 <code>sudo /*path to SheepShaver folder*/SheepShaver.app/Contents/MacOS/SheepShaver & sleep 10
Line 27: Line 26:
 sudo ifconfig bridge1 up</code> sudo ifconfig bridge1 up</code>
  
-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 and later may have 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 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. 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.
wireless_appletalk_ss_bii_osx.txt ยท Last modified: 2015/04/04 21:48 by nucar
 
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki