Confused by network settings when running in VM

[StuntMonkeh]

I have followed the installation procedure as shown in the Wiki.

I cannot connect to the dashboard (http://hda) but Im guessing this must be because the host is on a different network segment.

The host machine is an Ubuntu machine running virtual box and is on a 192.168.1.xxx network.

I want the Amahi VM to sit on the same network i.e. 192.168.1.xxx

The problem is me not understanding how this is actually working.

[rjwaldren]

Accessing Amahi through the HDA alias is dependant upon Amahi acting as the DNS server.

Using Virtualbox I had luck with my pulling DHCP/DNS from the VM if I renewed my hosts adapter. (That's using a VB bridged adapter) You could also explicitly set the Amahi servers IP address in ubuntu's /etc/resolv.conf to ensure the VM is used for DNS resolution.

Before you try anything though make sure you can reach the amahi vm from the host. Ping and browse to the server by IP address.

[StuntMonkeh]

Checked the setup of the two VM network adaptors from the Amahi command line.

eth0 is 192.168.56.10
eth1 is 10.0.3.15

The VM host address is 192.168.1.117

Am I correct in thinking that I need to change the VM host address to one within the 192.168.56.xxx range to see the dashboard i.e. type 192.168.56.10 into the web browser address bar....

[rjwaldren]

I'm no pro at the host only adapter setup - was to limited for any real testing. If adapter is setup correctly on your chost you shown be able to access Amahi at 192.168.56.10, but only from the machine that is running the VM. If your only intending to test from your VM host machine the Wiki should be fine. If your looking to test from other machines on the network go with the bridged VM adapter. Note the last paragraph of the wiki page.

The Bridging adapter piggy backs on the physical host adapter and the VM's address can be within your 192.168.1 subnet with everything else. It will appear on the network just as though you were running on real hardware - start handing out addresses and handling DNS, etc.