Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Could somebody help in analyzing ICE connection logs

273 views
Skip to first unread message

shazzzzzzzz

unread,
May 1, 2019, 12:44:48 PM5/1/19
to mozilla-...@lists.mozilla.org
Firefox fails to gather relay candidates only on my machine.

Here is my setup
- Open Suse leap 42.3
- Firefox - 66.0.3 (64-bit)
- TURN server - coturn configured to listen on port 192.168.144.87:443 (TCP and TCP/TLS)
- Forced use of relay candidates - media.peerconnection.ice.relay_only = true
- No firewall rules
- ICE config
- turn:webrtc1-144-87.de:443?transport=tcp
- turns:webrtc1-144-87.de:443?transport=tcp
- TURN server URL http://webrtc1-144-87.de/ is reachable from Firefox and maps to IP - 192.168.144.87
- I make a webrtc audio call

The same TURN server works fine with Chrome and Firefox on other machines. Also on Wireshark, I see no packets being exchanged between my machine and TURN server either!

I want help in reading ICE logs to understand why Firefox fails to gather candidates only on this specific machine.

Thanks for any help!
------------------------------------------------------------------
ICE logs(about:webrtc)

ICE(PC:1556636332416317 (id=19327352844 url=https://test.de:3443/test_phone.html?c=config&config=test)): relay only option results in no host candidate for IP4:192.168.251.172:0/UDP

ICE(PC:1556636332416317 (id=19327352844 url=https://test.de:3443/test_phone.html?c=config&config=test)): relay/proxy only option results in ICE TCP being disabled

ICE(PC:1556636332416317 (id=19327352844 url=https://test.de:3443/test_phone.html?c=config&config=test)): relay only option results in no host candidate for IP4:192.168.251.172:0/UDP

ICE(PC:1556636332416317 (id=19327352844 url=https://test.de:3443/test_phone.html?c=config&config=test)): relay/proxy only option results in ICE TCP being disabled

Write buffer not empty for IP4:192.168.144.87:443/TCP 44 - already armed (@0x7f12828051f4), not connected

NrSocketProxy::OnClose 0x7f1282804c00 reason=2147500037 name=NS_ERROR_FAILURE

NrSocketProxy::OnClose 0x7f1282805800 reason=2147500037 name=NS_ERROR_FAILURE

NrSocketProxy::OnClose 0x7f1282806c00 reason=2147500037 name=NS_ERROR_FAILURE

NrSocketProxy::OnClose 0x7f1282807800 reason=2147500037 name=NS_ERROR_FAILURE

Write buffer not empty for IP4:192.168.144.87:443/TCP 44 - already armed (@0x7f1282805df4), not connected

Write buffer not empty for IP4:192.168.144.87:443/TCP 44 - already armed (@0x7f12828071f4), not connected

Write buffer not empty for IP4:192.168.144.87:443/TCP 44 - already armed (@0x7f1282807df4), not connected

STUN-CLIENT(relay(IP4:192.168.251.172:0/TCP|webrtc1-144-87.de:443)::TURN): Timed out

TURN(relay(IP4:192.168.251.172:0/TCP|webrtc1-144-87.de:443)): mode 20, nr_turn_client_error_cb

TURN(relay(IP4:192.168.251.172:0/TCP|webrtc1-144-87.de:443)) failed

TURN(relay(IP4:192.168.251.172:0/TCP|webrtc1-144-87.de:443)): cancelling

ICE-CANDIDATE(relay(IP4:192.168.251.172:0/TCP|webrtc1-144-87.de:443)): nr_turn_allocated_cb called with state 4

ICE-CANDIDATE(relay(IP4:192.168.251.172:0/TCP|webrtc1-144-87.de:443)): nr_turn_allocated_cb failed

STUN-CLIENT(relay(IP4:192.168.251.172:0/TLS|webrtc1-144-87.de:443)::TURN): Timed out

TURN(relay(IP4:192.168.251.172:0/TLS|webrtc1-144-87.de:443)): mode 20, nr_turn_client_error_cb

TURN(relay(IP4:192.168.251.172:0/TLS|webrtc1-144-87.de:443)) failed

TURN(relay(IP4:192.168.251.172:0/TLS|webrtc1-144-87.de:443)): cancelling

ICE-CANDIDATE(relay(IP4:192.168.251.172:0/TLS|webrtc1-144-87.de:443)): nr_turn_allocated_cb called with state 4

ICE-CANDIDATE(relay(IP4:192.168.251.172:0/TLS|webrtc1-144-87.de:443)): nr_turn_allocated_cb failed

STUN-CLIENT(relay(IP4:192.168.251.172:0/TCP|webrtc1-144-87.de:443)::TURN): Timed out

TURN(relay(IP4:192.168.251.172:0/TCP|webrtc1-144-87.de:443)): mode 20, nr_turn_client_error_cb

TURN(relay(IP4:192.168.251.172:0/TCP|webrtc1-144-87.de:443)) failed

TURN(relay(IP4:192.168.251.172:0/TCP|webrtc1-144-87.de:443)): cancelling

ICE-CANDIDATE(relay(IP4:192.168.251.172:0/TCP|webrtc1-144-87.de:443)): nr_turn_allocated_cb called with state 4

ICE-CANDIDATE(relay(IP4:192.168.251.172:0/TCP|webrtc1-144-87.de:443)): nr_turn_allocated_cb failed

STUN-CLIENT(relay(IP4:192.168.251.172:0/TLS|webrtc1-144-87.de:443)::TURN): Timed out

TURN(relay(IP4:192.168.251.172:0/TLS|webrtc1-144-87.de:443)): mode 20, nr_turn_client_error_cb

TURN(relay(IP4:192.168.251.172:0/TLS|webrtc1-144-87.de:443)) failed

TURN(relay(IP4:192.168.251.172:0/TLS|webrtc1-144-87.de:443)): cancelling

ICE-CANDIDATE(relay(IP4:192.168.251.172:0/TLS|webrtc1-144-87.de:443)): nr_turn_allocated_cb called with state 4

ICE-CANDIDATE(relay(IP4:192.168.251.172:0/TLS|webrtc1-144-87.de:443)): nr_turn_allocated_cb failed

ICE(PC:1556636332416317 (id=19327352844 url=https://test.de:3443/test_phone.html?c=config&config=test)): peer (PC:1556636332416317 (id=19327352844 url=https://test.de:3443/test_phone.html?c=config&config=test):default) has no stream matching stream PC:1556636332416317 (id=19327352844 url=https://test.de:3443/test_phone.html?c=config&config=test) transport-id=transport_0 - f3be2c21:d2c661d7fd52656d1674317deaed38c1

+++++++ END ++++++++

Nils Ohlmeier

unread,
May 1, 2019, 12:49:29 PM5/1/19
to shazzzzzzzz, mozilla-...@lists.mozilla.org
Hello,

based on the logs you should check if you have set media.peerconnection.ice.proxy_only to true as well.
If that options is set it means Firefox will only connect through HTTP proxies.
You may either have set this option manually, or some privacy related web extensions also set that option.

Best
Nils
> _______________________________________________
> dev-media mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-media

shazzzzzzzz

unread,
May 2, 2019, 11:31:39 AM5/2/19
to mozilla-...@lists.mozilla.org
Hi Nils,

All fields under "media.peerconnection.ice" have default values.

I also tried couple of things
- I disabled the addons - Ghostery and uBlock Origin.
- Restarted Firefox in safe mode

I could reproduce the issue in both cases with Firefox not sending out any packets to TURN server.

Is there anything else I can try?

Thanks!
0 new messages