Closed Bug 1244562 Opened 10 years ago Closed 10 years ago

no host candidates on Windows 10

Categories

(Core :: WebRTC: Networking, defect, P1)

46 Branch
Unspecified
Windows 10
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: philipp, Assigned: drno)

References

Details

Attachments

(2 files)

Attached file about:webrtc log
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.97 Safari/537.36 Steps to reproduce: I was testing https://webrtc.github.io/samples/src/content/peerconnection/pc1/ in 46.0a2 (2016-01-31) on Windows 10 (insider build 11102) and got an ice failure. No ice candidates were gathered. Actual results: the log shows this error: (generic/ERR) UDP socket error:Internal error at c:/builds/moz2_slave/m-aurora-w32-ntly-000000000000/build/src/dom/network/UDPSocketParent.cpp:169 this=07625E60 (ice/WARNING) ICE(PC:1454259631482000 (id=2147483652 url=http://webrtc.github.io/samples/src/content/peerconnection/pc1/)): couldn't create socket for address IP6:[2001:0:9d38:90d7:c14:11fe:cd72:e118]:0/UDP (ice/ERR) ICE(PC:1454259631482000 (id=2147483652 url=http://webrtc.github.io/samples/src/content/peerconnection/pc1/)): couldn't create any valid candidates I can reproduce that on meet.tokbox.com, even though there are relay candidates gathered and the connection succeeds. Expected results: This works in 44 and 47. Both versions gather a candidate from that interface.
This is a teredo interface, ipconfig shows this: Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2001:0:9d38:90d7:c14:11fe:cd72:e118 Link-local IPv6 Address . . . . . : fe80::c14:11fe:cd72:e118%7 Default Gateway . . . . . . . . . : ::
OS: Unspecified → Windows 10
Assignee: nobody → drno
Status: UNCONFIRMED → NEW
Rank: 16
Ever confirmed: true
Priority: -- → P1
45.0b1 is not affected
Two strange things: 1) I can't get Teredo working on my Win 7 machine. It looks like Microsoft took teredo.ip6.microsoft.com down. Not sure how to enable it. 2) Failing to create an address on any given interface should be ignored and thus not end up in the "couldn't create any valid candidates". No real idea what is going on. Would it be possible to get a full ICE debug log file https://wiki.mozilla.org/Media/WebRTC/Logging#ICE.2FSTUN.2FTURN with R_LOG_LEVEL=9
Attached file ice.txt
teredo failure seems unrelated. I disabled my teredo interface and it still failed.
Comparing the log to our code the only way this makes sense if somehow the ICE policy gets set to 'relay'. Can you please double check the the user pref 'media.peerconnection.ice.relay_only' in about:config is set to false?
Flags: needinfo?(philipp)
duh, that was it. Thanks Nils!
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(philipp)
Resolution: --- → INVALID
Blocks: 1246363
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: