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 =====

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 and later may have a "​Thunderbolt Bridge"​ interface that uses bridge0. You can use bridge1 without having a bridge0 interface.

+

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. 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. 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.