2012-03-06 - Re: [GRASE-Hotspot] VM Ware Installation

Header Data

From: Tim White <ti***8@gmail.com>
Message Hash: bfd223b593231d5d25cb24232ee5221a3bf46bfd72a4bc42d56bbb3636603d90
Message ID: <4F568282.8070801@gmail.com>
Reply To: <2107147156.75034.1331064094579.JavaMail.open-xchange@email.1and1.co.uk>
UTC Datetime: 2012-03-06 14:32:50 UTC
Raw Date: Wed, 07 Mar 2012 07:32:50 +1000

Raw message 

Hi JS.

Its a bit harder to help when running in a VM as they can introduce all 
sorts of odd things (especially if it doesn't let normal layer 2 through 
as it's a virtual mac address).

Your host machine needs 2 network interfaces, one to the internet, and 
one to the "lan". Due to routing, it won't be able to test the hotspot 
from the host machine, as it's default gateway is obviously not the 
hotspot, and the network interface it has to the LAN needs to be under 
the control of the hotspot, so it can't also use that same network 
interface to talk to the hotspot.

The "WAN" interface on the host is setup like normal (wireless in your 
case). The LAN interface on the host again needs to not be setup for the 
host. (Unless someone who is running it differently successfully can 
correct me). The WAN interface on the guest needs to be a virtual one 
that uses the host as the gateway. The LAN interface on the guest needs 
to be the hosts LAN interface, at layer 2 (no ip routing to make it 
happen), referred to as bridged in virtualbox.

What I have found best for testing, is actually 2 virtual machines. One 
for the hotspot server (WAN interface is "natted" in virtualbox, and LAN 
interface is internal only) and the "testing" machine which has one 
network interface that is on the internal only network as well. This way 
your host machine isn't also trying to be your test machine, the test 
environment is confined to that one physical machine and it generally 
just works. Layer 2 routing between the host network and the guest 
network can just be so picky that I gave up in my test environment and 
just boot up multiple virtual machines. (Which helps as I don't normally 
have windows machines on my home network).

The only problem I see with your current setup is the "Host only" 
network interface, as this routing is Layer 2, VMware is probably not 
letting the correct Layer 2 stuff through, and even if it is, your host 
machine is probably confusing things.

Hope that makes some sense.

Tim

On 07/03/12 06:01, ju***c@vilasmolic.co.uk wrote:
>
> here is the scene:
>
> Workstation: Win XP or Win 7 running VMWare Workstation 7
>
> Hotspot Server: Ubuntu 11.10 VM running on Win XP or Win 7
>
>                 1 VM Network Point (one has access to internet 
> 192.168.124.129)
>
>                 1 VM Network Point (Host Only Setting 10.1.0.1)
>
>

Thread