WebRTC Control
Have control over WebRTC (disable | enable) and protect your IP address.
Configures how WebRTC's network traffic is routed by changing Chrome's privacy settings.
Review user movement across collected snapshots.
View collected rating snapshots from the latest 7-day window to assess rating stability.
Compare 1-day, 7-day, and 30-day net growth and growth rate.
Review publication date, version, supported languages, and crawl timestamps.
Review the store description, core capabilities, and common use cases.
Configures the WebRTC traffic routing options in Chrome's privacy settings.
★ What it does:
This configures WebRTC to not use certain IP addresses or protocols:
- private IP addresses not visible to the public internet (e.g. addresses like 192.168.1.2)
- any public IP addresses associated with network interfaces that are not used for web traffic (e.g. an ISP-provided address, when browsing through a VPN)
- Require WebRTC traffic to go through proxy servers as configured in Chrome. Since most of the proxy servers don't handle UDP, this effectively turns off UDP until UDP proxy support is available in Chrome and such proxies are widely deployed.
Inspect the latest comments and rating distribution.
Store average score: 3.9. The bars below are calculated from synced review text only, so they may be empty for extensions that have public ratings but no synced comments yet.
Review related products from the Chrome Web Store detail page.
Have control over WebRTC (disable | enable) and protect your IP address.
Disable WebRTC and prevent IP leak.
Prevent WebRTC leaks using the official API.
Hides your private and public IP addresses by configuring how WebRTC's network traffic is routed.
Shows your IPv4 & IPv6 address and also geolocational informations about your IP addresses.
Protects you against tracking through "free", centralised, content delivery.
Using this site ipleak dot net, this add on seems to block the actual local IP, my LAN IP, but NOT my WAN, or public IP. So there's no real point here. If it is privacy that you're after, then you don't want your ISP provided IP detected, that is the WAN IP. Still, it gets three starts because it does get rid of the LAN IP, so it's a decent start.
Works as intended, my WebRTC leak when using a VPN is no more!! It doesn't disable and hide the RTCPeerConnection as the Firefox fix for this does, but it changes the IP to mask the current PIA VPN IP.
Does not work with ZenMate
It works.
Non-Functional - DNS & IP still leaking. Yet another reason to use a browser that values your privacy - Firefox... Simple config change and Poof! No more WebRTC leaks of any kind. Not to mention that you can also make the same settings changes on the Android version and Google still doesn't allow any plugins on Chrome for Android - not that this one is functional (at least not on my current Chrome version [Version 47.0.2526.8 dev-m (64-bit)]
Does not work as intended. After installing the plugin (chrome latest version) my DNS still leaks.
@justin When using the limiter can't create connections between 2 tabs in the same computer, or 2 computers in the same LAN.
Its a add-on that adds something that should be a default feature in Chrome. It should have settings that allow you to completely disable WebRTC, instead of dis-allowing a few network paths. However at the end of the day it only allows WebRTC to query your public IP, which is is accessible by connecting to a website anyway. However, only your public IP that you are connecting with is shown, meaning if you turn on a VPN, it will only show the VPN IP. Thanks for finally getting around to it google, but full disable would be a nice addition.
It Works very well. Tested all the options in: ipleak.net PS: To effectively prevent the IP leak (private and public IP) when using VPNs (proxies) like Hola, Hotspot Shield, SurfEasy and others, should enable the "Use my proxy server (if present)" option, since the default option is "Use my default public and private IP addresses." For five stars, still lack the option to enable / disable the extension directly from its icon.
Works as intended, but works too well. I finally discovered that this was the reason my Hangouts phone calls wasn't having audio. Needs whitelist feature.