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
After some change in the network, such as a reboot in the router, portmaster loses the ability to detect ipv6, causing no website or even windows itself to recognize ipv6, even if I am leaving portmaster, and only works again if I disable and turn on the network adapter again, unlike ipv4 detects and works normally.
What did you expect to happen?:
IPv6 works after network change
How did you reproduce it?:
Go to a site that detects IPv6, restart the router, and watch it lose IPv6, even with a restart in Portmaster
Debug Information:
Version 1.5.1
Portmaster
version 1.5.1
commit tags/v1.5.1-0-g7c3925db32e665a40ba46d888e5e9cacf872beea
built with go1.21.2 (gc) windows/amd64
using options
by user@docker
on 17.10.2023
Licensed under the AGPLv3 license.
The source code is available here: https://github.com/safing/portmaster
Platform: Microsoft Windows 11 Pro 10.0.23585 Build 23585
System: Microsoft Windows 11 Pro windows (Standalone Workstation) 10.0.23585 Build 23585
Kernel: 10.0.23585 Build 23585 x86_64
No Module ErrorUnexpected Logs
231113 18:16:19.096 er/resolve:461 > WARN 442 resolver: query to dns://2606:4700:4700::1112:53#system failed: read udp [fe80::3a4e:4363:999c:1c8d%Ethernet]:22348->[2606:4700:4700::1112]:53: i/o timeout
231113 18:16:19.096 er/resolve:461 > WARN 444 resolver: query to dns://2606:4700:4700::1112:53#system failed: read udp [fe80::3a4e:4363:999c:1c8d%Ethernet]:32737->[2606:4700:4700::1112]:53: i/o timeout
231113 18:16:21.108 er/resolve:461 > WARN 446 resolver: query to dns://2606:4700:4700::1002:53#system failed: read udp [fe80::3a4e:4363:999c:1c8d%Ethernet]:56694->[2606:4700:4700::1002]:53: i/o timeout
231113 18:16:21.108 er/resolve:461 > WARN 448 resolver: query to dns://2606:4700:4700::1002:53#system failed: read udp [fe80::3a4e:4363:999c:1c8d%Ethernet]:50512->[2606:4700:4700::1002]:53: i/o timeout
231113 18:16:21.108 er/resolve:461 > WARN 450 resolver: query to dns://2606:4700:4700::1002:53#system failed: read udp [fe80::3a4e:4363:999c:1c8d%Ethernet]:41433->[2606:4700:4700::1002]:53: i/o timeout
231113 18:16:21.108 er/resolve:461 > WARN 452 resolver: query to dns://2606:4700:4700::1002:53#system failed: read udp [fe80::3a4e:4363:999c:1c8d%Ethernet]:41169->[2606:4700:4700::1002]:53: i/o timeout
231113 18:16:21.109 er/resolve:461 > WARN 454 resolver: query to dns://2606:4700:4700::1002:53#system failed: read udp [fe80::3a4e:4363:999c:1c8d%Ethernet]:18392->[2606:4700:4700::1002]:53: i/o timeout
231113 18:16:21.109 er/resolve:461 > WARN 456 resolver: query to dns://2606:4700:4700::1002:53#system failed: read udp [fe80::3a4e:4363:999c:1c8d%Ethernet]:18538->[2606:4700:4700::1002]:53: i/o timeout
231113 18:16:21.109 er/resolve:461 > WARN 458 resolver: query to dns://2606:4700:4700::1002:53#system failed: read udp [fe80::3a4e:4363:999c:1c8d%Ethernet]:18011->[2606:4700:4700::1002]:53: i/o timeout
231113 18:21:40.294 v/location:303 > WARN 460 netenv: failed to get IPv4 device location from traceroute: did not receive any actionable ICMP reply
231113 18:27:00.282 CURRENT TIME
Status: Trusted
ActiveSecurityLevel: Trusted
SelectedSecurityLevel: Off
ThreatMitigationLevel: Trusted
CaptivePortal:
OnlineStatus: Online
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. {00a7edf4-6ec6-41da-8f33-b80427aeeab8} [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. {6734e5d6-6a59-477d-939e-442b9d781585} [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}
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}
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. {6a9295d6-9e12-4e31-bdcd-291b2a49fcf4} [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. {14f4e0b3-bc93-4181-a491-d526de330b1c} [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. {c26cd7fb-baf9-4d8e-a1a1-da31ec4072ac} [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. {c2fc9130-313b-4b6a-8776-e6a141fa1ed5} [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. {a5ce762f-096d-4b33-954f-651509e2254c} [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. {b6095309-96b2-419f-ac97-e182009f42c1} [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. {996f7a89-69c0-4cc8-80e6-d501fc288b6c} [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. {0099389c-aa21-4237-bbd1-39bcb0a0e2e8} [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 {b6a11002-5766-4a49-8cf3-15d0e4963ce1} [no provider key] FWPM_LAYER_STREAM_V4 {94f25722-8dd9-49fc-8b64-1374205ab5e0}
STREAM_FILTER Filter Filter used to capture Stream traffic {ebaf4e1a-6d6e-4d11-bd1d-97c1e20e9476} [no provider key] FWPM_LAYER_STREAM_V6 {94f25722-8dd9-49fc-8b64-1374205ab5e0}
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. {13a299fd-e4c9-4a24-b836-ece0302fda26} [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. {c59d5d1b-aef2-48b0-8366-4e197b071335} [no provider key] FWPM_LAYER_STREAM_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
TCP_FILTER Filter Filter used to capture TCP traffic {bbf8e11b-89aa-4f4b-82ab-5a5c75a4258d} [no provider key] FWPM_LAYER_ALE_FLOW_ESTABLISHED_V4 {94f25722-8dd9-49fc-8b64-1374205ab5e0}
TCP_FILTER Filter Filter used to capture TCP traffic {ec07753b-3041-4164-a750-1f5d1a1c6b7c} [no provider key] FWPM_LAYER_ALE_FLOW_ESTABLISHED_V6 {94f25722-8dd9-49fc-8b64-1374205ab5e0}
Teredo socket option opt out block filter Filter [no description] {3b0844c3-47ca-482d-9baf-99cbb6f0638c} {d33d300d-7397-40a7-b762-7d1a91351ad5} FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6 {7b6b11f6-cbb5-433c-ae06-6a4f0076e49e}
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.
What happened:
After some change in the network, such as a reboot in the router, portmaster loses the ability to detect ipv6, causing no website or even windows itself to recognize ipv6, even if I am leaving portmaster, and only works again if I disable and turn on the network adapter again, unlike ipv4 detects and works normally.
What did you expect to happen?:
IPv6 works after network change
How did you reproduce it?:
Go to a site that detects IPv6, restart the router, and watch it lose IPv6, even with a restart in Portmaster
Debug Information:
Version 1.5.1
Platform: Microsoft Windows 11 Pro 10.0.23585 Build 23585
No Module Error
Unexpected Logs
Status: Trusted
SPN: disabled (module disabled)
Resolvers: 8/8
Config: 6
Updates: stable (13/31)
Compatibility: WFP State (36)
Goroutine Stack
The text was updated successfully, but these errors were encountered: