Running Parrot In Virtual Box networking errors

Support Network
1

Briefly describe your issue below:

pinging 8.8.8.8 or google.com shows “Temporary failure in domain name resolution” or “Network unreachable”. I have tried various Virtualbox adapter settings.

What version of Parrot are you running? (include version (e.g. 4.6), edition(e.g. Home//KDE/OVA, etc.), and architecture (currently we only support amd64)

Parrot Security
from uname -a:
Linux parrot 5.4.0-4parrot1-amd64 #1 SMP Parrot 5.4.19-4parrot1 (2020-02-27) x86_64 GNU/Linux

What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)
Downloaded parriot security

Downloaded the Parrot security ISO, then loaded the iso as a bootable device in a virtualbox VM. Proceeded with graphical install on a VDI.

Configured to multiboot with other systems? (yes / no)

No

List your networking hardware (make, model, firmware version):

On the host: Intel Dual-Band Wireless AC-8260

If there are any similar issues or solutions, link to them below:

If there are any error messages or relevant logs, post them below:

2

Frim what i know virtual box gives network issue with many linux installation even when you’re running windows in it so i always opt for vm workstation player.
Still try to use ethernet cable to see if it works or not wireless adapters don’t show up in vboxes that easily also make sure you installed vbox guest additions

3

more info here:

Issue #1:
can’t ping google dot com, can’t ping 8.8.8.8
All of these ping commands hang and wont show responses.

Virtualbox Adapter setting is NAT.
Connection on the host Windows 10 machine works fine.
output of ip a:

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:7e:b7:a1 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic noprefixroute eth0
       valid_lft 85644sec preferred_lft 85644sec
    inet6 fe80::403a:c701:7bb1:5d64/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

output of cat /etc/resolvconf/resolv.conf.d/head:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

output of cat /etc/resolv.conf (I made changes to this in an attempt to solve my problem and the changes stuck)

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 8.8.8.8
nameserver 208.67.222.222

Issue #2:
Can’t ping 8.8.8.8 or google dot com The error message for both is "Network is unreachable"

Virtualbox network adapter setting is set to Bridged Adapter (Microsoft Network Adapter Multiplexor Driver).
Connection on Windows 10 host works fine.
the resolvconf info is the same as Issue #1.

output of ip a:

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:7e:b7:a1 brd ff:ff:ff:ff:ff:ff
    inet 192.168.56.101/24 brd 192.168.56.255 scope global dynamic noprefixroute eth0
       valid_lft 352sec preferred_lft 352sec
    inet6 fe80::403a:c701:7bb1:5d64/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

Issue #3:
Can’t ping google dot com: shows error message "Temporary failure in name resolution"
Can’t ping 8.8.8.8: "Network is unreachable"

Virtualbox adapter settings are set to Host-Only Adapter (Virtualbox Host-Only Ethernet Adapter)
Windows 10 host connectivity is fine.
The resolvconf settings are the same as in Issue #1 .
In Windows 10 network settings, the VirtualBox Host-Only Network (Adapter) and the Wifi (Adapter) are bridged to form “Network Bridge”.

Output of ip a:

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:7e:b7:a1 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic noprefixroute eth0
       valid_lft 86322sec preferred_lft 86322sec
    inet 192.168.56.101/24 brd 192.168.56.255 scope global dynamic noprefixroute eth0
       valid_lft 598sec preferred_lft 598sec
    inet6 fe80::403a:c701:7bb1:5d64/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

I have already done a sudo apt update && sudo apt full-upgrade before posting.
Virtualbox guest additions is installed.
Virtualbox is on the latest version.

4

Are you fucking serious? Host only doesn’t connect to internet. Only bridge or NAT can.

1 Like
5

In the past I was able to open a web page and reach websites, but when I could do that the ping tests still wouldn’t work. Pinging localhost does work.
I prefer not to use another virtualization application.

6

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.