Hi all.

Please refer to http://www.linuxquestions.org/questi...vm-4175425590/ for the initial way that I got my internet working on a Debian-Squeeze VM, installed on a Fedora-14 guest.


Now, when I ping the guest from my VM, via ::

(where 192.168.1.2 is the IP-Address of my guest machine), it works;




but when I do the other way round ::

the guest machine fails to ping the VM.







For brevity, I am attaching the output of ifconfig of my Debian VM ::


Any ideas what I may be doing wrong?
I will be grateful.


Thanks and Regards,
Ajay

It appears you may be using two separate subnets and if so may require additional routing.

Your VM has an IP range: 192.168.4.0 - 192.168.7.255 for the subnet you've given based on its IP and Netmask. You can get calculations for CIDRs like this at:
http://www.subnet-calculator.com/cidr.php

You don't tell us what your NIC on the guest is setup for but since the IP is 192.168.1 it is NOT in the same subnet as above.

You might want to provide netstat -rn output for both the VM and the guest as well.

Also it may be a firewall issue. Do you have iptables enabled on the VM and if so is it allowing ICMP from the IP or subnet of the guest?

Finally it often helps when saying something doesn't work to give the actual command run and the output you saw. From what you wrote we might assume you did a ping of IP but if instead you did a ping of hostname and it resolved the wrong IP your issue could be a hosts or name resolution issue. By providing the actual command and output it helps keep people from asking you questions.

I don't follow you because of the mixed and/or misused terminology that makes this ambiguous. Are you doing the ping from host OS or the guest OS?

Your linked post mentions host. Here you mention guest. In both cases you mention VM. This is why it is so confusing as to what exactly you are doing.

There should be:
1. A host system.
2. Another host system on a separate machine on the same LAN so you can check from an outside perspective, if you have such a machine to use.
3. Virtual machine software (e.g VirtualBox)
4. A guest system with a different instance of OS (maybe a different OS, different distro, different architecture, or different version).

There should be a lot of configuration and diagnostic information:
1. ifconfig output from each system
2. route output from each system
3. ARP table dumps from each system
4. tcpdump outputs from various points, including bridges and/or tunnels
5. interface statistics in flux

Same issue.

I'm wondering if your VM engine is where you are doing pings from and to. I haven't heard of such a feature (though that does not mean there isn't). But I would not know the context of how a virtual machine program would carry out performing a ping (does it do an ARP request or assume knowledge of the MAC address of the guest) or responding to one (is it configure with an IP address, too)?



Is that the guest or host?

Unless you have a specific reason to do separate subnets and routing to virtual machine guests, I recommend bridging them to the host LAN connection, and using IP addresses from a LAN subnet (maybe just allow DHCP). This keeps things simple. Simple tends to more likely just work. Simple is easier to explain to others.

Thanks MensaWater and Skaperen for the replies.
And sorry for my ambiguous terminologies


Let me clear myself ::

a)
Fedora-14 is my host machine (machine over which VirtualBox is installed, into which Debian Squeeze VM has been set up)


b)
Debian Squeeze is my guest machine (VM).



Now, as I said that I could get the internet working only by setting the "Bridged Adapter" to NAT.



Also, I will prevent putting other details here (as requested by Skaperen). This is because I made some progress, as follows ::

(i)
Firstly, the thing I am trying to achieve is setting up a Webdav share on the VM, which should then be accessible from the host machine, via Firefox.


(ii)
Now on the VM (guest machine), I managed to configure the conf files correctly (I think). I say "correctly", because after a lot of huffs and puffs, I was able to "/etc/init.d/apache2 restart" successfully.


(iii)
On the VM, I disabled the auto-startup of firewall. So, on reboot, "iptables -L" show no configured rules.


(iv)
Also, on Fedora-14 VirtualBox settings, I enabled "Port Forwarding", with


(v)
Now, when I type "https://127.0.0.1:8080/webdav" in the URLBar of Fedora-14, the bottom-bar shows "Connected to 127.0.0.1..."; however, I do not get the typical webdav layout. Well, I am not even asked for the "certificate acceptance" thing that happens when connecting to a secure-webdav network for the first time.

Note that if I try with "http" instead of "https"; or any other port besides 8080, the bottom-bar just shows "Connecting to 127.0.0.1..."; it's only when it is "https://127.0.0.1:8080/webdav", does it show "Connected to 127.0.0.1". So, I guess there is some form of "acknowledgement" happening; just bad that it's not going the full way :-\


I am again sorry (especially Skaperen) for being unclear the last time :-\

I will be grateful to listening back from you.



Thanks and Regards,
Ajay

If you pinged it one way it really did return the ping correctly. Ping is a very poor two way test. It is not a single way test.