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
What happened:
After running for a time, the Portmaster core process suddenly hogs one to two cores and network access speed slows down to a crawl until it stops working completely. The UI complains a short time before the full outage that DNS resolution is slow. Only a restart of the PortmasterCore Windows service restores network access.
In addition to the "unexpected logs" lines below, I have a lot of these kind of log messages in the core log file (which is 1.8 MB in size, having been created today at 14:05 and closed on 15:15):
240829 15:15:34.972 work/ports:049 > WARN 829 network: took 382 attempts to find a suitable unused port for pre-auth
240829 15:15:35.020 work/ports:049 > WARN 831 network: took 155 attempts to find a suitable unused port for pre-auth
240829 15:15:35.136 work/ports:049 > WARN 833 network: took 145 attempts to find a suitable unused port for pre-auth
What did you expect to happen?:
Portmaster to not have such a high CPU usage and let network traffice flow unhindered.
How did you reproduce it?:
Start my PC, use it for a while, notice that remote desktop connections get sluggish.
Debug Information:
Version 1.6.10
Portmaster 1.6.10
built with go1.22.3 (gc -cgo) for windows/amd64
at 2024-05-15T12:03:21Z
commit 867d0bca2d71d7247039cf8e6b129580c28be7d6 (clean)
at 2024-05-15T09:08:08Z
from [email protected]:Safing/portmaster.git
Licensed under the GPLv3 license.
Platform: Microsoft Windows 10 Pro 10.0.19045 Build 19045
System: Microsoft Windows 10 Pro windows (Standalone Workstation) 10.0.19045 Build 19045
Kernel: 10.0.19045 Build 19045 x86_64
No Module ErrorUnexpected Logs
240829 15:21:59.570 er/resolve:460 > WARN 290 resolver: query to dns://10.1.1.28:53#config failed: read udp 10.27.101.48:13701->10.1.1.28:53: i/o timeout
240829 15:21:59.570 er/resolve:460 > WARN 292 resolver: query to dns://10.1.1.28:53#config failed: read udp 10.27.101.48:45132->10.1.1.28:53: i/o timeout
240829 15:21:59.570 er/resolve:460 > WARN 294 resolver: query to dns://10.1.1.28:53#config failed: read udp 10.27.101.48:20371->10.1.1.28:53: i/o timeout
240829 15:22:01.554 er/resolve:460 > WARN 296 resolver: query to dns://10.1.1.28:53#config failed: read udp 10.27.101.48:16166->10.1.1.28:53: i/o timeout
240829 15:22:01.554 er/resolve:460 > WARN 298 resolver: query to dns://10.1.1.28:53#config failed: read udp 10.27.101.48:21752->10.1.1.28:53: i/o timeout
240829 15:22:11.220 er/resolve:460 > WARN 300 resolver: query to dns://fda9:6e09:85ca::1:53#config failed: dial udp :62398->[fda9:6e09:85ca::1]:53: bind: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.
240829 15:22:50.340 er/resolve:460 > WARN 302 resolver: query to dns://10.5.2.28:53#config failed: dial udp :50124->10.5.2.28:53: bind: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.
240829 15:22:56.443 er/resolve:460 > WARN 304 resolver: query to dns://10.5.2.28:53#config failed: read udp 10.27.101.48:34762->10.5.2.28:53: i/o timeout
240829 15:22:56.522 er/resolve:460 > WARN 306 resolver: query to dns://10.5.2.28:53#config failed: read udp 10.27.101.48:19866->10.5.2.28:53: i/o timeout
240829 15:22:56.523 er/resolve:460 > WARN 308 resolver: query to dns://10.1.1.28:53#config failed: dial udp :52929->10.1.1.28:53: bind: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.
240829 15:23:22.605 CURRENT TIME
Check Point Software Technologies Ltd. Provider Application Control blade {91842344-b99c-4dcb-afce-fb6f7462f55b}
DatagramV4Callout Callout This callout is used to handle datagram data for IPv4. {a6be3096-66bf-4959-8629-1c3a4c40c31e} [no provider key] FWPM_LAYER_DATAGRAM_DATA_V4
DatagramV4Filter Filter The filter is used for handling datagram data for IPv4. {05617af3-4f34-41b1-8741-03731a93ebb3} [no provider key] FWPM_LAYER_DATAGRAM_DATA_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
DatagramV6Callout Callout This callout is used to handle datagram data for IPv6. {d55cb395-29a1-4716-8cb1-65c888995f54} [no provider key] FWPM_LAYER_DATAGRAM_DATA_V6
DatagramV6Filter Filter The filter is used for handling datagram data for IPv6. {2af8c2b0-c838-4ca1-93e1-d717439423b6} [no provider key] FWPM_LAYER_DATAGRAM_DATA_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
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}
L2TP Client Inbound and Outbound Filter Filter [no description] {1e8d6537-7c1e-4f74-8ef6-4720f30ffe9d} [no provider key] FWPM_LAYER_IPSEC_V4 FWPM_SUBLAYER_UNIVERSAL
L2TP Client Inbound and Outbound Filter Filter [no description] {568119b5-6040-4598-aa46-bd362c02877a} [no provider key] FWPM_LAYER_IKEEXT_V4 FWPM_SUBLAYER_UNIVERSAL
L2TP Client Inbound and Outbound Filter Filter [no description] {a556e197-38ed-4c12-8032-a5688e787f16} [no provider key] FWPM_LAYER_OUTBOUND_TRANSPORT_V4 FWPM_SUBLAYER_UNIVERSAL
L2TP Client Inbound and Outbound Filter Filter [no description] {ecf16626-78de-45f7-b03a-95e5655e6863} [no provider key] FWPM_LAYER_INBOUND_TRANSPORT_V4 FWPM_SUBLAYER_UNIVERSAL
L2TP Client Specific Filter Filter [no description] {08fc194c-e43c-4697-8204-62f04891f25a} [no provider key] FWPM_LAYER_INBOUND_TRANSPORT_V4 FWPM_SUBLAYER_UNIVERSAL
L2TP Client Specific Filter Filter [no description] {527e68e5-3318-4ec4-8f0e-a5e24e2e3a8f} [no provider key] FWPM_LAYER_OUTBOUND_TRANSPORT_V4 FWPM_SUBLAYER_UNIVERSAL
L2TP Client Specific Filter Filter [no description] {f915b7a6-7c8a-410a-add1-23f6640ca48a} [no provider key] FWPM_LAYER_IPSEC_V4 FWPM_SUBLAYER_UNIVERSAL
PortmasterALEInboundV4Callout Callout This callout is used by the Portmaster to monitor outbound IPv4 traffic before the connection is established. {e36216c5-7b33-40ee-b054-fb1bc7decc19} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V4
PortmasterALEInboundV4Filter Filter This filter is used by the Portmaster to monitor inbound IPv4 traffic before the connection is established. {e34562f7-ee72-441e-bb56-3c85732ff380} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterALEInboundV6Callout Callout This callout is used by the Portmaster to monitor outbound IPv6 traffic before the connection is established. {77ea9927-66e7-4cf8-9ea2-941edf2fae63} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6
PortmasterALEInboundV6Filter Filter This filter is used by the Portmaster to monitor inbound IPv6 traffic before the connection is established. {d0d50321-8817-4dbb-9552-074dbd983b38} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterALEOutboundV4Callout Callout This callout is used by the Portmaster to montiror outbound IPv4 traffic before the connection is established. {029819fe-97d9-4e5f-a0fb-78ef5cef8ac4} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V4
PortmasterALEOutboundV4Filter Filter This filter is used by the Portmaster to monitor outbound IPv4 traffic before the connection is established. {43534ab5-b4b1-4fd6-afbb-b7f4f1c0e0ad} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterALEOutboundV6Callout Callout This callout is used by the Portmaster to monitor outbound IPv6 traffic before the connection is established. {d6b0213a-337a-4cc6-84c0-cc60731b9e2a} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V6
PortmasterALEOutboundV6Filter Filter This filter is used by the Portmaster to monitor outbound IPv6 traffic before the connection is established. {33afa3ab-828f-4401-b105-7aa747854e3c} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
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. {d0c2b792-a831-4dc7-abcc-a0374c17e0e4} [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. {35880b1a-713e-4cac-93d4-ceaaa53c1c4c} [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. {35b993ce-9a9c-4f77-9140-a0b394548187} [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. {daf43d16-9eeb-49cd-b0dc-7a0c23382642} [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}
SbieCallout Callout A callout used by sandboxie to implement internet restrictions {0bf56435-71e4-4de7-bd0b-1af0b4cbb8f6} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V4
SbieCallout Callout A callout used by sandboxie to implement internet restrictions {0bf56435-71e4-4de7-bd0b-1af0b4cbb8f8} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V4
SbieCallout Callout A callout used by sandboxie to implement internet restrictions {0bf56435-71e4-4de7-bd0b-1af0b4cbb9f7} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V6
SbieCallout Callout A callout used by sandboxie to implement internet restrictions {0bf56435-71e4-4de7-bd0b-1af0b4cbb9f9} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6
SbieFilter Filter A filter that uses by sandboxie to implement internet restrictions {04325ddd-b0fe-45ca-a14f-70c88750fb42} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V4 {e1d364e9-cd84-4a48-aba4-608ce83e31ee}
SbieFilter Filter A filter that uses by sandboxie to implement internet restrictions {3ae891df-49b6-4290-8168-151e21e8f580} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6 {e1d364e9-cd84-4a48-aba4-608ce83e31ee}
SbieFilter Filter A filter that uses by sandboxie to implement internet restrictions {460cc70c-5cc6-46b1-8f80-dce361d93e1d} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V4 {e1d364e9-cd84-4a48-aba4-608ce83e31ee}
SbieFilter Filter A filter that uses by sandboxie to implement internet restrictions {716572b2-a9d0-4469-b774-8b87ca21819f} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V6 {e1d364e9-cd84-4a48-aba4-608ce83e31ee}
SbieSublayer SubLayer A sublayer used by sandboxie to implement internet restrictions {e1d364e9-cd84-4a48-aba4-608ce83e31ee}
StreamV4Callout Callout This callout is used to handle stream data for IPv4. {525dac52-65de-4a6f-b546-2b1f3bc226db} [no provider key] FWPM_LAYER_STREAM_V4
StreamV4Filter Filter The filter is used for handling stream data for IPv4. {f13d36cd-dfda-4e6c-880f-2d3ffbfe7179} [no provider key] FWPM_LAYER_STREAM_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
StreamV6Callout Callout This callout is used to handle stream data for IPv6. {4321ddf9-57b2-4391-8fc5-c5b46c655587} [no provider key] FWPM_LAYER_STREAM_V6
StreamV6Filter Filter The filter is used for handling stream data for IPv6. {808f6ad2-74b8-4b91-8e82-1baf5f45d694} [no provider key] FWPM_LAYER_STREAM_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
Teredo socket option opt out block filter Filter [no description] {c33e62a8-a59c-4f4c-97fe-e5dc42cb7bf5} {f0e2c118-95fb-4f48-901b-037d1c36d49a} FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6 {7b6b11f6-cbb5-433c-ae06-6a4f0076e49e}
VPN Reconnect Sublayer SubLayer [no description] {9367171b-3264-4f09-a0e8-81b38c162f17}
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.
Pre-Submit Checklist:
What happened:
After running for a time, the Portmaster core process suddenly hogs one to two cores and network access speed slows down to a crawl until it stops working completely. The UI complains a short time before the full outage that DNS resolution is slow. Only a restart of the
PortmasterCore
Windows service restores network access.In addition to the "unexpected logs" lines below, I have a lot of these kind of log messages in the core log file (which is 1.8 MB in size, having been created today at 14:05 and closed on 15:15):
What did you expect to happen?:
Portmaster to not have such a high CPU usage and let network traffice flow unhindered.
How did you reproduce it?:
Start my PC, use it for a while, notice that remote desktop connections get sluggish.
Debug Information:
Version 1.6.10
Platform: Microsoft Windows 10 Pro 10.0.19045 Build 19045
No Module Error
Unexpected Logs
Status: Online
SPN: disabled (module disabled)
Resolvers: 7/7
Config: 4
Updates: stable (13/33)
Compatibility: WFP State (51)
Goroutine Stack
The text was updated successfully, but these errors were encountered: