Opened 16 months ago

Closed 7 months ago

#684 closed System Defect (fixed)

PC-BSD 9.1 beta networking inoperative in VirtualBox

Reported by: MoebusNet Owned by:
Priority: major Milestone: 9.1
Component: System Configuration Version: 9.1-BETA1
Keywords: network, virtualbox Cc: trac-bugs@…

Description

Ubuntu 12.04 host
VirtualBox? 4.2.6 r82870
PC-BSD 9.1 beta guest from PCBSD9.1-X64-VBOX.vdi verified with md5sum

Unable to configure network so that it works. IP and NetMask? are not configured in PC-BSD. Set up VirtualBox? bridged network as directed in how-to's. Not familiar enough with BSD to set it up on command-line. GUI tools in PC-BSD show network as active, but is not functional. Network settings appear to be correct in PC-BSD GUI tools.

Posting from a Linux guest OS on the same VirtualBox? system.

First time trying out PC-BSD, please forgive errors.

Attachments (3)

24.png (82.0 KB) - added by MoebusNet 16 months ago.
58.png (56.2 KB) - added by MoebusNet 16 months ago.
24.2.png (25.1 KB) - added by MoebusNet 15 months ago.
Networking shows not configured, but working

Download all attachments as: .zip

Change History (14)

comment:1 Changed 16 months ago by MoebusNet

Ran PC-BSD 9.0-x86 Live-CD in same VirtualBox? environment, same issue. Default is for wired networking to be disabled; unable to configure wired networking with GUI tools. When attempting to enable Wired Networking via GUI, clicking 'Enable' box enables change from 'Static' to 'DHCP', but changes are immediately lost upon clicking "Save'. Networking is currently not possible from VirtualBox?.

Log files do not present any messages to do with networking.

comment:2 Changed 16 months ago by MoebusNet

Installed PCBSD9.1-x64-DVD.iso to same VirtualBox? environment as previous attempts (PCBSD9.1-x64-VBOX.vdi and PCBSD9.0-x86-DVD-live.iso). Networking was properly configured at default settings. There may be an error in the PCBSD9.1-x64-VBOX.vdi and PCBSD9.0-x86-DVD-live.iso images, since the md5sums for the respective images checked out. Glad to have my first PC-BSD OS with working networking up and running in VBox!

Changed 16 months ago by MoebusNet

Changed 16 months ago by MoebusNet

comment:3 Changed 16 months ago by MoebusNet

Downloaded PC-BSD9.1-x64-VBOX.vdi.bz2, confirmed md5sum, created new .vdi VM using ftp://ftp.pcbsd.org/pub/handbook/9.1/handbook_en_ver9.1.html#__RefHeading__20713_674241385 to include 'Configuring the Network Adapter' in paragraph 2.7.1.1. Set up VM as instructed, networking inoperative. Changed Network Adapter configuration to match working configuration in VM created from PCBSD9.1-x64-DVD.iso using only default VM settings. In the .vdi VM, networking is still not working using .iso VM's Network Adapter settings. Still no networking in VM using PC-BSD9.1-x64-VBOX.vdi.

comment:4 follow-up: Changed 16 months ago by dlavigne

Please post the output of ifconfig from within the vm (i.e. on the PC-BSD system).

comment:5 in reply to: ↑ 4 Changed 16 months ago by MoebusNet

Replying to dlavigne:

Please post the output of ifconfig from within the vm (i.e. on the PC-BSD system).

# ifconfig
em0 flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM
ether 8:00:27:31:64:61
nd6 options=21<PERFORMNUD,AUTOLINK_LOCAL>
media: Ethernet autoselect(1000baseT<full-duplex>)
status:active

lo0 flags=<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
n6 options=21<PERFORMNUD,AUTOLINK_LOCAL>

comment:6 follow-up: Changed 16 months ago by dlavigne

OK. What happens if you "dhclient em0" as the superuser within the PC-BSD vm?

comment:7 in reply to: ↑ 6 Changed 16 months ago by MoebusNet

Replying to dlavigne:

OK. What happens if you "dhclient em0" as the superuser within the PC-BSD vm?

# dhclient em0
DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent databases - sleeping.

I'll be off-line until 0800 CST tomorrow; sorry it took so long to reply.

comment:8 Changed 15 months ago by MoebusNet

If it will help to compare the VM with working networking created from PCBSD9.1-x64-DVD.iso:

# ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 08:00:27:df:26:30
inet6 fe80::a00:27ff:fedf:2630%em0 prefixlen 64 scopeid 0x1
inet 10.0.2.15 netmask 0xffffff00 broadcast 10.0.2.255
nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

# dhclient em0
dhclient already running, pid: 1124.
exiting.

comment:9 Changed 15 months ago by MoebusNet

OK, this is weird. After looking at everything I could at

http://wiki.pcbsd.org/index.php/Network_Configuration#Troubleshooting_Network_Settings

but not changing anything, networking in the .vdi VM is working. I was running the VM from the DVD.iso install, shut it down, booted up the .vdi VM and networking started up. Posting from the .vdi VM now.

Here is the .vdi VM output of:

# ifconfig em0
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 08:00:27:31:64:61
inet6 fe80::a00:27ff:fe31:6461%em0 prefixlen 64 scopeid 0x1
inet 10.0.2.15 netmask 0xffffff00 broadcast 10.0.2.255
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active

# dhclient em0
dhclient already running, pid: 999.
exiting.

Networking may or may not work again on next boot-up. I wasn't able to find out what driver was being used.

Changed 15 months ago by MoebusNet

Networking shows not configured, but working

comment:10 Changed 15 months ago by MoebusNet

To make things more interesting, the GUI for network configuration claims that the wired interface is not configured Networking shows not configured, but working.

Networking is currently working; I can browse web pages in the .vdi VM.

comment:11 Changed 7 months ago by joshms

  • Resolution set to fixed
  • Status changed from new to closed

Please give 9.2 a shot and it should perform much better for you. I leave my virtualbox on NAT mode and it works fantastic without having to configure anything in networking. I can't duplicate the issue on 9.2, but if the problem persists for you please let us know.

Note: See TracTickets for help on using tickets.