Is your feature request related to a problem? Please describe.
Currently, when using ZeroOmega to switch to a proxy profile, the browser's WebRTC traffic (UDP) bypasses the proxy by default. This causes the user's real public and local IP addresses to be exposed during WebRTC leak tests (e.g., on browserleaks.com/webrtc). This significantly undermines privacy protection and IP masking when using a proxy.
Describe the solution you'd like.
I would like to request adding an option in ZeroOmega's "Settings" or "Advanced Options" to control the WebRTC IP Handling Policy.
Specifically, it would be highly beneficial to have a feature similar to the "Use my proxy server (if present)" option found in Google's official WebRTC Network Limiter extension. This would force WebRTC traffic to strictly follow ZeroOmega's active proxy settings.
Technical reference:
This can be easily implemented using the Chrome Extension API chrome.privacy.network.webRTCIPHandlingPolicy. By setting its value to "disable_non_proxied_udp", it forces the browser to send WebRTC traffic only through the proxy server, which perfectly prevents real IP leaks.
Describe alternatives you've considered.
The current workaround requires users to install additional third-party extensions like WebRTC Network Limiter or WebRTC Control solely to handle WebRTC leaks. This creates a fragmented user experience and adds unnecessary overhead to the browser. It would be much more convenient if ZeroOmega could manage this setting natively.
Additional context.
Many ZeroOmega users highly value privacy and IP spoofing/masking. Integrating this feature would greatly improve the "out-of-the-box" security experience, helping users achieve a comprehensive proxy coverage without needing extra plugins.
Thank you for your open-source contributions and for maintaining ZeroOmega!
Is your feature request related to a problem? Please describe.
Currently, when using ZeroOmega to switch to a proxy profile, the browser's WebRTC traffic (UDP) bypasses the proxy by default. This causes the user's real public and local IP addresses to be exposed during WebRTC leak tests (e.g., on browserleaks.com/webrtc). This significantly undermines privacy protection and IP masking when using a proxy.
Describe the solution you'd like.
I would like to request adding an option in ZeroOmega's "Settings" or "Advanced Options" to control the WebRTC IP Handling Policy.
Specifically, it would be highly beneficial to have a feature similar to the "Use my proxy server (if present)" option found in Google's official
WebRTC Network Limiterextension. This would force WebRTC traffic to strictly follow ZeroOmega's active proxy settings.Technical reference:
This can be easily implemented using the Chrome Extension API
chrome.privacy.network.webRTCIPHandlingPolicy. By setting its value to"disable_non_proxied_udp", it forces the browser to send WebRTC traffic only through the proxy server, which perfectly prevents real IP leaks.Describe alternatives you've considered.
The current workaround requires users to install additional third-party extensions like
WebRTC Network LimiterorWebRTC Controlsolely to handle WebRTC leaks. This creates a fragmented user experience and adds unnecessary overhead to the browser. It would be much more convenient if ZeroOmega could manage this setting natively.Additional context.
Many ZeroOmega users highly value privacy and IP spoofing/masking. Integrating this feature would greatly improve the "out-of-the-box" security experience, helping users achieve a comprehensive proxy coverage without needing extra plugins.
Thank you for your open-source contributions and for maintaining ZeroOmega!