Version 4.1.14 breaks network support on Openstep 4.2

[poingg]

After upgrading do 4.1.14, networking stopped working. I downgraded Virtualbox back to 4.1.12 and it's working again.

This is valid both for NAT and bridged adapter modes

[poingg]

Logfile

[Aleksey Ilyushin]

Could you please try if it works with PRO/1000 adapters instead of PCNet? If you could provide the description of how you test the network along with the internal capture file made during the test it would be very much appreciated. See https://www.virtualbox.org/wiki/Network_tips for the info on how to enable internal capture. Do not forget to disable it after the test.

[dopey]

I'm seeing a similar behavior. I just wanted to mention that the PRO/1000 adapter is not an option. OPENSTEP 4.2 does not support the PRO/1000 adapter and only provides drivers for the AMD PCNet adapter.

I'll try to do the internal capture bit and post the details as I have more time to test it.

[dopey]

VirtualBox-4.2-4.2.6_82870_fedora18-1.x86_64

That's the version I'm using. I enabled the capture, started the VM and then opened a terminal and started pinging 10.0.2.2 (the NAT gateway address)

Attached is the pcap file. It seems able to do arp requests and get an arp response but that's it. No actual ping is captured.

[Daniel Ashton]

This is still an issue under 4.3.6 r91406

[Daniel Ashton]

This issue remains under 4.3.8 r92456. It would be great to see this break loose and start working.

[Daniel Ashton]

This issue remains under 4.3.10 r93012.

[segabor]

Not working either in the latest version 4.3.12 r93733

[segabor]

For the record, this ticket made this happen #3783. Anyway, issue still exists.

[JL]

Still broken in 4.3.26. :-(

[polarhome]

I can confirm that this problem appears on openSUSE 12.2 AMD64 too. Is there any hope that this issue will be fixed?

[Frank Mehnert]

polarhome, OpenStep is one item but what about OpenSUSE 12.2, what's your problem with networking there? Please describe what not works and provide a corresponding VBox.log file.

[Valery Ushakov]

This is a regression in PCnet emulation introduced by a fix to #3783.

[polarhome]

Replying to frank:

polarhome, OpenStep is one item but what about OpenSUSE 12.2, what's your problem with networking there? Please describe what not works and provide a corresponding VBox.log file.

I am sorry for misunderstanding. I was testing recent virtualbox (4.3.28) with OPENSTEP 4.2 guest on OpenSUSE 12.2 AMD64 host - and the networking does not work. Or better it works as described. The ARP recovery works but no ICMP, UDP or TCP protocol works.

[Valery Ushakov]

You can try a 4.3 test build, revision 100516 or higher. It brings back TCP/IP. There's still a problem with 802.3 framing which we suspect is a bug in the OpenStep driver, but we need to investigate more.

[JL]

Replying to vushakov:

You can try a 4.3 test build, revision 100516 or higher. It brings back TCP/IP. There's still a problem with 802.3 framing which we suspect is a bug in the OpenStep driver, but we need to investigate more.

I tried the test build but without success. When booting Openstep 4.2 it reports no network connection and prompts to start without networking by pressing CTRL-C as before.

[Valery Ushakov]

OpenStep uses BOOTP, not DHCP and our DHCP server doesn't speak BOOTP, unfortunately. Use manual configuration. You can also use Simple Network Starter for that.

[Andrew Daugherity]

Just tested Openstep 4.2 on VirtualBox 4.3.30 and 5.0.2 (both of which have higher build numbers than 100516) and networking now works again! (Using the PCnet-FAST III adapter Am79C973 in the VM config, and the AMD PCnet-32 PCI Ethernet Adapter v4.00 driver in Openstep.) Many thanks for finally fixing this!

For NAT mode I configured the VM with a static IP of 10.0.2.15, router 10.0.2.2, and the host machine's DNS server. I also tested bridged mode with a static IP on the host's subnet and the host's default router and that worked fine too.

[segabor]

Just tested my old OPENSTEP vbox with the latest VirtualBox (5.1.14) and I can confirm networking is working again.