Hi,
I am running both alpha release and haiku-nightly-hrev49897-x86_gcc2_hybrid-cd in (separate VM) VirtualBox Version 5.0.10 r104061. I do not have any networking issues with alpha release using the NAT network configuration. However, haiku-nightly with NAT can not complete the DHCP negotiation. VirtualBox appears to receive the DHCP request:
00:06:54.787509 NAT: DHCP offered IP address 10.0.2.15
00:06:59.531808 NAT: DHCP offered IP address 10.0.2.15
00:07:08.509411 NAT: DHCP offered IP address 10.0.2.15
00:07:25.079022 NAT: DHCP offered IP address 10.0.2.15
00:07:57.568699 NAT: DHCP offered IP address 10.0.2.15
00:09:01.966204 NAT: DHCP offered IP address 10.0.2.15
but haiku-nightly (syslog) gives
DAEMON ‘DHCP’: /dev/net/pcnet/0: SEND DHCP_DISCOVER to 255.255.255.0:67
DAEMON ‘DHCP’: /dev/net/pcnet/0: DHCP Status = operation timed out
DAEMON ‘DHCP’: /dev/net/pcnet/0: SEND DHCP_DISCOVER to 255.255.255.0:67
DAEMON ‘DHCP’: /dev/net/pcnet/0: Timeout shift: 8 secs (try 1)
DAEMON ‘DHCP’: /dev/net/pcnet/0: DHCP Status = operation timed out
DAEMON ‘DHCP’: /dev/net/pcnet/0: SEND DHCP_DISCOVER to 255.255.255.0:67
Eventually it times out and self-assigns an ip address. Manually entering 10.0.2.15 does not enable networking, so I suspect there is a problem in the pcnet driver.
I went back and grabbed haiku-nightly-hrev47259-x86gcc2hybrid-cd from three years ago and tried it. It appears to have the same issue, although I did not check the log file.
Is there a way to enable more debugging in the pcnet driver? Note that without network capability I will not be able to download patches or tools to further diagnose this problem. I am interested in building haiku-nightly and do some developing on it.
Switching to Intel PRO/1000 MT Desktop did fix the problem. Alpha R4 works with PCNET/FastNet III, so I did not think to change the network card in VirtualBox.
The latest nightly build seems to have a bug in the networking negotiation. It re-negotiates about every three minutes. On my system it forces the router to recycle. This makes the web a bit flakey as I run a very slow connection. It works but not so pretty good!
There seems to be a similar problem with the RTL2860 driver (or its environment) - since I can connect to a WiFi link with WPA2 but it only gets a link local address and goes no further. I’m pretty sure it used to work shortly after WPA(2) was implemented.
Actually we followed FreeBSD network drivers offering, and in this case the “pcn” doesn’t work on VirtualBox, whereas the “le” driver has worked before, but has become obsolete for real hardware (the upgrade happened since alpha4). FreeBSD doesn’t support this virtual device on Virtualbox, neither does Haiku now.
I was thinking, since there is a bug report that dates back a good ways, the configuring VirtualBox documentation (https://www.haiku-os.org/guides/virtualizing/virtualbox) should instruct the user to use the Intel PRO/1000 option (which works for alpha4 as well), instead of leaving the network configuration to Troubleshooting. In my case, while I read the VirtualBox documentation initially before installing alpha4 and had no problems, when I installed haiku-nightly I did not make the connection (no pun intended). VirtualBox appears to default to the Intel Pro/1000 card for *BSD VMs, but Haiku is an “other/unknown” OS relative to the options, for which VB defaults to PCNet Fast III as the network card.
Thanks for the help and the links to the bug reports.