Virtualbox пинг виртуальной машины

As you can see in the table above, for NAT option, there is no connection to the host (row 4, column 1). To understand why that is the case let’s see what NAT is, what is the need for NAT, how it works and what is the reason its chosen as default by the developers of VirtualBox.

NAT Basics

What is NAT? NAT stands for Network Address Translation. This is a protocol that is used on routers to translate between 2 sets of IP addresses namely public and private IP addresses. It does that using the concept of Port forwarding.

Need for NAT

As we know an IP version-4 address (ipv4) is 32 bits long. This means we can have up to 2^32 combinations, which comes to about 4,294,967,296 or 4 billion unique addresses. But since we are living in the internet age and each one of us has about 5 devices per person (office laptop, home laptop, mobile phones, smart TVs, desktops, tablets, etc) connected to the internet. Hence we need more than 4 billion addresses which is possible through ipv4. To overcome this issue, the engineers came up with ipv6 addresses, which are 64-bit address, so we can have around 18,446,744,073,709,551,616 devices. This number is more than the number of grains of sand in all the beaches all over the world so we should be good with ipv6 for the foreseeable future!

But like all technologies, adapting to ipv6 addresses is gonna take some time. This is where NAT comes in. If you go ahead and type in google what is my IP? You will see a result that is different than the one shown if you type in ifconfig command (if you are on Mac or Linux) or ipconfig (on windows) on the terminal.

In fact, if you go to any device on your Local Area Network (LAN) and google what is my IP? you will get the same IP address for all of the devices. This is the IP address of the router device provided by your Internet Service Provider (ISP) and not your computer.

This is because in our networks we use 2 sets of IP address namely private IP address and public IP address. The router translates between the private and public IP addresses using the NAT protocol so that it can send the results of your google search to your computer and not to your colleague’s computer!

The image below shows the hierarchy of IP addresses and the use of NAT

How NAT works?

To explain how it works briefly, the router keeps track of which computer requested what resource with the help of something called address translation tables so that when a network packet is received from the internet it can send the received packets to the correct computer on your local area network.

I hope you understood the need for NAT and how it conceptually works. The exact mechanisms of NAT and its various types are beyond the scope of this article, so let’s stop here. I recommend you to do more research on it if you are interested.

The problem

Keeping the default settings, I have booted up my ubuntu virtual machine and I got its IP using the ifconfig command as shown in the screenshot below.

In Linux, the inet addr is the IP address.

When I try to ping to this IP from my host OS (windows10), I get the following results.

As we can see from the screenshot above, my host windows machine cannot see the virtual machine on my network.

Let’s try pinging the other way. I got the IP of my windows machine using the ipconfig command as shown in the screenshot below.

Then I tried pinging this IP from the guest OS and you can see the screenshot below.

As you can see in the screenshot below, pinging from the guest OS to the Host OS is a success.

This is because VirtualBox uses the NAT protocol to translate between your Host OS’s IP and the Guest OS’s IP.

Reason only one side pinging works

Part of this NAT protocol is that NAT will only allow network traffic originated from the inner side of the NAT.

For example, when you open up your browser and go to google.com, you are sending a request to the google server from the inner side of the NAT (LAN side) and the router sends this request forward to the Google server which is in the outer side of the NAT (the internet) and once the server sends the requested page back, your router sends it back to your computer.

The diagram below shows the hierarchy of NATs in a typical network with devices being the physical computers and vm’s being the virtual machines running inside physical computers.

Reason NAT is chosen as default

In a typical organization, you can see several computers running multiple vm’s on each computer. They also usually have a strict networking policy to allow only authenticated devices to have access to the LAN for security reasons. If developers need to talk to network administrators every time they wish to make a virtual machine, then this process will get tedious for everyone.

Thus by using NAT, you can have as many virtual machines running as you desire and you are not using up any of the IPs in your LAN. In other words, VirtualBox attempts to create a sub-network under your local IP using NAT so that

Need#2 for NAT

This brings us to the Need#2 of NATs, which is that nobody from outside your LAN can initiate a session with your computer and nobody from the internet can hack your computer.

