virtualbox.org

Host: Ubuntu 20.04 LST Guest: Ubuntu 16.04 BBB VM Hardware: Dell Poweredge R510
I see the NICs in the Host with addresses but the Guest only sees the loopback. What am I doing wrong?

Host
rfrenkel@RSF-PowerEdge-R510:~$ ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 84:2b:2b:73:38:aa brd ff:ff:ff:ff:ff:ff
inet 192.168.10.110/24 brd 192.168.10.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
inet6 fe80::927d:9e20:e6da:920b/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 84:2b:2b:73:38:ab brd ff:ff:ff:ff:ff:ff
inet 10.1.10.10/24 brd 10.1.10.255 scope global dynamic noprefixroute eno2
valid_lft 600374sec preferred_lft 600374sec
inet6 2601:180:8300:e980::1/128 scope global dynamic noprefixroute
valid_lft 190932sec preferred_lft 93255sec
inet6 2601:180:8300:e9808ba5:aba5:9203/64 scope global temporary dynamic
valid_lft 345597sec preferred_lft 81848sec
inet6 2601:180:8300:e980:c484:ba0a6c0/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 345597sec preferred_lft 345597sec
inet6 fe80::956f31a8:3504/64 scope link noprefixroute
valid_lft forever preferred_lft forever

Guest set for Bridged to eno2
bigbluebuttoneubuntu: '\$ ip address show
1: 1o: <L00PBACK, UP, LOUER_UP> ntu 65536 qdisc noop state UNKOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 :: 1/128 scope host
valid_lft forever preferred_lft forever
2: enpos3: <BR0ADCAST,MULIICAST> mtu 1500 qdisc noop state DOWN group defau1t qlen 1000
Iink/ether 08:00:27:7d:c8:2d brd ff:ff:ff:ff:ff:ff
bigbluebuttoneubuntu: ~$ ping 10.1.10.11
connect: Network is unreachable
bigbluebuttoneubuntu: 'ş
Thanks, Ray

Please zip and post the guest's .vbox file, using the forum's Upload Attachment tab.

Here is the vbox file.

Here is what I see:

<Network>
<Adapter slot="0" enabled="true" MACAddress="0800277DC82D" cable="false" type="82543GC">
<DisabledModes>
<InternalNetwork name="intnet"/>
<NATNetwork name="NatNetwork"/>
</DisabledModes>
<BridgedInterface name="eno2"/>
</Adapter>
<Adapter slot="1" MACAddress="080027329EDC" type="82540EM"/>

You have switched the first Bridged network card the New Guest Wizard picked from the default PRO/1000 MT Desktop (82540EM) to the T Server (82543GC). The second network card is not connected but is present as the default MT Desktop (82540EM). The second card is not shown as "enabled" but it is there in the 'recipe'. I wonder if Ubuntu has drivers for the T version?

The slot 0 "enabled" card has "false" on the cable, meaning the 'cable' is disconnected. No traffic can flow.

I changed to the default adapter and checked cable connected box then I ran "sudo ip link set enp0s3 up" Now I have inet6 scope global and inet6 scope link addresses but no inet (ipv4) address.

bigbluebuttoneubuntu: ~$ sudo ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet $127.0.0.1/8 scope host lo
valid_Ift forever preferred_lft forever
inet6 :: 1/128 scope host
valid_Ift forever preferred_lft forever
2: enp0s3: <BRDADCAST, MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1
000
link/ether 08:00:27:7d:c8:2d brd ff:ff:ff:ff:ff:ff
inet6 2601:180:8300:e980:a00fe7d:c82d/64 scope global mngtmpaddr dynamic
valid_lft 345589sec preferred_lft 345589sec
inet6 fe80: :a00fe7d:c82d/64 scope link
valid_Ift forever preferred_Ift forever
bigbluebuttoneubuntu:~$

Which is the IP I use for BBB?

I can sure mess things up when I am trying to fix a network glitch. There are way too many things to set and change. I surmise that you may have done some tweaking too.

First, decide exactly what kind of network you need connected to your guest. Pick just one for now and set only the first network adapter in the guest. See Virtualbox Networks: In Pictures to help decide what you need. Note that if you used and edited NAT network in your guest the NAT network settings may be damaged too. If you want to use NAT network, make a new NAT network for this test.

Please start a fresh brand new guest and a new install of the Ubuntu 16 OS. Let the network card type stay as defaulted by the New Guest Wizard. Set the "Attached To" and "Name" dropdowns to the desired network setting you determined above. Start the guest and you should get an IPv4 address in the guest.