Force Chromium to Use Proxy IP Address in WebRTC instead of Public IP
#2,059 opened on Aug 23, 2022
Repository metrics
- Stars
- (18,674 stars)
- PR merge metrics
- (Avg merge 1d 11h) (9 merged PRs in 30d)
Description
Description
Force Chromium to Use Proxy IP Address in WebRTC instead of Public IP while using VPN
Who's implementing?
- I'm willing to implement this feature myself
The problem
Browsers leaks Public IP through WebRTC protocols while routing traffics through browser specific proxies such as chrome vpn extensions. but using Native VPN Application (OS Specific) doesn't produce public ip through WebRTC.
How to overcome this problem and force chromium to use proxy IP instead of public IP for WebRTC communication.
Note- Blocking WebRTC from Browser does hide the public ip but many websites eg. google.com, godaddy.com treats you as a bot and blacklist you from using some of their services.
This issue is more related to browser fingerprinting than ungoogling stuffs..
No Extensions available to solve this problem till now but some of the automation tools such as Kameleo.com is able to do such things but those are pricy.
Possible solutions
Force chromium to use proxy ip through ICE Framework TURN/STUN signaling services
Alternatives
No response
Additional context
No response