virtualbox.org

I am running Vbox on an ubuntu host. The guest is debian. When I start up the Guest, I can see the words "failed to start raised network interfaces". I have two interfaces installed; #1 is NAT called " " #2 is Host Only called "vboxNet0". I am using a wireless since my Dell XPS doesnt have a wired NIC interface. I tried using Bridged network for #1 but got a message "route not found". Can anyone tell me what the issue is? I saw some comments about the automated naming of interfaces, but I don't know how to override that.

When I go to the Host and type ssh bitnami@10.0.2.15 I get "no route to host".
Here is the ifconfig on the host:

Code: Select all

richb201@richb201-XPS-13-9370:~$ ifconfig
br-3fdd67cb8cb8: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.20.0.1  netmask 255.255.0.0  broadcast 172.20.255.255
        ether 02:42:59:29:f2:e2  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-7d954c11630f: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        ether 02:42:66:73:b4:27  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-a6199012a820: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.21.0.1  netmask 255.255.0.0  broadcast 172.21.255.255
        ether 02:42:a1:f9:7c:da  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:37:be:bc:e4  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 1984  bytes 186009 (186.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1984  bytes 186009 (186.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vboxnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.56.1  netmask 255.255.255.0  broadcast 192.168.56.255
        inet6 fe80::800:27ff:fe00:0  prefixlen 64  scopeid 0x20<link>
        ether 0a:00:27:00:00:00  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 240  bytes 40984 (40.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:4e:5a:e9  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.10  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::703a:9a83:a8f6:ab58  prefixlen 64  scopeid 0x20<link>
        ether 9c:b6:d0:94:e5:b1  txqueuelen 1000  (Ethernet)
        RX packets 30083  bytes 21012953 (21.0 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 17624  bytes 5073192 (5.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Help!

If you have a "NAT" connection, you get by default a 10.0.2.15 IP, which is what you seem to want to connect over. You can't. Not with "NAT".

Please read the following: User Manual, ch. Introduction to networking modes including the Overview table, which shows quickly what kind of connection is required to achieve what you want.

And remember, you can always have more than one network card in your guest to cover multiple scenarios, just like in your case. Try to connect through the HostOnly IP...

virtualbox.org

trouble setting up adapters

trouble setting up adapters

Re: trouble setting up adapters