Media/WebRTC/Privacy: Difference between revisions

→‎Prefs that control ICE Candidate generation: Update Prefs to account for changes introduced in 1297416
(Removed non-10s reference as bug has been fixed)
(→‎Prefs that control ICE Candidate generation: Update Prefs to account for changes introduced in 1297416)
Line 21: Line 21:
** LAN IP addresses are not generated, the external IP address for that interface is (for a VPN, the exit portal of the VPN)
** LAN IP addresses are not generated, the external IP address for that interface is (for a VPN, the exit portal of the VPN)
** If your router does not support 'hairpinning', a within-LAN call will end up being routed through an external TURN server
** If your router does not support 'hairpinning', a within-LAN call will end up being routed through an external TURN server
* '''media.peerconnection.ice.no_host''' -- boolean (default false) -- eliminate all local addresses from the candidates (Firefox 51) -- {{Bug|1297416}}
* '''media.peerconnection.enabled''' -- boolean (default true) -- enables/disabled ability to create RTCPeerConnection objects (all recent Firefox versions)
* '''media.peerconnection.enabled''' -- boolean (default true) -- enables/disabled ability to create RTCPeerConnection objects (all recent Firefox versions)


Line 34: Line 35:
| use_document_iceservers || Yes || Yes || Yes || N/A || All interfaces will be used to try to connect to the relay
| use_document_iceservers || Yes || Yes || Yes || N/A || All interfaces will be used to try to connect to the relay
|-
|-
| default_address_only || No || Yes || Yes || N/A || Only the interface with the default route
| default_address_only || Yes || Yes || Yes || N/A || Only the interface with the default route
|-
| no_host || No || Yes || Yes || N/A || All interfaces will be used
|-
|-
| peerconnection.enabled || No || No || No || Always || N/A
| peerconnection.enabled || No || No || No || Always || N/A
Confirmed users
908

edits