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
When I use this as a client on a dual-stack machine, my IPv4 traffic gets wrapped into WG tunnel and my IPv6 traffic doesn't. Since your container doesn't support IPv6 as of today, on the related interfaces it should not allow any IPv6 traffic to not spoil the origin of packets.
Expected Behavior
I expect that when I bring up a tunnel it hides my origin by blocking IPv6 on related interfaces.
Steps To Reproduce
Run a client on dual-stack machine then run IP tests in browserleaks.com. It is gonna say that by IPv4 means you are in XYZ country and by IPv6 means you are in ABC country.
Environment
Any IPv6 && WireGuard capable host with a browser.
CPU architecture
x86-64
Docker creation
docker compose up -d
Container logs
No logs.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Is there an existing issue for this?
Current Behavior
When I use this as a client on a dual-stack machine, my IPv4 traffic gets wrapped into WG tunnel and my IPv6 traffic doesn't. Since your container doesn't support IPv6 as of today, on the related interfaces it should not allow any IPv6 traffic to not spoil the origin of packets.
Expected Behavior
I expect that when I bring up a tunnel it hides my origin by blocking IPv6 on related interfaces.
Steps To Reproduce
Run a client on dual-stack machine then run IP tests in browserleaks.com. It is gonna say that by IPv4 means you are in XYZ country and by IPv6 means you are in ABC country.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: