Additional data point:socratis wrote:OK, this is getting more serious then, mainly because it's a second report that transcends major versions. Let's recap:Release dates:
- Upgrading from 5.1.6 to 5.1.8, the connection is reset in some sites.
- Upgrading from 5.0.26 to 5.0.28, same problem. @helloworld111: guest OS, network mode (NAT?) and browser details please.
- Observed so far with Win7 and Firefox/Chrome. Reprodusable in two sites (so far); photo.net and autoschmitt.com. Don't know what distinguishes them from others.
So, in between 12/Sep and 28/Oct, something must have changed? Only in the NAT code? According to the changelogs, the common things that are there (which might be responsible), are:
- 2016-07-18 : 5.0.26
- 2016-09-12 : 5.1.6
- 2016-10-28 : 5.1.8, 5.0.28
So far, we have CodeVisio, socratis and helloworld111 reporting this. I've been watching the bug reports lately and I don't remember seeing anything similar being reported so far. I'd say one more confirmation and it's a bug report.
- NAT: don’t exceed the maximum number of “search” suffixes. Patch from bug #15948.
- NAT: fixed parsing of port-forwarding rules with a name which contains a slash (bug #16002)
- NAT Network: when the host has only loopback nameserver that cannot be mapped to the guests (e.g. dnsmasq running on 127.0.1.1), make DHCP supply NAT Network DNS proxy as nameserver.
I'm running Windows 7 host and CentOS 7 guests (the guests are managed via vagrant and use NAT)
Running npm on the CentOS 7 guests yielded many errors due to truncated/incomplete files being downloaded from our Artifactory server.
Downgrading from VirtualBox 5.1.8 to 5.1.6 resolved the issue.