RTCPeerConnection stuck at gathering state, IPV6 Only Network

[Ankur Deep Jaiswal]

Hi,

What can cause RTCPeerConnection to be stuck at gathering state, without even collecting local candidates,

Have Tried all/relay options, but no candidates

This seems to impact any chromium based implementation, Google Chrome, Edge.

Firefox Had No Issues, was able to gather local and remote candidates.

This is an IPV6 only network and firefox was gathering anonymized local Candidates,

Chrome  93.0.4577.63, Windows 10, IPV6 Only Network

Firefox: 91

Help Appreciated in advance

Ankur Deep Jaiswal

[Harald Alvestrand]

Can you send us the interface configuration (I think it's "ip addr" on windows, but unsure)?

In particular, the IPv6 addresses in use?

There's a couple of outstanding bugs wrt candidate gathering on IPv6 networks, but it has been hard to get a repro; one known issue is that Chrome/WebRTC refuses to use MAC-based non-privacy-enhanced IPv6 addresses for privacy reasons (they are perfect tracking tokens).

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/6f601a1e-c744-46a1-a46f-3b9f92b407efn%40googlegroups.com.

[Ankur Deep Jaiswal]

Hi,

do you mean ipconfig ?

[Ankur Deep Jaiswal]

Hi, This is what i was able to gather.

Windows 10.0.18363.1556

Connection-specific DNS Suffix . :

IPv6 Address .  .  .  .  .  .  .  . . . . . . : fd00:4408:2009:1::23aa

Link-local IPv6 Address .  .  .  . . . : fe80::81e3:6d0d:9cf5:9f9a%5

Default Gateway .  .  .  .  .  .  . . . . .: fd00:4408:2009:1::2301

                                                            fe80::5:73ff:fea0:17%5

Please do let me know, if more info in needed.

Thanks