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
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.
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.
The text was updated successfully, but these errors were encountered: