I've been reviewing more close votes recently. There's been certain trend of a few questions being impossible to review correctly to my mind, and I wanted to ask if there's a community view on how to handle them.
I call them "impossible to review correctly" because the decision to close them very much depends on knowing the correct answer and the reason for closure is "doesn't belong on this site" meaning I very likely don't!
They all involve Linux and MS Windows interacting in some way. Depending on the answer, the question might be about something in MS Windows, or it might be about something in Linux.
This is about packet loss on a Linux guest Virtual Machine on a Windows 11 Host. Networking is "bridge mode" meaning the host hypervisor somehow emits packets from the VM with it's own mac address and IP and identifies incoming packets, routing them into the VM.
Tom Yan's Comment is very pertinent:
Note that WiFi client is not designed to support to be bridged. It could be that VirtualBox only implemented workaround for IPv4 to work
I have no knowledge if this is true or not, frankly I'm skeptical, but as a reviewer I couldn't be sure. What's more, this would be a detail about how Virtualbox Bridge networking behaves on MS Windows. That's totally outside my sphere of knowledge and way off topic for this site. So while there might hypothetically be someone here who could answer it, it's not reasonable for us to expect that.
FYI I voted to close because I think it needs a lot more detail to be sure of an answer if it is a Linux problem.
This is about linux behaviour on the face of it. But it's Linux interacting with a remote Active Directory server.
You're using VAS which is an AD bridge solution and it can (and will) cache results. What you're seeing is how VAS works. Talk to the software vendor.
What's not totally clear is the extent to which this is about the behaviour of software running on Linux vs the behaviour of a Windows server.
On balance I voted to leave open and leave a vague enough answer based on what I understand might help the OP.
So what to do?
I find myself stuck between:
- Either we leave questions open because there is "reasonable doubt" that they might still be about software running on Linux. This might be seen by some as "cluttering up" U&L with non-Linux questions. But at least it doesn't ask people to review questions based on details well outside their sphere of expertise. It keeps the review focussed on the question and not potential answers.
- We slam closed questions because we suspect the might not be about linux, but we can't be sure. Personally I don't like this idea, I don't see it as actually positive. But it might sooth some people's OCD.
- We skip any question we're not sure about for such grounds, in which case such questions may remain open because there's simply nobody who knows the answer and so not 5 people to close the question.
Honestly I'm not quite sure how to proceed with them.