You are not understanding what a vpn is and the different types of implementations. Instead of looking for "bugs" that are irrelevant to your vpn implementation, you should be learning about properly setting up your vpn.
no, you have not experienced the bug and you are still misunderstand vpn, which can be more dangerous than no vpn...The VPN appears to be properly set up now from my end, it was pretty straightforward, but obviously questions would remain for anyone that never intended to setup one in the first place; its truly a serious matter for the sake of anyone's privacy and security. The WebRTC VPN Bug was something I just came across when I was doing a random IP check when I was connected to my VPN through my mobile device.
Like you said, its not pertaining to our particular usage.
The aspect remaining now is going about port closure and fiddling around with firewall settings. From there, I should be all set.
Your post again indicates that you have no idea what you are talking about. Pray tell, what is a "public VPN"...The concept of VPN is pretty clear now. Instead of relying on public VPN, I can use my own now, which is an added bonus. Its a pretty good layer of security.
That bug was meant to serve as a distraction when I comparing IP's. It serves no relevance here
Stop copy and pasting nonsense...Go study up on vpn...Problem lays in the API which causes browsers like chrome and opera to expose such info, otherwise no big deal here, probably irrelevant to our intended purpose, back on topic