Now let’s extend the analogy of the internet & LAN to your host & guest OSes. In the same way, you can initiate a session from your LAN to the internet but not the other way around, your guest OS can talk to machines on the outside of the NAT, in our case the Host OS, but not the other way around. I hope you got the point.

The Solution

But what if you need to set up a network app like a web server or a file server inside the virtual box so that your colleagues can access it from their machines? Or maybe you need to log into your virtual machine remotely over SSH?

Then you need the virtual machine to act as a separate computer on the LAN as shown in the image below.

To achieve that, you need to change the option from NAT to Bridged Adapter as shown in the screenshot below.

After changing the settings again, I have booted up my ubuntu virtual machine and I got its IP using the ifconfig command as shown in the screenshot below.

Now to test if it works, go to the command line again and try pinging the IP to see if it works. When I try to ping to this IP from my host OS (windows10), I get the following results.

So now I can ping to my guest OS from my host OS.

The short version of the answer

To summarize the solution you need to follow these steps to be able to ping your virtual machine from any other device on your network

Step#1: Choose your virtual machine and click on settings

Step#2: Go to network settings

Step#3: Choose Bridged adapter

Step#4: Reboot the virtual machine

Step#5: Get the IP of the virtual machine and ping it to see if it works!

This is the easiest solution to just let the virtual machine be on the same level as other machines on your LAN. If you are doing this with your home network, it should work just fine. If you are doing it in your office be sure to check in with your network admin to make sure he opens up an IP for you if needed!

Did all the steps correctly and it still doesn’t work? then read on for some more settings you can change that might help make it work as you need it to.

Other settings that might help

1. Check your IP settings

Make sure they are in the same subnet and have the same DNS and gateway. If DHCP is enabled, then the virtual box should automatically get the correct IP settings(dns, gateway and ip addresses)

What is DHCP? DHCP stands for Dynamic Host Configuration Protocol. It’s a networking protocol that assigns IP settings to your device.

If it’s disabled on your guest OS, try enabling it and see if that solves the issues.

Since the process to change the DHCP settings on each OS varies a lot, I leave it to you to google and figure out how to change it.

2. Check your firewall

Configure firewall settings on the host OS to give all permissions to the virtual box app.

What is a firewall? It is a program that scans all the incoming network packers and only allows the ones as instructed by its settings.

I leave it to you to google and figure out how to do this for your specific Host OS.

3. Check your MAC address

MAC stands for Media Access Control, it is a unique address that is assigned to every hardware device capable of connecting to the internet.

Make sure that the MAC address as shown in the screenshot below is not a duplicate on your LAN. In other words, make sure that none of the other computers in your LAN has this MAC address.

A couple more workarounds

Wordaround#1: Try enabling promiscuous mode

This mode basically skips the internal processing of received packets and sends all the incoming packets straight to the CPU.

This can be done by changing the settings of VirtualBox as below.

But be careful as the promiscuous mode is set to deny for a good reason so that no one can hack into our machines. Make sure you don’t have sensitive data in your virtual box guest OS if you wish to turn it on.

You should be good to go as long as

Wordaround#2: Try sharing a folder

The host/guest OS combination that this workaround is found to work in is shown below

Guest OS: Windows XP or 7

Add at least 1 shared folder from guest to host

But this is not the best solution since its not practical as it can get tedious to share a folder to all the present and future devices that might need to connect to your virtual machine’s network-based service.

If you wish to connect to just one or 2 machines then its worth giving it a try.

There are other ways to get it to work. For example, if your goal is to just connect to your VirtualBox using SSH and not let all other machines on your LAN see your virtual machine, then you can always open port 22 on the NAT settings and connect to it from the particular machine of interest and keep it hidden to all other machines. You can learn more about how to accomplish that at this link.

Bonus Tip

One more tip before I conclude this article! Try enabling hardware virtualization on your Host PC’s BIOS if it supports it, as this will increase the performance of your VirtualBox. You can google how to do this, by searching “how to enable virtualization in ”

Alright, let’s stop here.

I hope you guys learned something through this post and hope it was useful to you guys.

You can email us or contact us through this link if you have any questions or suggestions.

If you liked the post, feel free to share this post with your friends and colleagues!

