IPv6 Connections Blocked on system startup #1448
Comments
|
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
|
|
Hey @nrarend, thanks for the report. I've looked into this a couple times already, but haven't yet found the issue. Can you send me all the details you have about the TCPIP error (Event ID 4199) you are seeing? Also, can you try if it works if you disable SPN? |
|
Something else I just noticed here and in a similar issue - #1443 I see there is some other network firewall active. |
|
I had the same problem, and the process was similar to the description above. There is no other protection software except simplewall and Windows defender. log: 240229 12:46:25.316 pat/module:108 > ERRO 003 compat: self-check #3: dns integration check failed: failed to receive test response: lookup a9b1a5bf0c3e12073a817d67b5c1bdccdb.self-check.portmaster.home.arpa.: no such host 240229 12:48:38.431 i/database:190 > WARN 005 api: websocket connection error with 127.0.0.1:59136: read tcp 127.0.0.1:817->127.0.0.1:59136: wsarecv: An existing connection was forcibly closed by the remote host. 240229 13:07:04.891 v/location:303 > WARN 007 netenv: failed to get IPv4 device location from traceroute: failed to send icmp packet: write ip4 0.0.0.0->1.1.1.1: wsasendto: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. |
The Windows Event Viewer has two events about the network: |
How did you resolve it? Can you tell me what the given parameters of the errors were? |
|
My computer is a DIY PC. I tried adding the following rule to Protmaster's rules. Testing the computer sleeping, shutting down and turning it back on didn't cause the problem, but due to my personal time constraints I've only done limited testing. rule： |
|
Thanks for testing, I will continue to look into this soon. |
|
This rule doesn't solve the problem. However, I found a problem in debugging that the link-local ipv6 address keeps changing while Portmaster is on, and the address doesn't change until I stop Portmaster. |
|
Same problem for months, IPv6 is lost if any changes happen to the network and only returns if the adapter is restarted Log Name: System |
Version 1.6.5Platform: Microsoft Windows 11 Pro 10.0.26080 Build 26080No Module ErrorUnexpected LogsStatus: OnlineSPN: disabled (module disabled)Resolvers: 6/6Config: 10Updates: beta (13/33)Compatibility: WFP State (36)Goroutine Stack |
|
After restarting the adapter and IPv6 works again Version 1.6.5Platform: Microsoft Windows 11 Pro 10.0.26080 Build 26080No Module ErrorUnexpected LogsStatus: OnlineSPN: disabled (module disabled)Resolvers: 10/10Config: 10Updates: beta (13/33)Compatibility: WFP State (36)Goroutine Stackevents log Log Name: System |
|
This issue has been automatically marked as inactive because it has not had activity in the past two months. If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics. |
github-actions
bot
added
the
stale
|
This issue has been automatically closed because it has not had recent activity. Thank you for your contributions. If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
IPv6 is blocked with Portmaster upon starting into Windows with Portmaster running. IPv6 is enabled in system network adapter and router. If I shut down the Portmaster service, restart the network adapter, and restart Portmaster service, IPv6 connections work fine. In Event Viewer, I can see the TCPIP error (Event ID 4199) about conflicting addresses with system having address of 00-00-00-00-00-00.
What did you expect to happen?
I expect IPc6 connections to work fine without any extra steps.
How did you reproduce it?
This happens almost every time I start into Windows. On the rare occasion, IPv6 connections seem to be allowed for a short period of time before being broken. Very rarely, the problem doesn't occur at all until rebooting the system again. It can also be reproduced if I restart the adapter while Portmaster service is running, even if IPv6 connections had been working before. The only truly reproduceable event involves getting IPv6 working by suspending the Portmaster service, restarting the network adapter, and restarting Portmaster. There seems to be rare exceptions to everything else.
Additional information
Debug-Info: https://support.safing.io/privatebin/?1ae7b9c7c2a989cd#3FNQkQ9MNSpXAqS4mkyk4Gbr5ZLuXH4Jpq9yvASyCzu2
The text was updated successfully, but these errors were encountered: