How to Stop WebRTC Local IP Address Leaks on Google Chrome and Mozilla Firefox While Using Private I
If you are using a VPN or a Proxy and you would like to test this WebRTC Local IP leak, click here.
Note: This doesn't affect OSX or Android users, seemingly just Windows users.
Google Chrome users should download this add-on that will block WebRTC. Opera users can download this plugin that will allow them to download and use Google Chrome add-ons. Mozilla Firefox users can actually turn off the default WebRTC functionality directly in Firefox settings by typing ‘about:config’ into the search bar and browsing to the ‘media.peerconnection.enabled’ option and setting it to FALSE. Users of Canary, Nightly, and Bowser are also vulnerable to this IP leak. However, the local IP address leak should not affect Internet Explorer or Safari users unless they have manually added WebRTC themselves.Private Internet Access already comes with many advanced features for the most privacy-centric users. PIA even suggests that you test for DNS, email, and IPv6 IP address leaks when setting up their service.
Hello all, just got word that the WebRTC Block plugin for Google Chrome doesn't cut it at the moment. Another user, uSuper, has updated the original github tool developed by Daniel Roesler to defeat what uSuper calls "naive WebRTC blocking." uSuper first reported that the use of an iframe defeated WebRTC Block in his review of WebRTC Block in the Google Chrome plugin store three days ago.