From July 29th, 2015 to May 27th, 2022, 39% user give 5-star rating, 7% user give 4-star rating, 12% user give 3-star rating, 8% user give 2-star rating, 33% user give 1-star rating. for WebRTC Network Limiter chrome extension.
Just installed and when I tried to configure the options, the most important one to use a proxy was grayed out. The reason stated was because I needed a newer version of Chrome. Updated Chrome, and still the option is grayed out. My VPN was running, so I don't know what the deal is, but so far, this extension seems useless if I can't use a proxy. Will update my review if I can utilize the option.
Does not work with "latest" version of chrome Version 98.0.4758.102. it says I need a newer version? I think this extension is toast.
the option "use my proxy server(if present)" is disabled for me and I have the latest version of the chrome!
This should just be baked into Chrome so that WebRTC honors proxy selections.
Using newest version chrome beta, the 'use my proxy server' option is greyed out. It says require newer version of chrome.
It's no small wonder this extension doesn't work - IT HASN'T BEEN UPDATED SINCE 01/2016!!! I'm checking out WebRTC Network Limiter.
how to use ?
05 MAY 2021 ... ... I am using it on BRAVE > Version 1.24.82 Chromium: 90.0.4430.93 (Official Build) (64-bit) The option to use the "Proxy" is grayed out. I am being told that is because it is due to CHROME being out of date >> "Grayed out options require newer version of Chrome." I am using the newest version of BRAVE, and it is up to date. Likely some difference between the GOOGLE version and the CHROME that BRAVE employs ... though I do not know that for sure. I ONLY use the browser ... I do not spend any time trying to know anything about it. Anyway ... any other experiences similar to this?
is not blocking webRTC leaking of internal IP# when using VPN, your privacy would be compromise when VPN is not blocking webRTC traffic, do your own proper tests by using these sites; https://browserleaks.com/webrtc https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/ [ click GATHER CANDIDATES button at page bottom, there should be no your local IP addresses reported ] remove extension & report ABUSE to google !!! keep in mind that google is MAKER of this extension !!!
Can't select the 4th option ("Use my proxy server"), as it's grayed out. The very last line in the extension options window states that "grayed out options require newer version of Chrome". I'm using the latest build - just checked and updated, the About page says it's up to date, but the 4th option is still grayed out. In essence, this extension seems to be broken and useless to me.
This plug in doesn't do what it meant, Be Aware!! The Only reason you might be interested in installing this plug in is to make your browsing safer and avoid less browser leaking which is not what I saw after testing (Regardless of which option you might choose on the plug in).
Doesn't work, and complicated. A simple ON or OFF would suffice. Here are settings you must choose but no instructions on the benefits or risk associated: 1. Give me the best media experience: This option allows Chrome to explore all network paths to find the best way to send and receive media, which may be different from normal web traffic. 2. Use my default public and private IP addresses: This option forces Chrome to use the same network path for media as for normal web traffic, except when a web proxy is present. For machines behind a NAT, Chrome will also use the default private address to enhance connectivity. To prevent degraded performance, Chrome will attempt to send media directly instead of using the proxy. 3. Use only my default public IP address: This option is the same as Use my default public and private IP addresses except that Chrome will not use the private default address. 4. Use my proxy server (if present): This option forces Chrome to use the same network path for media as for normal web traffic, including use of a web proxy. Chrome will always attempt to send media through the proxy, which will typically hurt media performance and increase the load on the proxy; furthermore, this behavior may be incompatible with some applications.
I use a Good VPN and most Wed leak detectors showed no leaks but ONE IP leak program showed a partial leak of my local address. So i turned this extension on and selected the last option of force through proxy (for vpns) as some suggested here and the leak is now clear so this extension seems to do something. These web leaks things are sent outside of your vpn tunnel so some detectors cant see them but your ISP certainly will have a record so the vpn encrypted tunnel AND the web leak is critical to lock down. Apparently many quality VPN'S leak even when the tunnel is stable so what good is that for total privacy??
The solution to most people's issue with the extension is to select 'connect only through Proxy server' which is the default option selected despite being on the bottom of the list. Only select the other 3 if you value convenience over privacy and know what you are doing. If you select the first option on the list, you may as well not have the extension at all, I actually don't know why 'option 1' is even there because option 2 is certainly what you'd want to pick if you only want to leak WebRTC to sites that you trust to stream to-and-from. Option 3 is a truly skewed version of option 4. Option 3 will remove all streaming-speed benefits of webRTC leaking while preventing you from truly having an airtight protection of it because it will still leak partially, especially if the website is something where your microphone or webcam can be activated (even if you select no). This will enable your real IP to 'slip' despite offering 0% benefit. Never pick option 3 instead of option 4 if you are smart, both will protect you a good amount against leaks.
Fix it NOW
First; I love this extension. Thank you developer(s). Second; I think it would be an enhancement for the default setting to be the 4th option instead of the 1st option. Forcing traffic to the same path as other traffic would, in my opinion, be a more secure option and therefore be a more sensible default setting. Many users may not know there are options and thus may not change the default less-secure option to a more secure option.
It works, but i need to configure this extension on Windows using policy registry keys (HKLM\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\[extension-id]\policy). Please, explain how...
Great !
Unable to set options, the option menu is flickering out of control.
Useless in Vivaldi 1.15.1147.64 (which is based on Chrome). Unable to change options and make it work.
helpful
No longer works. WebRTC Control works fine though.
Works exactly as I want it to. I use PIA's VPN extension and have this installed alongside in order to prevent leaks in Incognito (where I do not allow PIA).
This extension creates a bug: when opening shortcuts (from say your desktop) to a website, Chrome then displays an error, say it has become 'unresponsive'. Not being able to open shortcuts is a major annoyance, so had to disable this extension.
so functional.
awesome, works well
Use proxy mode with your VPN. All good now.
it good it work well
THIS ONLY WORKS IF YOU ARE CONNECTED TO THE INTERNET USING A VPN SERVICE. If you directly connect to the internet through your ISP then this will do nothing for you. It is not a magic plugin to make you anonymous for free. Reading the comments it seems some people were missing the point of this extension so I just clarified it.
Used to work well but stopped working. I uninstalled and reinstalled it but still does not work.
The issue with WebRTC leaking your public IP when connected to a VPN was fixed with Chrome M48. https://groups.google.com/forum/#!msg/discuss-webrtc/_5hL0HeBeEA/XIRu2N40DQAJ https://bugs.chromium.org/p/chromium/issues/detail?id=518852&can=1&q=WebRTC%20leak&sort=-modified&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified https://tools.ietf.org/html/draft-shieh-rtcweb-ip-handling-00
Simply does not work. Any settings used, still show a cleat RTC leak when tested :/
I MUST HAVE EVEN WITH VPN SOFTWARE, BUT ESPECIALLY EXTENSIONS AND FREE VPNS
GOOD
also had to remove and re add to get it working again
حتی وقتی که از وی پی ان و فیلتر شکن استفاده میکنین بازم هم هکر ها و مقامات میتونن آدرس آی پی شما رو پیدا کنن و غیره...ولی استفاده از این افزونه جلوی این کار رو میگیره .ممنون از گوگل
Using it in combination with Windscribe VPN. Simple and works as advertised, just click the option to "Use my proxy server (if present)"
ipleak.net can detect a leak (maybe devs of WebRTC Network Limiter willl fix it in the future). but if you use ublock origin you're safe (activate in settings)
Does NOT WORK
Not working in Ubuntu 16.10.
Thank you
EXCELLENT - It works great. I use NordVPN. With this extension, all IP/DNS leak tests can't find me. NOTE: If you're using a VPN, use the proxy mode in order for this to work. Don't be alarmed by the icon (which looks to not be working (doesn't show blue.)) Will rate 5 stars when there is a way you can see the extension working.
Stopped working
Seems works ....
Works now in latest chrome by changing options to automatically work with the VPN if detected. Tested on ipleak.net and worked on multiple occasions.
Fixed my webRTC calling issue.
Better descriptions vs WebRTC Leak Prevent
I visited https://ipleak.net/ and discovered that WebRTC detection was revealing my IP address. This extension fixed that problem.
So far it worked together with Betternet VPN I can't see my IP leaking literally on this page @ the "Your IP address - WebRTC detection" But their not saying "No leak, RTCPeerConnection not available" https://ipleak.net/ Torguard can see my VPN IP but they can't literally see my real ip WebRTC Detection it's literally blank https://torguard.net/vpn-webrtc-leak-test.php
not working as it should. my dns still leaks.
ok
Works, but blocks sites from being able to keep you logged in, or to remember this computer. Everytime I sign into google or outlook or even kickstarter I have to reach for my phone for a security code.
It stopped working for me. Removed and re-added again and it seems to be working again. Might be a suggestion if anyone else is finding that it's not blocking your IP anymore
Assuming this is for use with a VPN, in Chrome 48.0.2564.109 m, using Windows 7, this extension does work (even if the VPN is only a browser extension like Zenmate or Browsec), but only if you select "Use my proxy server (if present)" in the options menu, which is pretty much to state the obvious. I'm not sufficiently technically-informed to know why anyone would use the extension with their given IP, so if there is a reason it would be interesting to know.
stopped working
Works for me
While it worked, it worked great. But now it is just taking up space. I select 'use only default ip' but it will not stay selected, so the program does not block the leak.
it will be better.
It works for me behind a VPN
Works perfect for me, including behind VPN using OpenVPN.
Doesn't work. Check https://www.privacytools.io/#webrtc your IP address will still show up even if you use a proxy/VPN
Working perfectly as described! If Browser to Browser communication is a problem, then use the 1st option to determine the best IP address! If doing something naughty then always use the 2nd one...
Does not block IP leak while using VPN.
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.
It works.
It stopped working
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.
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.
It doesn't work in Incognito mode. Still leaks both VPN & Actual IP Addresses. Test page: https://diafygi.github.io/webrtc-ips/
It works.
It didnt work
Still showing Public IP. Tested at https://diafygi.github.io/webrtc-ips/ Only hides local IP not public. I use the latest Chrome.Not using Chrome anymore till google fixed this. All add-ons still show public ip. Back to Firefox
Useless
It's working fine.
This add-on helps remove a VPN flaw that shows your IP address. Isn't that the whole point of a VPN?? If you look at this in the Google app store, you will see that this one is made by Google. Chrome is normally an awesome browser and has a lot fewer issues than many other browser but still has WAY too many entries in the start manager with no details so you cannot trim it down easily as a memory hog or clear it's cache, but fixing security flaws like this are paramount.
It does not work. Back to FF and Pale Moon.
Not working anymore, although it worked for a couple of days. The old Chrome 42 is still working, by adding the following line to Preferences file: "webrtc":{"multiple_routes_enabled":false} Google, how about taking users' privacy more seriously and fix for real this WebRTC mess?
Promoted by privacy site TorrentFreak.
It works as intended.
Promoted by piracy site TorrentFreak.