The WebRTC IP Leak Controversy
WebRTC (Web Real-Time Communication) is the protocol that allows browsers to handle high-speed video and audio chats directly, without plugins. To establish the fastest possible peer-to-peer connection (especially when both users are on the same corporate network or home LAN), WebRTC was originally designed to query the operating system and share the user’s *local* IP address (e.g., 192.168.1.5) with the web application.
Privacy advocates quickly pointed out a major flaw: this behavior allowed any website to silently ping the WebRTC API and map out a user’s internal home network, bypassing VPNs which normally hide the external IP. In response, Google introduced the “Anonymize local IPs exposed by WebRTC” feature. When active, Chrome generates a fake, anonymized mDNS (Multicast DNS) hostname (like random-string.local) instead of handing over the actual numeric local IP. While this is fantastic for privacy, it completely breaks WebRTC video calls on older, enterprise networks that do not support mDNS routing, causing internal company video chats to fail.
How to Turn Off Local IP Anonymization
If you are a network administrator trying to fix internal WebRTC routing issues on a closed corporate LAN, you can disable this anonymization via the experimental flags menu.
- Open Google Chrome.
- Click inside the main address bar at the top of the browser.
- Type
chrome://flagsand press Enter. - On the “Experiments” page, use the search bar to look for Anonymize local IPs exposed by WebRTC.
- If the flag is available, click the dropdown menu next to it and change it from “Default” (or Enabled) to Disabled.
- Click the blue Relaunch button at the bottom of the screen.
Warning: Disabling this will expose your actual local LAN IP address to any website that runs a WebRTC script. Only do this if strictly required for internal enterprise video conferencing.