networks – eth1 could not be opened Maybe the gateway is a problem (with virtualbox)

Use Parrot Security v4.5 (I know this is not Ubuntu, but maybe the solution to this problem is the same as Ubuntu) and this is my / etc / network / interfaces:

# This file describes the network interfaces available in your system.
# and how to activate them. For more information, see interfaces (5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto what
iface what inet loopback

# First interface
auto eth0
iface eth0 inet dhcp

# Second interface
auto eth1
iface wth1 inet static
network mask

But when I do it:

restart network service

I have this error:

the work for networking.service failed because the control process came out with the error code

And with:

state of the service network

I have:

ifup: eth1 could not be opened

If I delete the last three lines (if only delete the line of the gateway, this does not work) in the file / etc / network / interfaces and if:

restart network service

and then add only the network mask and the transmission line with (NO gateway line):

restart network service

I have no problem

What is the problem? Thank you.

note well This is my configuration in the virtual box:
enter the description of the image here

How to get rid of the border around windows in VirtualBox transparent mode

Running Windows 10, VirtualBox 6.04 and Ubuntu 18.10

In continuous mode, there is an extended border around the windows. It is functional but a little distracted and seems to occur in all applications.

enter the description of the image here

networks – Interfaces in VirtualBox

I have a computer in VirtualBox with three interfaces. Two of them are connected to the internal network, and one is connected to a bridged adapter.
After starting that computer, I can see the three interfaces.

(enp0s3, enp0s8, enp0s9)

My question is how to recognize what the bridge is and what the internal ones are, so I can configure the correct IP addresses.
Thank you

networks – VirtualBox VM can not resolve DNS after restart

Configured VirtualBox VM running CentoOS 7, running on the Windows 10 host.
VM configured with host only adapter in NIC 1 and NAT in NIC 2.
NIC 1 works correctly and connects to the host, but can not connect to the Internet (assuming in NIC 2) and host names can not be resolved.
After restarting the network service (systemctl restart network), the Internet becomes accessible.

The IP query shows the enp0s8 adapter with the NAT IP address, but there is no network script in / etc / sysconfig / network-scripts / (the ifcfg-enp0s8 file does not exist), while the network script for the adapter only for the host (enp0s3) exists.

How can I configure it to work without the need to restart the "network" service?


[centos@eiab90 ~]$ nmcli dev show enp0s8
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 08: 00: 27: 29: 2C: EA
GENERAL. STATE: 100 (connected)
GENERAL CONNECTION: cable connection 1
GENERAL.CON-PATH: / org / freedesktop / NetworkManager / ActiveCo
IP4.ROUTE[1]: dst =, nh =, mt ​​= 101
IP4.ROUTE[2]: dst =, nh =, mt = 10
IP6.ADDRESS[1]: fe80 :: e457: 8cf: 5f9d: ea1c / 64
IP6.ROUTE[1]: dst = fe80 :: / 64, nh = ::, mt = 101
IP6.ROUTE[2]: dst = ff00 :: / 8, nh = ::, mt = 256, table

Macos: High Sierra can not be installed in VirtualBox or Parallels, it does not resolve when the date changes

I am trying to install High Sierra in VirtualBox or Parallels. My host is MacOS Sierra.

My installer is 10.13.6 Build 17G85 with its verified checksums.

I created the ISO with this method:
Install macOS High Sierra as a VirtualBox guest (in macOS High Sierra)?

Both VirtualBox and Parallel start the ISO to "Install MacOS", but when I press "Continue", I have the "This copy of the Install MacOS Sierra application" is damaged and can not be used to install MacOS.

Changing the date with the terminal using "date 090100002018" (September 1, 201) does not work.

Any ideas?

virtualbox – Ubuntu X server screen

I'm new to Ubuntu.
I have installed Ubuntu server 18.04 (cli version, without GUI) and virtualbox software on it.
Now I am trying to run virtualbox but I get the following errors. I'm sure I need to install some additional packages (for example, X Windows) but I do not know exactly what I need.
Please help.

I connected to the server through the SSH console:

root @ oovm: / etc / apt # vboxmanage –version

root @ oovm: / etc / apt # virtualbox
Qt WARNING: QStandardPaths: XDG_RUNTIME_DIR not set, by default a & # 39; / tmp / runtime-root & # 39;
Qt WARNING: QXcbConnection: Could not connect to the screen
Qt CRITICAL: Could not connect to any X screen.

Please, give me an instruction on how to make everything work.

Thank you.

virtualbox – How to use TShark to capture the network traffic (Internet) of virtual machines?

I have two virtual machines running in VirtualBox, both are ubuntu 18.04 and my host machine is also ubuntu 18.04. I also have a running Python script in each virtual machine that sends http and https requests to a list of websites. I would like to monitor network traffic on both virtual machines using a tool such as tshark; Is that even possible to achieve? And if so, how to do it.

Note that for each VM I have two adapters, adapter 1 uses NAT and adapter 2 is only for the Host (I use this to enable ssh access between my hsot machine and my VM).

Thanks for your help.

virtualbox: the boxing virtual Linux guest died after MacOS automatically updated while the guest was running

I know I should have turned off the guest, but I was away from the computer when a forced update occurred on the MacOS host.

At first, the administrator said that the virtual machine was still running when it was not.

Then I clicked right to save it, then I tried to go back to it and it did not work

Then I discarded the saved state and tried to restart and got the same error

The virtual machine & # 39; xxxxxxxxx & # 39; ended unexpectedly during the start due to signal 6.

Result code:
NS_ERROR_FAILURE (0x80004005)
IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

Any suggestion would be very grateful,

Is it safer to use Qubes with Whonix from Virtualbox than directly on the host computer?

I know it is not recommended to run Qubes-Whonix from Virtualbox due to performance issues, but other than that, is it safer? That is to say. Is it harder or easier to hack / infect Qubes-Whonix running from Virtualbox than running as usual?

virtualbox – CPUs added with VBoxManage do not appear in HTOP

Following this question, I changed the CPU numbers of my guest.

I used the following commands

    # VM is off
VBoxManage modifyvm "Ubuntu 12" --cpus 2
VBoxHeadless --startvm "Ubuntu 12" 

Now, I hope the guest turns on, SSH and check htop, which shows me that there is still only one CPU. What is wrong? I guess the CPUs have not really been added, or they have not been initialized correctly since they are not shown in htop

enter the description of the image here