You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 29, 2024. It is now read-only.
What happened:
I have this notification since last update, but I am not sure what it actually is trying to say?
Does it mean that there are rules that are identical to those two processes or what? I also don't know if it's a typo or not, but Please change on of them "Host Process for Windows Services" or "System DNS Client" doesn't make much sense to me..
Also these two "Change" buttons are not quite obvious either, clicking on them just takes you to either "Host Process for Windows Services" or "System DNS Client"
What did you expect to happen?:
Not applicable, I suppose, but I guess actually telling me what's wrong.
How did you reproduce it?:
Not sure.
Debug Information:
Version 1.0.0
Portmaster
version 1.0.0
commit tags/v1.0.0-0-g6868333425ff0c4ab25bba19e22f560da6eaced0
built with go1.19 (gc) windows/amd64
using options main.go
by user@docker
on 18.10.2022
Licensed under the AGPLv3 license.
The source code is available here: https://github.com/safing/portmaster
Platform: Microsoft Windows 11 Enterprise 10.0.22621 Build 22621
System: Microsoft Windows 11 Enterprise windows (Standalone Workstation) 10.0.22621 Build 22621
Kernel: 10.0.22621 Build 22621 x86_64
Status: Trusted
ActiveSecurityLevel: Trusted
SelectedSecurityLevel: Off
ThreatMitigationLevel: Trusted
CaptivePortal:
OnlineStatus: Online
Edge traversal Teredo Authorization Sublayer SubLayer Edge traversal Teredo Authorization Sublayer {7b6b11f6-cbb5-433c-ae06-6a4f0076e49e}
IPxlat Forward IPv4 filter Callout Filters forwarded IPv4 packets into synthetic IPv6 packets {b255c296-7e0c-4115-95f3-b7f24a8a1162} [no provider key] FWPM_LAYER_IPFORWARD_V4
IPxlat Forward IPv4 sub layer SubLayer Sub layer for filtering forwarded IPv4 packets into synthetic IPv6 packets {4351e497-5d8b-46bc-86d9-abccdb868d6d}
IPxlat Inbound IPv6 filter Callout Filters incoming IPv6 packets into synthetic IPv4 packets {93bb703d-0502-42e2-8e30-a14576e5085d} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V6
IPxlat Inbound IPv6 sub layer SubLayer Sub layer for filtering incoming IPv6 packets into synthetic IPv4 packets {dfb035ca-c2a7-4684-97b6-4dbc57c63590}
IPxlat Outbound IPv4 filter Callout Filters outgoing IPv4 packets into synthetic IPv6 packets {66d52657-1979-4e58-b3f7-4756434c4880} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V4
IPxlat Outbound IPv4 sub layer SubLayer Sub layer for filtering outgoing IPv4 packets into synthetic IPv6 packets {d3e70856-fc90-4c0a-b9b2-a6f73e20b5cc}
Insecure.Com LLC. Provider Npcap {af617412-ce10-4058-8996-abc79fd805ff}
Network Npcap Filter (Loopback) Filter [no description] {21022f40-9578-4c39-98a5-c97b8d834e01} {af617412-ce10-4058-8996-abc79fd805ff} FWPM_LAYER_INBOUND_IPPACKET_V6 {2f32c254-a054-469b-b99b-3e8810275a72}
Network Npcap Filter (Loopback) Filter [no description] {ed7e5eb2-6b09-4783-961c-5495eaad3601} {af617412-ce10-4058-8996-abc79fd805ff} FWPM_LAYER_INBOUND_IPPACKET_V4 {2f32c254-a054-469b-b99b-3e8810275a72}
Npcap Loopback Sub-Layer SubLayer Sub-Layer for use by Npcap Loopback callouts {2f32c254-a054-469b-b99b-3e8810275a72}
Npcap Network Callout Callout Npcap loopback network traffic {21022f40-9578-4c39-98a5-c97b8d834e28} {af617412-ce10-4058-8996-abc79fd805ff} FWPM_LAYER_INBOUND_IPPACKET_V6
Npcap Network Callout Callout Npcap loopback network traffic {ed7e5eb2-6b09-4783-961c-5495eaad361f} {af617412-ce10-4058-8996-abc79fd805ff} FWPM_LAYER_INBOUND_IPPACKET_V4
NsAleFlowEstablishedV4 Callout Nsr ALE Flow Established V4 Callout {71da3b2d-c3e4-4aba-a5af-2518733296eb} [no provider key] FWPM_LAYER_ALE_FLOW_ESTABLISHED_V4
NsAleFlowEstablishedV6 Callout Nsr ALE Flow Established V6 Callout {891dd37c-9874-4a5e-a039-ba6f448a0e93} [no provider key] FWPM_LAYER_ALE_FLOW_ESTABLISHED_V6
NsStreamV4 Callout Nsr Stream V4 Callout {be26feaa-d260-4ee7-b4dc-ef842f537842} [no provider key] FWPM_LAYER_STREAM_V4
NsStreamV6 Callout Nsr Stream V6 Callout {3df07fda-20cc-4ad6-a06f-1df3134b4971} [no provider key] FWPM_LAYER_STREAM_V6
NsrSubLayer SubLayer nsr sublayer {94f25722-8dd9-49fc-8b64-1374205ab5e0}
PortmasterInboundV4Callout Callout This callout is used by the Portmaster to intercept inbound IPv4 traffic. {05c55149-4732-4857-8d10-f178f3a06f8c} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V4
PortmasterInboundV4Filter Filter This filter is used by the Portmaster to intercept inbound IPv4 traffic. {9cd324d6-d175-4500-a500-ddc53954beb0} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterInboundV6Callout Callout This callout is used by the Portmaster to intercept inbound IPv6 traffic. {ceff1df7-2baa-44c5-a6e5-73a95849bcff} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V6
PortmasterInboundV6Filter Filter This filter is used by the Portmaster to intercept inbound IPv6 traffic. {81f07bab-0e38-4017-82d1-7b66f5ec32ed} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterOutboundV4Callout Callout This callout is used by the Portmaster to intercept outbound IPv4 traffic. {41162b9e-8473-4b88-a5eb-04cf1d276b06} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V4
PortmasterOutboundV4Filter Filter This filter is used by the Portmaster to intercept outbound IPv4 traffic. {39450de6-2ced-4900-90dc-27b66fdfde03} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterOutboundV6Callout Callout This callout is used by the Portmaster to intercept outbound IPv6 traffic. {32bad112-6af4-4109-809b-c07570ba01b4} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V6
PortmasterOutboundV6Filter Filter This filter is used by the Portmaster to intercept outbound IPv6 traffic. {8f36abc5-fb53-4bc7-b13c-f411e991e24b} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterSublayer SubLayer The Portmaster sublayer holds all it's filters. {a87fb472-fc68-4805-8559-c6ae774773e0}
STREAM_FILTER Filter Filter used to capture Stream traffic {1ccce713-f782-4052-955a-0b4d6320587b} [no provider key] FWPM_LAYER_STREAM_V6 {94f25722-8dd9-49fc-8b64-1374205ab5e0}
STREAM_FILTER Filter Filter used to capture Stream traffic {43cf5ec3-6172-4dd7-af1c-7f4a4ee5a015} [no provider key] FWPM_LAYER_STREAM_V4 {94f25722-8dd9-49fc-8b64-1374205ab5e0}
TCP_FILTER Filter Filter used to capture TCP traffic {224254da-e6d3-45fe-8b2c-f3fdd8a22902} [no provider key] FWPM_LAYER_ALE_FLOW_ESTABLISHED_V6 {94f25722-8dd9-49fc-8b64-1374205ab5e0}
TCP_FILTER Filter Filter used to capture TCP traffic {b9d6ba7c-4845-4950-879c-dc8f164db41f} [no provider key] FWPM_LAYER_ALE_FLOW_ESTABLISHED_V4 {94f25722-8dd9-49fc-8b64-1374205ab5e0}
Teredo socket option opt out block filter Filter [no description] {d0208626-7dae-4c12-a731-274fcc87ebee} {fa61ddd4-83f2-4240-a597-5158816ff6d1} FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6 {7b6b11f6-cbb5-433c-ae06-6a4f0076e49e}
No Module ErrorUnexpected Logs
221020 10:05:17.977 terception:165 > ERRO 030 interception: failed to remove persistent verdicts: The operation completed successfully. [LE 0x0] [RC 0x1]
221020 10:05:19.322 terception:165 > ERRO 032 interception: failed to remove persistent verdicts: The operation completed successfully. [LE 0x0] [RC 0x1]
221020 10:05:21.136 terception:165 > ERRO 034 interception: failed to remove persistent verdicts: The operation completed successfully. [LE 0x0] [RC 0x1]
221020 10:05:23.575 terception:165 > ERRO 036 interception: failed to remove persistent verdicts: The operation completed successfully. [LE 0x0] [RC 0x1]
221020 10:05:24.474 terception:165 > ERRO 038 interception: failed to remove persistent verdicts: The operation completed successfully. [LE 0x0] [RC 0x1]
221020 10:05:25.484 terception:165 > ERRO 040 interception: failed to remove persistent verdicts: The operation completed successfully. [LE 0x0] [RC 0x1]
221021 08:30:55.210 r/updating:029 > WARN 042 updates: failed to update index all/intel/intel.json: failed to fetch index all/intel/intel.json: failed to make request to "https://updates.safing.io/all/intel/intel.json": Get "https://updates.safing.io/all/intel/intel.json": dial tcp 116.203.130.137:443: bind: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
221021 08:31:00.313 r/updating:029 > WARN 044 updates: failed to update index stable.json: failed to fetch index stable.v2.json: failed to make request to "https://updates.safing.io/stable.v2.json": Get "https://updates.safing.io/stable.v2.json": dial tcp 116.203.130.137:443: bind: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
221021 08:31:00.313 dates/main:254 > ERRO 046 updates: check failed: failed to update indexes: failed to update all indexes, last error was: failed to fetch index stable.v2.json: failed to make request to "https://updates.safing.io/stable.v2.json": Get "https://updates.safing.io/stable.v2.json": dial tcp 116.203.130.137:443: bind: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
221021 08:31:00.313 ules/tasks:392 > ERRO 048 updates: task updater failed: failed to update indexes: failed to update all indexes, last error was: failed to fetch index stable.v2.json: failed to make request to "https://updates.safing.io/stable.v2.json": Get "https://updates.safing.io/stable.v2.json": dial tcp 116.203.130.137:443: bind: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
221021 08:57:37.162 CURRENT TIME
How does not answering the question result in the ticket being closed? I have the same issue but for different apps. App Settings Match Conflict
Multiple app settings match the app at "C:\Windows\System32\svchost.exe" with the same priority, please change on of them: "Windows Service: License Manager" or "Windows Service: Wdi Service Host"
@netExtra I appreciate your activity here, and I remember some issues we were writing where you were nice and helping.
You seem not to be a developer though, and yes reporting issues helps, but keeping issues open that have been not looked at for over a year does not help anyone. what you did is actually more helpful. A new report with new information in the current version of Portmaster!
This issues is from October 2022 and I closed it almost a year later, and now it is again over halve a year later, so this issues probably has nothing to do with yours.
Portmaster had major changes and windows as well.
So pleas don't see a closed issue as a discouragement, but understand that just keeping it open does not make us more likely to look at it or work on it. Quite the opposite if we know that open issues are all active and that there is actually some helpful information in them makes us more likely to tackle them
Pre-Submit Checklist:
What happened:
I have this notification since last update, but I am not sure what it actually is trying to say?
Does it mean that there are rules that are identical to those two processes or what? I also don't know if it's a typo or not, but
Please change on of them "Host Process for Windows Services" or "System DNS Client"
doesn't make much sense to me..Also these two "Change" buttons are not quite obvious either, clicking on them just takes you to either "Host Process for Windows Services" or "System DNS Client"
What did you expect to happen?:
Not applicable, I suppose, but I guess actually telling me what's wrong.
How did you reproduce it?:
Not sure.
Debug Information:
Version 1.0.0
Platform: Microsoft Windows 11 Enterprise 10.0.22621 Build 22621
Status: Trusted
Config: 3
Resolvers: 6/6
SPN: disabled (module disabled)
Compatibility: WFP State (32)
No Module Error
Unexpected Logs
Goroutine Stack
The text was updated successfully, but these errors were encountered: