WebRTC ICE Gathering - Chrome VirtualBox

[Afonso Vilalonga]

Hello!

I was testing a self-made WebRTC application running inside a VirtualBox VM and noticed that when gathering ICE candidates, Chrome only retrieves them from the first non-private network it finds.

For example, if I configure a NAT network on adapter 1 (nic1) and a bridged network on adapter 2 (nic2), I only receive candidates from the network on adapter 1, not from both adapter 1 and adapter 2.

This behavior can also be observed using the Trickle ICE example on the WebRTC samples website.

Is there a reason for this behavior? 

Thank you so much for your time.

[Harald Alvestrand]

(this may get better answers on discuss-webrtc)

does adapter 2 have an assigned IP address?

ICE forms candidates from IP addresses, not interfaces.

(For ease of communication, provide the result of "ip addr" or its VirtualBox equivalent on both interfaces)

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/cad43ea3-e694-4a9e-bd31-873a1b5b6517n%40chromium.org.

[Harald Alvestrand]

FWIW, the answer (I think) is that you need a P2PPortAllocator::Config with enable_multiple_routes=true.

For Chrome, this is set here:

https://crsrc.org/c/third_party/blink/renderer/modules/peerconnection/peer_connection_dependency_factory.cc;drc=81e4ab4dec47df836df1975d9ba09b1caa0f38fb;l=943

Good luck!