Skip to content
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

Webrtc leak can't work #2678

Closed
1nj0k opened this issue Sep 9, 2020 · 1 comment
Closed

Webrtc leak can't work #2678

1nj0k opened this issue Sep 9, 2020 · 1 comment
Labels
question Further information is requested

Comments

@1nj0k
Copy link

1nj0k commented Sep 9, 2020

Seems prevent WebRTC from leaking local ip address can't work properly.

I have used this website to test, https://webbrowsertools.com/test-webrtc-leak/

Hope it can be fixed.

@1nj0k 1nj0k changed the title Webrtc leak can' work Webrtc leak can't work Sep 9, 2020
@ghostwords
Copy link
Member

Hello!

I believe this is working as intended. Privacy Badger sets WebRTC IP handling policy to "default_public_interface_only" when the protection is enabled. This corresponds to WebRTC behavior mode 3, which says your private IP is not provided. This is what we mean by "local IP address".

Setting WebRTC behavior to mode 4 breaks all WebRTC applications when you don't have a proxy configured. See #2632 for this very problem. If you do have a proxy, and you would like to force WebRTC to use it, I suggest installing a dedicated extension that does switch WebRTC to mode 4.

Let me know if you have any questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants