You are not logged in.
I have a win10 x64 guest in a virtualbox on an Arch server with kernel 4.3.3-3-ARCH SMP PREEMPT.
I've installed the Virtualbox add-ons for inside the guest, and it has network connectivity.
I'm using the emulated Intel NIC with NAT for the virtual NIC in the guest, but this problem reproes (more often) when using the Paravirtualized (virtio) drivers.
I have a srcds server instance running in the VM. I've forwarded the ports from the router to the host, and from the host to the guest. Clients can connect and play on the server.
After a period of time (with virtio drivers it's 3 hours, with emulated NIC its a few days), clients can no longer connect to the srcds server instance. Restarting srcds does not fix this issue. Other network services (like an http server) are still accessible. Restarting the guest VM solves the issue until the next time it happens.
I installed wireshark on the windows guest and I see srcds ping packets being received and responded to by the process, I even see the packets from my own connection attempt and they're being responded to immediately.
Has anyone else experienced this? My next step is to just put the VM on the network in bridged mode and see if that solves the problem, but I'd rather not since it adds another driver to my kernel.
Does this sound like an issue to report upstream?
Last edited by darkfoon (2016-01-31 22:57:35)
Offline