-
-
Notifications
You must be signed in to change notification settings - Fork 316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ICMPv6 Neighbor Advertisements are blocked #1777
Comments
Experiencing the same issue with Portmaster 1.6.28 (dev build): IPv6 connectivity fails when using SLAAC without DHCPv6 because ICMPv6 RAs cannot pass through the firewall. This renders IPv6 prefix discovery through both RS and all-nodes multicast inoperable, ultimately leading to no IPv6 address being assigned. Looking at log trace, it seems that ICMPv6 packet is missing its payload layer (or set to zero):
This is the origin of the error: portmaster/service/firewall/interception/windowskext2/packet.go Lines 57 to 64 in 7261594
It looks like payload layer is extracted from ConnectionV4 when dealing with IPv4: portmaster/service/firewall/interception/windowskext2/handler.go Lines 50 to 60 in 7261594
However, for IPv6 this does not seem to be the case: portmaster/service/firewall/interception/windowskext2/handler.go Lines 102 to 111 in 7261594
Now, the payload layer might well be set elsewhere in the code, like the kernel extension, but my limited knowledge is proving to be insufficient for further investigation. Windows 11 Pro 10.0.22631 Build 22631 |
IPv6 pings fail. A packet capture on the host running Portmaster shows no responses to the ICMPv6 NS requests from the router.
How did you reproduce it?:
ping -6 -S <Windows IPv6 GUA> <Gateway IPv6 GUA>
Debug Information:
Version 1.6.28
Platform: Microsoft Windows 11 Pro 10.0.22631 Build 22631
Unexpected Logs
Status: Online
SPN: disabled (module disabled)
Resolvers: 3/3
Config: 13
Updates: beta (13/35)
Compatibility: WFP State (43)
Worker Status: 3/55 (0?)
Goroutine Stack
The text was updated successfully, but these errors were encountered: