VirtualBox on Freenas vm - virtualbox

I have a FreeNAS vm running in ESXi 6. I have installed VirtualBox jail on FreeNAS and assigned it a static IP.
I can ping that IP from shell in FreeNAS, but not from any of my other virtual machines.
They are all on the same subnet.
What can I try to fix this?

Firstly, FreeNAS should not be installed within a VM environment especially for production systems. This is also mentioned repeatedly on FreeNAS support and forums. I hope you are just conducting testing.
Back to your question, have you checked your firewalls / routing on your ESXi VMs, VB VMs, FreeNAS? I haven't tried this particular configuration before but typically its incorrect network settings that prevent pings. Have you tried dynamic IP?

Related

Unable to access ESXi-7 with web client

After installing VMware ESXi 7 with VMware Workstation, I can't access it from web client from the displayed IP.
This is my IPv4 configuration.
Any idea how to fix this?
Try to ping your ESXi, check your network configuration gateway and IP address.
How did you configure vmware workstation ? I guess your issue come from your network configuration on vmware workstation.
This documentation may help you to choose the right network to use on Vmware Workstation for your need. https://docs.vmware.com/en/VMware-Workstation-Player-for-Windows/16.0/com.vmware.player.win.using.doc/GUID-C82DCB68-2EFA-460A-A765-37225883337D.html
Add https:// before the IP address.

Issue setting up Open vSwitch on GCE (DHCP client not working)

I am trying to simulate an on-premises solution on GCP.
I am not able to bridge with the GCE NIC and get DHCP working on that.
I have isolated the issue and also successfully tests the similar thing on a sandboxed Vagrant (VirtualBox) setup.
Both approaches are scripted and available on the following repos:
https://github.com/htssouza/ovs-gcp-issue
The DHCP functionality for Compute Engine only provides and manages the IP address for the instance itself. It does not function as a general purpose DHCP server for other clients running hosted inside the instance.

Google cloud virtual instance cannot ping my Mac (checked firewalls)

I have a virtual machine instance running on Google Cloud Compute Engine — a preemptible free-tier CPU running Ubuntu 17.04. The end goal is to connect it to a MongoDB running on my local machine, a 2015 Macbook Pro (OS 10.12.6). But first, I've been trying to ensure the VM can reach my Mac via ping.
Running ping <VM's external IP> from my Mac works.
pinging my Mac from another Mac on the same wifi network works.
Running ping <Mac's IP> from the VM via the browser terminal does not work.
I've disabled my Mac's firewall. I've also configured my VM's firewall rules to allow all inbound and outbound traffic, to no avail:
ingress firewall rules, egress firewall rules
How might I get this instance to ping my Mac successfully?
Does your Mac's IP address begin with 10., 192.168., or between 172.16. and 172.32.? These are private addresses only reachable within your Mac's local network, which is (part of) why GCE cannot reach your VM.
This is part of a very common configuration. An ISP only allocates one (or a small number) of IP addresses to your home or business. A router on the network performs NAT to share that IP addess between computers on the local network, which instead use private IP addresses for themselves. As the router doesn't know what to do with the inbound MongoDB traffic, it blocks it.
There are two common ways around this that are usually found in your router settings:
"port forwarding" where you tell the traffic to forward all traffic on port 1234 to your Mac. This can get MongoDB working, but not ping.
If you have whole extra IP addresses, "DMZ" where your router directly forwards an entire extra IP to your instance. If you have only one IP address this is not an option as that IP is needed to be shared for other devices on the Wifi.
You likely also have a firewall on the router. If you use a DMZ or port-forwarding you must make sure that firewall allows traffic through too.
That said, I'm not sure that this is a sensible thing to do. Opening up your local network to the internet can create major security issues, plus it is likely unreliable more expensive (free tier only provides 1GB egress/month, your db traffic could exceed this).
Actually running MongoDB on instances within GCE is almost certainly a better option in every regard for you.

Can't manage to connect my virtual machine to the internet

I have a windows server 2003 as the guest in VMware player and windows 7 enterprise as the host. I'm trying to connect to the inernet from my guest and i can't. In my VMware player virtual machine settings my network addapter is set to NAT but i can't get it to work.My host is in the work LAn and connected to the internet through it. Could this have something to do with it not working properly? Do I have to perform some special setup?
The problem may be caused by:
You're NATting to the wrong host's network interface in the VM's option.
Your VM's NIC DNS configuration is wrong. To verify this issue, try to PING the host's NIC from the VM.

VM Communicating with Another VM

I have two separate VMs created with VMWare Fusion. One is running Windows 7. The other is running Centos. I have an application on the Centos VM that needs to communicate with resources on the Windows VM. Does anyone know how I can setup communication between the VMs?
Your Fusion virtual machines all get IP addresses from DHCP by default. So, just use what you would to get resources if they were different machines.