Источник

Настройка сети VirtualBox

VirtualBox позволяет на одном устройстве запустить несколько виртуальных машин с разными операционными системами. Виртуальные машины используют для тестирования нового ПО, для знакомства с особенностями разных ОС, а также для запуска программ, которые созданы для определённой операционной системы.

Какие типы подключения доступны в VirtualBox

В VirtualBox можно разными способами настроить интернет:

Для VirtualBox 6.1 доступны инструменты:

На одной виртуальной машине можно использовать до 4 сетевых адаптеров. Для каждого адаптера есть возможность выбрать любой тип подключения. Благодаря этому можно комбинировать настройки, выбирать разные варианты работы сети. Например, комбинировать NAT и сетевой мост. Ниже мы рассмотрим, как включить/отключить адаптер.

Как включить и отключить адаптер

1. Выберите гостевую ОС, кликните на неё правой кнопкой мыши. Нажмите Настроить:

2. В появившемся меню выберите Сеть:

3. Выберите адаптер, который хотите добавить или удалить. Затем переключите чек-бокс Включить сетевой адаптер в нужное положение. Если вы включаете новый адаптер, в выпадающем списке выберите тип подключения и нажмите OK:

Готово, гостевая ОС будет работать с выбранными адаптерами.

Как подключить виртуальную машину к интернету

Если вам нужен доступ только в интернет, можно использовать NAT-подключение. NAT изолирует виртуальную машину от соединений извне, поэтому доступа к другим гостевым ОС при таком подключении не будет. Проводником в интернет выступает хост-система, через которую и проходят все входящие и исходящие запросы.

В VirtualBox при создании каждой виртуальной машины подключение к интернету с помощью NAT происходит автоматически. Поэтому это самый простой способ подключения гостевой ОС к интернету.

Чтобы включить или отключить интернет с помощью NAT в VirtualBox:

1. Выберите нужную виртуальную машину и кликните по ней правой кнопкой мыши. Нажмите Настроить:

2. В появившемся меню выберите Сеть. Поставьте галочку напротив «Включить сетевой адаптер». Выберите тип подключения NAT и нажмите OK:

Настройка сети на виртуальной машине VirtualBox

Готово, теперь вы знаете, как включить интернет на виртуальной машине VirtualBox.

Как настроить сеть между хостом и виртуальной машиной VirtualBox

Для подключения между основной и гостевой ОС нужно использовать тип подключения «Сетевой мост». В этом случае виртуальная машина подключается напрямую к основной сети как полноценное устройство. Для подключения используется сетевая карта хост-системы.

Чтобы включить сетевой мост:
1. Выберите виртуальную машину, которую хотите подключить к сети. Кликните по ней правой кнопкой мыши и нажмите Настроить:

2. В появившемся меню выберите вкладку «Сеть».
3. В настройках адаптера в строке «Тип подключения» выберите Сетевой мост и нажмите OK:

Готово, гостевая ОС теперь доступна для основной.

Настройка сети между виртуальными машинами в VirtualBox

Иногда нужно объединить в одну сеть несколько виртуальных машин. Для этого используется подключение «Сеть NAT». Она объединяет необходимые виртуальные машины в локальную сеть. Как и в случае с обычным NAT, у каждой есть доступ в интернет, но от доступа извне они изолированы.

Чтобы создать сеть из виртуальных машин VirtualBox:
1. На главной странице VirtualBox нажмите Файл ― Настройки:

2. Перейдите во вкладку Сеть и нажмите на кнопку с зеленым плюсом:

3. Нажмите OK:

4. Выберите виртуальную машину, которую хотите добавить в сеть, и кликните по ней правой кнопкой мыши. Нажмите Настроить:

5. Выберите тип подключения Сеть NAT. В строке «Имя» выберите имя созданной сети. Нажмите OK:

Как создать сеть из виртуальных машин VirtualBox

6. Если вы хотите подключить другие виртуальные машины к сети, повторите действия с 4 шага.

Готово, локальная сеть из виртуальных машин создана.

Источник

• ← что приготовить на 18 летие сына на стол дома
• Блок управления стиральной машины электролюкс 1000rpm →