WebRTC, known as a browser plugin, is commonly used for website applications that require a quick, straight-forward connection. As WebRTC creates a connection through the UDP protocol, the link should not be routed via proxy servers utilized in browsers. Websites have to be put into service in revealing the actual public IP address and local IP address, even when a proxy is available. Also, a similar plugin should be used to retrieve local IP address and locate media devices.

The altered mode of WebRTC configures both local and public IP addresses in launching browser profile. Addresses should be equivalent to the IP of browser profile configuration.

The course of action ‘fill on start based on external IP’ defines that the browser profile will connect first to a server when launched. The real WebRTC external IP is easily detected. Therefore, it would be better to return and then configure the WebRTC Public IP. Every period, IP addresses will change, by then WebRTC Public IP instantly adjusts corresponding to its changes.

If option is left disabled, it means WebRTC Public IP is already manually configured.

As users tap on ‘new browser profile’ or ‘get new fingerprint’, the browser will generate local IP addresses. Users can configure it manually. However, some browser profile does not allow local IP address configuration.

Local IP addresses need to be within the range to make it valid. The considered valid range is:

It is common for users in the residences to have 0 in their third digit or at block C, and arbitrary numbers on the 4th or block D. Meanwhile, those users in a company obtain another set of numbers other than 0 on block C and D.