Possible ipv4 leak? For RPI 3

gam9pgam9p
in General Privacy Discussion
I have a PIA account and I set up my pi to sign in and it works. My problem, at least I think it's a problem is that when i check my ip with ipleak.net, in the webrtc part it shows my VPN ip, but under that it shows "local ipv4 address: ...."
So is this a leak? Or is this the webrtc bug where I just need to install the chrome extension thing?

Thanks

Comments

  • itsmefloralucaitsmefloraluca
    it's a webrtc bug i dont know if chrome has an extension it did before.I use firefox with there extension or you can do it manually also with firefox.
  • gam9pgam9p
    ok, the local ipv4 address is just a bug, good to know thanks.
    ill just do that extension thing with chrome.

    Thanks.
  • KharizKhariz
    I don't know about the use of the word "bug".  WebRTC is leaking your local ipv4.  But yeah, the solution is to disable WebRTC.  In Chrome you can use "WebRTC Network Limiter" plugin.  uBlock also can block it in the current version of their plugin.
  • bobclampetbobclampet
    Does uBlock? I see their setting, but my local IP is definitely still leaking...
  • josh1985josh1985
    Why would my Webrtc IP be shown as 10.24.10.6? Win 7, Chrome -  https://ipleak.net/10.24.10.6
  • bgxsecbgxsec
    edited May 2017
    josh1985 said:
    Why would my Webrtc IP be shown as 10.24.10.6? Win 7, Chrome -  https://ipleak.net/10.24.10.6
    Because webrtc accesses the NAT part of your OS.

    gam9p said:
    ok, the local ipv4 address is just a bug, good to know thanks.
    ill just do that extension thing with chrome.

    Thanks.
    No, its not a bug. Its an actual IP address in use by your system which WebRTc is actually getting and that's an intended 'purpose built'  function of WebRTC. An  intended 'purpose built'  function is not a bug, its intended normal and expected operation.

    Does uBlock? I see their setting, but my local IP is definitely still leaking...

    @ you three:

    Although it is a private IP address (local IP), those are as common as dirt and there are probably millions of others with the same private IP in use, a private IP is not route'able on the internet so no issue there and no one can trace that back to you specifically.

    However, the fact that the WebRTC test shows any IP address, private or public, means that WebRTC can still access the NAT which means its still possible your real ISP IP address could be exposed. Disable WebRTC for/in the browser. For IE/Edge you don't need to worry about it, for Firefox, Chrome, Opera, (and maybe some other browsers especially if based on Chrome) it needs to be disabled.

    Even if one does not show a WebRTC leak on the test, still disable it for/in the browser. The test uses a simple basic implementation of the WebRTC test, there are now servers which are more advanced. Even if you do not show a WebRTC leak on the test now a more advanced implementation on a server somewhere may still reveal your real ISP IP, so disable WebRTC anyway even if you don't think you need to do so...

    WebRTC is also supported by the OS's platforms Android & iOS but there is no way to disable that support in those (last time I looked), however, unless you use a browser that has it enabled in those there won't be an issue.
  • josh1985josh1985
    @bgxsec I don't believe you can turn WebRTC off in Chrome on a Windows machine?
  • m32b64m32b64
    edited June 2017
    josh1985 said:
    @bgxsec I don't believe you can turn WebRTC off in Chrome on a Windows machine?

    The PIA Chrome extension has a setting to block WebRTC.
  • m32b64m32b64
    josh1985 said:
    @bgxsec I don't believe you can turn WebRTC off in Chrome on a Windows machine?
    There is an extension on the Chrome Web Store.  WebRTC Network Limiter .
Sign In or Register to comment.