Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
ipleak.net circumvents WebRTC blocking #1995
Steps to reproduce
### Actual behavior
For establishing a p2p connection between two computers (p1 and p2), you must find out a local IP of the p1 (i.e. the address in the local network), the global IP of the p1's provider and send these IPs to the p2 (and then the same procedure for p2).
It's quite easy to get local IP, but to determine global IP you have to use STUN/TURN servers. The main purpose of such servers is to send back the global IP when a request from the computer behind the NAT-router is received. When the option "Block WebRTC" is enabled, AdGuard blocks such requests (as you can see in the filtering log - https://uploads.adguard.com/buker_mhchu.png), so determining of "your" global IP address will become impossible. Thus, establishing of p2p connection is also impossible.
The IP address of the computer, specified in
To sum up, in fact, there is no WebRTC leak in case of "Block WebRTC" option is enabled.