Re: [Freedos-devel] VirtualBox and RC1 Networking

[Jerome E. Shidel Jr.]

Hello Louis, 

> Any idea how VirtualBox was configured for the user reporting the
> issue?  NAT, Internal Network, Bridged, Host-only?  This could answer
> the firewall question.

This was discovered to be an issue after the last VirtualBox update by Me 
during final testing just before the final RC1 release.

Basically, It is just a test virtual machine using VirtualBox standard 
defaults. This was fine in previous versions of VB. But, not now.

VirtualBox defaults to NAT. I’ve tried others like Bridged and different NICs. 
But those mostly don’t work at all. I see there is a “Port Forwarding” in VB 
advanced networking settings. I don’t know if it was there prior to the latest 
update to VB.
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] VirtualBox and RC1 Networking

[Louis Santillan]

Any idea how VirtualBox was configured for the user reporting the
issue?  NAT, Internal Network, Bridged, Host-only?  This could answer
the firewall question.

On Wed, Nov 2, 2016 at 4:35 AM, Jerome E. Shidel Jr.  wrote:
> Hello All,
>
> The latest release of VirtualBox seems to have broken networking support on 
> that “hardware.” Under the previous version of VirtualBox, installing the 
> FDNET package (included with RC1) would provide an automatic fully working 
> networking support. Programs like FDNPKG, PING, WGET and such worked great. 
> However, with this last VirtualBox update, this is not the case. PING appears 
> to function properly. But, everything else seems to fail. FDNPKG throws 
> “failed” messages, WGET says “Connection reset by server”, etc. I do see that 
> VirtualBox seems to have configuration settings for an integrated firewall. 
> But, I don’t know if they were there in the previous release when networking 
> “just worked.” I have heard that this has also occurred with some Windows 
> installs in VirtualBox. This leads me to think that it is probably not a 
> problem with the packet drive or networking inside the VM.
>
> So, does anyone know if it is a VirtualBox configuration issue or a 
> VirtualBox bug? If it is a configuration issue, do you know how to remedy the 
> problem?
>
> Thanks, Jerome
> --
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel

--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] VirtualBox and RC1 Networking

[Jerome E. Shidel Jr.]

Hello All,

The latest release of VirtualBox seems to have broken networking support on 
that “hardware.” Under the previous version of VirtualBox, installing the FDNET 
package (included with RC1) would provide an automatic fully working networking 
support. Programs like FDNPKG, PING, WGET and such worked great. However, with 
this last VirtualBox update, this is not the case. PING appears to function 
properly. But, everything else seems to fail. FDNPKG throws “failed” messages, 
WGET says “Connection reset by server”, etc. I do see that VirtualBox seems to 
have configuration settings for an integrated firewall. But, I don’t know if 
they were there in the previous release when networking “just worked.” I have 
heard that this has also occurred with some Windows installs in VirtualBox. 
This leads me to think that it is probably not a problem with the packet drive 
or networking inside the VM.

So, does anyone know if it is a VirtualBox configuration issue or a VirtualBox 
bug? If it is a configuration issue, do you know how to remedy the problem?

Thanks, Jerome
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel