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

Issue 721322 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

No ICE host candidates at all

Reported by ibc@aliax.net, May 11 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. Create a PeerConnection (with our without ICE servers) and do the normal setLocalDescription + setRemoteDescription.
2. Or just try it in https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/
3. ICE gathering completes without any host candidate.

What is the expected behavior?
Host candidates should be gathered.

What went wrong?
No host candidates at all, but just reflexive ones.

Did this work before? N/A 

Chrome version: 58.0.3029.110  Channel: stable
OS Version: OS X 10.12.4
Flash Version: 

This just happens in my Chrome stable in Mac OSX (currently 58.0.3029.110) and also previous stable versions. It does NOT happen in Canary.

chrome://webrtc-internals clearly shows that no host candidates are gathered.

I can reproduce this in many places:

* https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/
* https://tryit.jssip.net/
* or in ANY WebRTC app.

This is basically annoyed.
 

Comment 1 by ibc@aliax.net, May 11 2017

> This is basically annoyed.

I meant "annoying". Actually I cannot get WebRTC work on localhost or local networks.

Comment 2 by rsesek@chromium.org, May 11 2017

Components: Blink>WebRTC

Comment 3 by guidou@chromium.org, May 11 2017

Components: -Blink>WebRTC Blink>WebRTC>Network
Labels: Needs-Triage-M58
Labels: TE-NeedsTriageHelp
Labels: Needs-Feedback
I'm still getting host candidates. Are you sure you're not using the Network Limiter extension?

Also, since you can reproduce it in 58 but not Canary, could you try bisecting a little further? You could try with 59, with a Beta build.

Comment 7 by ibc@aliax.net, May 17 2017

OK, found the issue. It's due the Privacy Badger extension. It comes with a checkbox called "Prevent WebRTC from leaking local IP address". I have it disabled but still it filters local candidates.

Sorry for the noise, you can close this issue.
Project Member

Comment 8 by sheriffbot@chromium.org, May 17 2017

Cc: deadbeef@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "deadbeef@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)

Sign in to add a comment