Make a conscious choice about default ICE server configuration

[johanhelsing]

In matchbox 0.3, we defaulted to stun:stun.johanhelsing.studio:3478, that seemed to work fine for me on:

@heartlabs reported some problems with stun requests timing out in Chromium. So we switched to "stun:stun.l.google.com:19302", which seemed to work fine.]

I did some tests on various platforms recently, and although everything seems to work fine with Google's stun server on windows, I no longer get connections in Firefox on linux.

server	FF (win)	FF (linux)	Chrome (win)	Chromium (linux)
stun:stun.l.google.com:19302	ok	no connection	ok	binding timeout (30s) then connects
stun:stun.johanhelsing.studio:3478	ok	ok	ok	binding timeout (30s) then connects

@heartlabs what os and browser + version did you experience the timeouts with?

[heartlabs]

I did now some extensive checks and found the following for me:

I tried to connect two clients with my game (WIP) where one of them ran on either

• My own PC (Windows)
• An Android Phone
• An iPhone

In all cases the matchbox_server was hosted on a different server

This is what came out:

• When I use Chrome in Windows - it doesn't work at all for me with any URL (I also tried stun.stunprotocol.org) - except when the second client is either in the same WIFI or in the public WIFI just out of the window in the street (I guess it's close enough that STUN isn't needed). I can't connect to a client via phone internet (tried with 2 phones)

• When I use Firefox in Windows - all of the 3 URLs work but I get a binding timeout (30s) first for stun.johanhelsing.studio:3478. I get that binding timeout on both my WIFI and the phone internet

• I can successfully play trans-network (using my phone internet) between my Windows Firefox and either a Safari on an iPhone or another Firefox on an Android (chrome on android doesn't work either here)

I cross-checked in a few cases with your box_game by the way and there were no differences with your game (matchbox_socket 0.3 I believe) and mine (matchbox_socket from master branch)

Now it would be interesting what results we get when we connect from different countries or even continents :)

[simbleau]

Is this still valid after #87 ?

[johanhelsing]

Is this still valid after #87 ?

I no longer have connection issues in FF on linux, so for me google's stun servers seem to work fine. I'm not sure what's causing the timeouts on chromium linux, though, but that has its own issue (#35).

@heartlabs: if you still have connection issues in chrome on windows where it should work, I think it would make sense to open a new issue.