WebRTC test page doesn't work when mDNS candidate protection enabled |
|||||
Issue descriptionChrome Version: Version 72.0.3608.4 (Official Build) canary (64-bit) OS: Mac What steps will reproduce the problem? (1) Enable mDNS protection via chrome://flags/#enable-webrtc-hide-local-ips-with-mdns (2) Go to https://webrtc.github.io/samples/src/content/datachannel/basic/ (3) Click Start button What is the expected result? Send button lights up What happens instead? Send button doesn't light up, indicating a connection could not be made Please use labels and text to provide additional information. If this is a regression (i.e., worked before), please consider using the bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help us identify the root cause and more rapidly triage the issue. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Nov 14
,
Nov 15
Issue 905597 has been merged into this issue.
,
Nov 15
Not sure if it's relevant for the Chrome <-> Chrome scenario as well, but Firefox rejects all of Chromes candidates because of this: https://tools.ietf.org/html/rfc5245#section-15.1 "<rel-addr> and <rel-port> MUST be present for server reflexive, peer reflexive, and relayed candidates."
,
Dec 17
Qingsi has been working on this already.
,
Jan 2
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by juberti@google.com
, Nov 14