Project

General

Profile

Bug #9320

Bridged Network under VirtualBox 5.2.8 (Hipster)

Added by Douglas Summers over 2 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2018-03-20
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

Not sure what happened. I've installed OI Hipster a couple of times now (as a VirtualBox guest)
and never had a problem until today. I'm running a bridged wireless USB NIC under Linux Mint 18.3.
My Windows 7 and Fedora 27 workstations have had no issues, and OI didn't either when I updated
the initial install (pkg update -v -r). What's weird is that the network settings seem OK: I'm getting
IPv4/IPv6 DHCP leases, the nameservers are being properly updated, and the NIC otherwise
seems to be active.

(from the guest)
root@DSS-openindiana:~# ifconfig e1000g0
e1000g0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 3
inet 192.168.0.6 netmask ffffff00 broadcast 192.168.0.255
ether 8:0:27:6f:52:73

root@DSS-openindiana:~# cat /etc/resolv.conf
nameserver 68.105.28.11
nameserver 68.105.29.11
nameserver 68.105.28.12

(from the host)
$ VBoxManage showvminfo OpenIndiana --machinereadable --details | egrep '^(nic|bridge|mac)' | grep -v none
bridgeadapter1="wlxbcec23100000"
macaddress1="0800276F5273"
nic1="bridged"
nictype1="82540EM"
nicspeed1="0"

I can't ping anything on the local network. The docs talk about making a VNIC, but I can't get that
to work either. It seems that something I updated is the culprit; I have not installed any new
software.

#1

Updated by Douglas Summers over 2 years ago

FYI - the bridged NIC works fine booting the OI install CD image.

#2

Updated by Douglas Summers over 2 years ago

After reinstalling (and updating) the bridged network seems to be working OK. The only thing I did
differently was how I installed the updates:

(from bug #9183)
It should be noted that a fresh install followed by changing root's expired password, doing 'pkg refresh --full' and then '*pkg image-update -v' work as expected and the system works as expected after a reboot. So the above issue is somehow related to running 'pkg update' instead of 'pkg image-update'

I'm really curious why this would make a difference.

#3

Updated by Douglas Summers over 2 years ago

I'm trying another clean install now; this time I'm connected via 1G ethernet. I've had nothing but problems with my wireless USB adapter, first under Mint 18.3 and now under Fedora 27. My other VMs, Windows 7 and OpenSUSE 42.3, have never had any network issues, whether bridged to wireless or ethernet. I'll let you know what happens.

Also available in: Atom PDF