local network chromecast
Hello everyone,,
Just getting set-up with PIA abs have a question which i couldn't seem to find any answers to in the forum. Vpn is working as expected through the android app, but want to cast from my android device to Chromecast. If i uncheck the 'block local network' check box from the PIA app whilst the vpn is running I can cast the screen off my Android to the tv via chromecast. Does this mean that my IP is still hidden? E.g. my chromecast is not connected through my PIA VPN... Thanks.
Just getting set-up with PIA abs have a question which i couldn't seem to find any answers to in the forum. Vpn is working as expected through the android app, but want to cast from my android device to Chromecast. If i uncheck the 'block local network' check box from the PIA app whilst the vpn is running I can cast the screen off my Android to the tv via chromecast. Does this mean that my IP is still hidden? E.g. my chromecast is not connected through my PIA VPN... Thanks.
Comments
This is slightly complex if you do not understand networking at all, but I will explain.
When you connect to PIA, you create a secure tunnel between your computer and the PIA servers. This tunnel is like the real world object that has only one entrance and only one exit. To allow the availability to access local resources (i.e. printers, storage devices, phones or chromecasts or other devices) requires that you essentially "break" a part of this tunnel to allow for these connections. This is accomplished through basic firewall rules in the PIA application. These firewall rules are generic and will work for most home networks that use either a Class A, Class B or Class C private network addressing scheme. The actual device running the VPN will still be masked, but the other resource is not masked by association with the masked device.
Additionally, by allowing for Local Area Network access, please keep in mind that there is a small chance that you theoretically could be attacked in a roundabout way not through the secure tunnel, but through the unsecure connection. This would require that an attacker know your specific IP Address, any weaknesses presented by the connecting device as well as what ports are being used to make this connection. For all practical purposes, the risk is extremely small and nearly negligible.