New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 905597 link

Starred by 1 user
Status: Duplicate
Merged: issue 905422
Owner: ----
Closed: Nov 15
Cc:
█ fi...@appear.in
sprang@chromium.org
rantonysamy@chromium.org
terelius@chromium.org
jansson@chromium.org
█ juberti@chromium.org
█ emadomara@chromium.org
webrtc-network-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Enabling the #enable-webrtc-hide-local-ips-with-mdns flag breaks P2P connection

Project Member Reported by vasanthakumar@chromium.org, Nov 15 
Chrome Version: 72.0.3611.0
OS: Mac OS 10.13.6

What steps will reproduce the problem?
Go to chrome://flags and enable #enable-webrtc-hide-local-ips-with-mdns
(1)Goto https://webrtc.github.io/samples/src/content/peerconnection/pc1/
(2)Click Start, Call button

What is the expected result?
Peer video should work.

What happens instead?
No peer video is seen. 

This also has similar behavior when using firefox as a peer user for other popular webrtc apps like appr.tc, appear.in etc [InterOP]

Does this reproduce while not using the flag?
No it reproduces only when the flag was enabled. 

Bug Source: https://twitter.com/juberti/status/1062850132507381763

Details about the feature: https://tools.ietf.org/html/draft-ietf-rtcweb-mdns-ice-candidates-02

Comment 1 by vasanthakumar@chromium.org, Nov 15

Components: Blink>WebRTC>PeerConnection
Labels: OS-Mac
webrtc_internals_dump (22).txt
372 KB View Download
webrtc_internals_dump Appear.in.txt
202 KB View Download

Comment 2 by fi...@appear.in, Nov 15 

the pc1 sample works for me -- if it does not on your network that might be a very interesting case to consider.

the appear.in failure is odd since it should just fall back to either the srflx or relay candidates. Unclear who is at fault here, might be either chrome or firefox acting badly.

Comment 3 by vasanthakumar@chromium.org, Nov 15 

@fippo: Yes I also feel the same. Here comes another information which is very useful.

Use chrome with the flag (DUT) and the peer device also have chrome (Disabled flag). [Chrome <-> Chrome]
observation: Works fine for appr.tc and appear.in. Thus this issue is specific to Chrome <-> Firefox.

Comment 4 by vasanthakumar@chromium.org, Nov 15

Cc: terelius@chromium.org sprang@chromium.org

Comment 5 by guidou@chromium.org, Nov 15

Components: -Blink>WebRTC>PeerConnection Blink>WebRTC>Network

Comment 6 by jeroendb@chromium.org, Nov 15 

There is a remaining issue on the Mac that prevents this from working. Currently this feature only works on Linux and Windows.

Comment 7 by jeroendb@chromium.org, Nov 15

Mergedinto: 905422
Status: Duplicate (was: Untriaged)

Comment 8 by fi...@appear.in, Nov 15 

can we undupe this and handle the interop failures here? Or should I file a new issue?

Comment 9 by jeroendb@chromium.org, Nov 15 

Please create a new issue for the interop, though if it is related to mDNS candidates on Mac OS we'll probably have it blocked by this one..

Comment 10 by juberti@google.com, Nov 15 

I'm interested to understand the non-pc1 failures better - if you can open new bugs for appear.in and chrome-firefox, we can investigate those individually. As fippo mentions, I would have expected appear.in to fall back to TURN.

Comment 11 by fi...@appear.in, Nov 15 

justin: new issue just for appear.in in https://bugs.chromium.org/p/chromium/issues/detail?id=905690
►

Sign in to add a comment