Changes between Version 4 and Version 5 of doc/TorBOX/VMware


Ignore:
Timestamp:
Sep 27, 2012, 11:50:01 PM (7 years ago)
Author:
proper
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/TorBOX/VMware

    v4 v5  
    1 [[TOC]]
    2 [https://trac.torproject.org/projects/tor/wiki/doc/TorBOX aos Homepage]
     1TorBOX has been renamed to Whonix.
    32
    4 '''This is a draft/scratchpad, NOT a usable tutorial!
    5 Uncompleted and heavily outdated.
     3This page has been moved. The History of this page might still be interesting.
    64
    7 = aos.ova's imported into VMware =
    8 [http://utup22qsb6ebeejs.onion/?x=entry:entry120401-121133 Recent test results using aos/Download.] [[BR]]
    9 '''Not recommend!
    10 
    11 = manual configuration =
    12 == aos with VMware instead of VirtualBox ==
    13 Tested using VMware Workstation 8.
    14 
    15 == Harden VMware ==
    16  * Remove printer
    17  * Disable 3D acceleration
    18  * Remove CD/DVD drive (after installation)
    19  * Remove floppy drive
    20  * Remove USB controller (at least disable automatically connect new devices)
    21  * Remove sound card
    22  * Do not install VMware Tools or open-vm-tools (comfort vs. security)
    23 
    24 == aos-Workstation ==
    25  * Connect the virtual network adapter to custom.  This is important! No host-only, no NAT, no bridging! I used VMnet9 virtual network, as it wasn't used by anything else.
    26  * Verify you CANNOT ping any external hosts.  Verify that the aos-Workstation is isolated from the network and the Internet.
    27 
    28 The important part is to setup a fixed IP for the virtual LAN network card and to use the same subnet like the aos-Gateway for VMnet9. Type 'nano /etc/network/interfaces'
    29 
    30 {{{
    31 # source: https://trac.torproject.org/projects/tor/wiki/doc/TorBOX
    32 
    33 # This file describes the network interfaces available on your system
    34 # and how to activate them. For more information, see interfaces(5).
    35 
    36 # The loopback network interface
    37 auto lo
    38 iface lo inet loopback
    39 
    40 # VMnet9
    41 auto eth0
    42 #iface eth0 inet dhcp
    43 iface eth0 inet static
    44 address 192.168.0.2
    45 netmask 255.255.252.0
    46 gateway 192.168.0.1
    47 }}}
    48 
    49 
    50 More configuration is required for the aos-Gateway server. Add three? virtual network cards before you install.
    51  * first one (will be called eth0 in linux): NAT
    52  * second one (will be eth1 in linux): Custom VMnet9 (No host-only, no NAT, no bridging!).
    53 
    54 == aos-Gateway ==
    55 '''eth0 configuration notes:'''
    56 for 'address': Go to VMware Workstation -> Edit -> Virtual Network Editor -> click on
    57 (in my case it was VMNet8) NAT -> click on DHCP Settings -> look at 'Start IP Address' and
    58 'End IP Address' the IP you choose here must be within the range of 'Start IP Address' and 'End IP Address' the 'Start IP Address' might not work, in that case use it's successor or any other.
    59 
    60 for 'netmask': No change for the netmask should be needed, to be sure go to VMware Workstation -> Edit -> Virtual Network Editor -> see at subnet mask in the right corner
    61 
    62 for 'gateway': Go to VMware Workstation -> Edit -> Virtual Network Editor -> click on (in my case it was VMNet8) NAT -> click on NAT Settings -> see 'VMware Gateway IP'
    63 
    64 
    65 Configure your network interfaces. 'nano /etc/network/interfaces':
    66 
    67 {{{
    68 # source: https://trac.torproject.org/projects/tor/wiki/doc/TorBOX
    69 #
    70 # comments start with a hash '#' and are ignored
    71 
    72 # This file describes the network interfaces available on your system
    73 # and how to activate them. For more information, see interfaces(5).
    74 
    75 #
    76 # - the loopback network interface -
    77 #
    78 #Enter this configuration:
    79 auto lo
    80 iface lo inet loopback
    81 
    82 #
    83 # - nat internet device -
    84 #
    85 # This device will connect to the internet and may be also connected from the host for SSH administration.
    86 #
    87 #Enter this configuration:
    88 auto eth0
    89 iface eth0 inet static
    90 address 192.168.161.128
    91 netmask 255.255.255.0
    92 gateway 192.168.161.2
    93 
    94 #
    95 # - vmnet9 -
    96 #
    97 # This device will only communicate with the aos-Workstation.
    98 #
    99 #Enter this configuration:
    100 auto eth1
    101 iface eth1 inet static
    102 address 192.168.0.1
    103 netmask 255.255.252.0
    104 }}}
    105 
    106 One might wish to access the aos-Workstation through SSH. Therefore he could add a second network adapter with [http://www.vmware.com/support/ws55/doc/ws_net_configurations_hostonly.html Host-Only Networking]. Beware
    107 {{{
    108 If you install the proper routing or proxy software on your host computer, you can establish a connection between the host virtual Ethernet adapter and a physical network adapter on the host computer. This allows you, for example, to connect the virtual machine to a Token Ring or other non-Ethernet network.
    109 
    110 On a Windows 2000, Windows XP or Windows Server 2003 host computer, you can use host-only networking in combination with the Internet connection sharing feature in Windows to allow a virtual machine to use the host's dial-up networking adapter or other connection to the Internet. See your Windows documentation for details on configuring Internet connection sharing.
    111 }}}
    112 
    113 = Testing =
    114  * Try restarting your various virtual machines (power on and off the virtual machines), at times VMware networking can give you headaches
     5https://sourceforge.net/p/whonix/wiki/VMware/