You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Connection IPs and Outgoing IPs. Connection IPs can be derived from the DNS record associated with a given hostname and region. For example: us-siliconvalley.privateinternetaccess.com
While you are connecting to the VPN service using one of the associated IPs, the public/outgoing IP address associated with your VPN session will be different.
We will need these two lists of IPs for different purposes. For example, if you wanted to stop a user from connecting TO a PIA VPN from inside your network/server you could block the Connection IP. If you wanted to whitelist or blacklist access FROM the PIA VPN service, you would need to use the Outgoing IP.
The Outgoing IP may be significantly harder to determine, given you will have to actually connect to the VPN region and document its IP. Further, it may actually be safe to determine the associated Outgoing IP subnet, and consider the IPs as used by PIA. (This is a sweeping assumption that I made with the original IP list)
The text was updated successfully, but these errors were encountered:
We will have two types of IP ranges for PIA.
Connection IPs and Outgoing IPs. Connection IPs can be derived from the DNS record associated with a given hostname and region. For example:
us-siliconvalley.privateinternetaccess.com
While you are connecting to the VPN service using one of the associated IPs, the public/outgoing IP address associated with your VPN session will be different.
We will need these two lists of IPs for different purposes. For example, if you wanted to stop a user from connecting TO a PIA VPN from inside your network/server you could block the Connection IP. If you wanted to whitelist or blacklist access FROM the PIA VPN service, you would need to use the Outgoing IP.
The Outgoing IP may be significantly harder to determine, given you will have to actually connect to the VPN region and document its IP. Further, it may actually be safe to determine the associated Outgoing IP subnet, and consider the IPs as used by PIA. (This is a sweeping assumption that I made with the original IP list)
The text was updated successfully, but these errors were encountered: