Since Janus was mentioned, I think this may also be related to another similar issue I was told about by some other Janus users. Apparently, the same ICE failure happens under some circumstances when using docker, IIRC when trying to talk to a colocated docker instance. I don't remember the exact details (I can look for them) but it was due to the "weird" NAT behaviour docker has when using its host networking, and so may be related to the VPN scenario described by Mikael. In that case too, though, Chrome was working while Firefox wasn't: my guess at the time was some different management of the ICE state machine and/or something related to prflx candidates, but I never got much into the details there.
Please let me know if there's any way I can help, Lorenzo Il giorno mercoledì 13 dicembre 2017 09:15:44 UTC+1, Mikael Nousiainen ha scritto: > I've made two gzipped packet capture files available here for 48 hours: > > https://expirebox.com/download/fb3256f9244ea32256fee9b62e517693.html > https://expirebox.com/download/a783df9cc23ccb127799d3e80a871870.html > > One of the includes setting up both sending and receiving stream (and it > looks like setting up sending goes further?) and the other one contains an > attempt to create receiving stream only. The data does include some > unnecessary TLS-encrypted packets that contain signalling traffic with Janus > server (I couldn't figure out how to filter it out now). > > -Mikael _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
