Skip to main content

Configure QUANTEEC for eCDN usage

The QUANTEEC plugin can be used to optimize the performance of video distribution within a company, known as an eCDN (enterprise Content Delivery Network). In your QUANTEEC customer area, you can set up one or more eCDN configurations to suit your needs.

Configure sites and eCDN rules​

In the Panel​

In the next session of the page called List of sites, you can create specific P2P rules for global use cases, sites, and/or subdomains. This configuration gives you precise control over the way data is exchanged within a corporate network, for example, by limiting P2P data exchanges within a single site with the same public IP address.

Here is a simple example of what an eCDN configuration with multiple sites might look like:

ecdn sites example

If a subnet is set, a public IP is mandatory. If you do not know the public IP, use "0.0.0.0".

In the plugin​

By default, the Quanteec Plugin will not try to use the local private IP. In order to activate the local IP retrieving, an option must be added in the configuration:

let quanteecConfig = {
      quanteecKey:"<enter-your-custom-videoID>",
      videoID:"<enter-your-custom-videoID>",
      useSubnets: true
}

Managing mDNS

By default, WebRTC uses a protocol called mDNS (multicast DNS) to hide the private IP. The protocol allows devices on the same local network to resolve hostnames (e.g., my-device.local) to IP addresses without needing a central DNS server. In WebRTC, mDNS is used to enhance privacy by hiding a user’s real local IP address from websites. Instead of exposing private IPs directly during WebRTC sessions, mDNS generates obfuscated ICE candidates (e.g., 12345.local) that are resolved to private IP addresses only within the local network.

Using mDNS in a corporate network can bring some challenges:

  • The private IP are hidden, making it impossible for Quanteec to associate the peers with subnet rules.
  • The network might block multicast traffic (common in enterprise networks or restrictive environments), and WebRTC peer connections may fail.
  • The protocol only works within the same local network, and if users are on different subnets, the obfuscated addresses cannot be resolved.

Because of that, you might need to disable mDNS in the browser in order for the Quanteec Plugin to perform well in your environment.

When is disabling mDNS NOT needed?​

Considering your network architecture, it might not be needed to disable mDNS if:

  • mDNS is not blocked in the local network
  • users are behind the same router

In these scenarios, the Quanteec Plugin should work just fine without any additional configuration. If at least one of the conditions is not respected, the Quanteec Plugin might fail to create connections and offload the network.

How to disable mDNS?​

Disabling mDNS in the browsers depends on the browser and the OS used.

How to disable mDNS in Chrome, Chromium, and Edge​

In Chrome-based browsers, mDNS can be disabled via the chrome flag #enable-webrtc-hide-local-ips-with-mdns.

Steps to Disable mDNS via Chrome Flags​

  1. Open the browser (Chrome, Edge, or any Chromium-based browser).
  2. In the address bar, type: 
    chrome://flags/#enable-webrtc-hide-local-ips-with-mdns
  3. Press Enter.
  4. Find the flag named " Anonymize local IPs exposed by WebRTC".
  5. Change the setting from Default or Enabled to Disabled.

Mozilla Firefox​

In Firefox, mDNS can be deactivated from embedded configurations.

  1. Open Firefox Configuration Settings:

    • Open Firefox.
    • In the address bar, type: 
      about:config
    • Press Enter.
    • Accept the warning message that says, "Proceed with Caution."

  2. Search for the Allowed Domains Setting:

    • In the search bar, type: 
      media.peerconnection.ice.obfuscate_host_addresses.whitelist

  3. Modify the Setting:

    • This preference allows you to specify domains for which mDNS is disabled.
    • If the preference does not exist:
      • Click the Add button (+ icon).
      • Choose String as the type.
      • Enter the preference name: 
        media.peerconnection.ice.obfuscate_host_addresses.whitelist
    • Set its value to a comma-separated list of domains for which you want to disable mDNS: 
      example.com,quanteec.com
    • Domains must be entered without http:// or https://.

  4. Restart Firefox:

    • Close all Firefox windows and restart the browser for the changes to take effect.