[Webkit-unassigned] [Bug 173052] RTCDataChannel connectivity issues in Safari 11

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=173052

--- Comment #1 from youenn fablet <youennf at gmail.com> ---
(In reply to Ashley Gullen from comment #0)
> WebRTC DataChannels appear to have connectivity issues on Safari 11 with
> macOS High Sierra.
> 
> This is a simple DataChannel-based multiplayer game demo made in Construct
> 2: https://www.scirra.com/labs/rtcgame/
> 
> Simply open the page, type in a name and click 'Join'. If you do this with
> two browsers, you should be able to see each player's actions as they move
> around with WASD and mouse move & click. However in Safari 11 the following
> cases fail to connect where Chrome can:
> 
> 1) Two Safari windows on the same machine cannot connect
> 2) Safari & Chrome on a Windows 10 machine on the same LAN cannot connect
> 3) Safari & Chrome on a remote Windows machine (over the Internet) establish
> a connection, but after a moment the DataChannel send() method starts
> throwing "InvalidStateError (DOM Exception 11): The object is in an invalid
> state."
> 
> Chrome and Firefox can interoperate in all of these cases; so should Safari.

Hi Ashley, thanks for the report.
Contrary to Chrome and Firefox, we do not leak private IP addresses access unless camera or microphone access is also granted.

You can use the Debug menu (see https://webkit.org/debugging-webkit/ to use "defaults write" magic to make it appear). Then you can go to "Media Flags" and check "Disable ICE candidate filtering". Once these options are set, make sure to create a new tab so that these options are propagated properly.

https://webrtc.github.io/samples/src/content/datachannel/basic/ does not work without this change but works with this change.

Would be great if you can test that and report the results.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170608/660e45a4/attachment-0001.html>