Hyper-V Virtual Machine Connection window refreshes every minute, consistently. #811
Comments
ghost
assigned 
|
Hey @Taarek, thanks for your report. Before start going into this, let me remind you that virtual machines are not yet officially support by Portmaster. See #166 for more details. Unfortunately, I am not familiar with Hyper-V. It seems that some network state makes something fire the If we can find out what that is what makes it think the network changed, we can work on a solution. |
|
Do you possibly know where I can see that? The event logs doesn't really reveal what it is that's triggering these events. FWIW; I experience this issue on my work PC and my PC at home, so it's not happening to a single device. |
|
@dhaavi At a further inspection, it seems like it's WSL causing it.. Every time this log entry happens, the WSL Network Adapter gets a new IPv6 address. PS C:\Users\Tarek> Get-Date
Thursday, 15 September 2022 20:48:20
PS C:\Users\Tarek> [System.Net.DNS]::GetHostByName('')
HostName Aliases AddressList
-------- ------- -----------
Tarek {} {fe80::605f:263b:2341:1748%33, fe80::4030:7b42:e6fb:cfcf%19, 10.20.20.38, 192.168.224.1…}
PS C:\Users\Tarek> Get-Date
Thursday, 15 September 2022 20:48:55
PS C:\Users\Tarek> [System.Net.DNS]::GetHostByName('')
HostName Aliases AddressList
-------- ------- -----------
Tarek {} {fe80::609f:ffc5:f9ee:a376%33, fe80::4030:7b42:e6fb:cfcf%19, 10.20.20.38, 192.168.224.1…}
PS C:\Users\Tarek> Get-Date
Thursday, 15 September 2022 20:51:00
PS C:\Users\Tarek> [System.Net.DNS]::GetHostByName('')
HostName Aliases AddressList
-------- ------- -----------
Tarek {} {fe80::fde6:c8df:2b61:3778%33, fe80::4030:7b42:e6fb:cfcf%19, 10.20.20.38, 192.168.224.1…}Screenshot of the network adapter in Task manager: These things do not happen if Portmaster is turned off, so is WSL perhaps doing something because it thinks it's being blocked? |
|
Auto-closing this issue after waiting for input for a month. If anyone finds the time to provide the requested information, please re-open the issue and we will continue handling it. |
|
Was this closed correctly? @dhaavi |
|
I was closing old issues where nothing was happening, to improve focus on issues which are actually active. as Daniel was also saying earlier, VMs are not supported at the moment, we will take a look into this when we start tackling VMs in the future. maybe this year. |
Pre-Submit Checklist:
What happened:
Apologies in advance if this is the wrong issue type, wasn't sure if it would fit more as a bug or incompatibility issue.
I know Hyper-V is not supported, but I am not exactly experiencing a connectivity issue, even though it technically is.
If I have Portmaster running, the VM Connection window (To view and control the VM) in Hyper-V reloads/refreshes every minute (at the exact second).
Sometimes restarting Portmaster fixes it, but is obviously not a good solution.
Every minute when it happens, it seems to fire a
Network State Change Firedevent according to Windows event logs.Connecting to the VM over SSH, SFTP, HTTP or RDP does not cause this behavior, and I've allowed all traffic that was previously blocked that would show up in Portmaster.
When I check the Portmaster logs, whenever it happens it seems like a bunch of
Allowed requests are happening, originating from svchost (see logs below)What did you expect to happen?:
No reloading/refreshing of the Hyper-V connection window if all traffic is allowed.
How did you reproduce it?:
Connect...on a VM for the VM Connection window to show up.Logs from Portmaster (found in %PROGRAMDATA%\Safing\Portmaster\logs):
Portmaster
Logs from WIndows Event Viewer:
(These events happens every minute, at the exact same second of that minute. And it's not a coincidence, they happen the same time the refreshes/reloads happen)
NetworkProfile/Operational
WMI-Activity/Operational
Debug Information:
Version 0.9.3
Platform: Microsoft Windows 11 Enterprise 10.0.22000 Build 22000
Status: Trusted
Config: 2
Resolvers: 6/6
SPN: disabled (module disabled)
Compatibility: WFP State (17)
No Module Error
Unexpected Logs
Goroutine Stack
The text was updated successfully, but these errors were encountered: