Bug 1627238 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I would need to see a packet capture, but the following things look suspicious to me:

listening-ip=*0.0.0.0*

ICE(PC:21372137213721372 (id=214741111111 url=http://someurl)): peer (PC:21372137213721372 (id=214741111111 url=http://someurl):default) no such component for candidate candidate:foundation 2 udp 16777215 {publicIP} 14332 typ relay raddr *0.0.0.0* rport 64480 generation 0

I'm guessing coTURN is using 0.0.0.0 in its allocation responses, which is invalid. Maybe Chrome substitutes the source IP address when this happens as a workaround or something?
Revision 1 by
on 
I would need to see a packet capture, but the following things look suspicious to me:

listening-ip=**0.0.0.0**

ICE(PC:21372137213721372 (id=214741111111 url=http://someurl)): peer (PC:21372137213721372 (id=214741111111 url=http://someurl):default) no such component for candidate candidate:foundation 2 udp 16777215 {publicIP} 14332 typ relay raddr **0.0.0.0** rport 64480 generation 0

I'm guessing coTURN is using 0.0.0.0 in its allocation responses, which is invalid. Maybe Chrome substitutes the source IP address when this happens as a workaround or something?

Back to Bug 1627238 Comment 3