problem with tcp candidates in canary

[bryand...@gmail.com]

Hello,

The latest canary does not connect via tcp for me any longer.  

Given an offer like below, with a single tcp candidate, and a listening server on the other end, Chrome Stable and Beta will connect to the tcp candidate, but Canary will not.  Have not tested Dev.

The Canary peer connection goes to checking, but does not arrive at connected.  Can someone tell me what has changed regarding outbound TCP candidates?

OFFER:

v=0 o=- 1 2 IN IP4 127.0.0.1 s=- t=0 0 a=group:BUNDLE audio video a=msid-semantic: WMS default m=audio 5050 RTP/SAVPF 100 c=IN IP4 192.168.4.102 a=rtcp:1 IN IP4 0.0.0.0 a=candidate:0 1 tcp 2130714367 192.168.4.102 5050 typ host generation 0

a=ice-ufrag:vOwK0WiJ/3FgSWB

:

:

In the chrome_debug.log, I see:

[29469:1799:0715/083540:INFO:CONSOLE(194)] "connection state: checking", source: https://v6dev.ivocalize.net:8443/pctest.html (194) [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(794)] Jingle:Net[en0:192.168.4.100/32]: Allocation Phase=Relay [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(794)] Jingle:Net[vnic0:10.211.55.2/32]: Allocation Phase=Relay [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(794)] Jingle:Net[vnic1:10.37.129.2/32]: Allocation Phase=Relay [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(794)] Jingle:Net[en0:192.168.4.100/32]: Allocation Phase=Tcp [29472:4615:0715/083540:VERBOSE3:port.cc(222)] Jingle:Port[:1:0:local:Net[en0:192.168.4.100/32]]: Port created [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(483)] Adding allocated port for audio [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(513)] Jingle:Port[audio:1:0:local:Net[en0:192.168.4.100/32]]: Added port to allocator [29472:4615:0715/083540:VERBOSE3:tcpport.cc(123)] Jingle:Port[audio:1:0:local:Net[en0:192.168.4.100/32]]: Not listening due to firewall restrictions. [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(794)] Jingle:Net[vnic0:10.211.55.2/32]: Allocation Phase=Tcp [29472:4615:0715/083540:VERBOSE3:port.cc(222)] Jingle:Port[:1:0:local:Net[vnic0:10.211.55.2/32]]: Port created [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(483)] Adding allocated port for audio [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(513)] Jingle:Port[audio:1:0:local:Net[vnic0:10.211.55.2/32]]: Added port to allocator [29472:4615:0715/083540:VERBOSE3:tcpport.cc(123)] Jingle:Port[audio:1:0:local:Net[vnic0:10.211.55.2/32]]: Not listening due to firewall restrictions. [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(794)] Jingle:Net[vnic1:10.37.129.2/32]: Allocation Phase=Tcp [29472:4615:0715/083540:VERBOSE3:port.cc(222)] Jingle:Port[:1:0:local:Net[vnic1:10.37.129.2/32]]: Port created [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(483)] Adding allocated port for audio [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(513)] Jingle:Port[audio:1:0:local:Net[vnic1:10.37.129.2/32]]: Added port to allocator [29472:4615:0715/083540:VERBOSE3:tcpport.cc(123)] Jingle:Port[audio:1:0:local:Net[vnic1:10.37.129.2/32]]: Not listening due to firewall restrictions. [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(794)] Jingle:Net[en0:192.168.4.100/32]: Allocation Phase=SslTcp [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(794)] Jingle:Net[vnic0:10.211.55.2/32]: Allocation Phase=SslTcp [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(794)] Jingle:Net[vnic1:10.37.129.2/32]: Allocation Phase=SslTcp [29472:4615:0715/083540:VERBOSE3:basicportallocator.cc(639)] All candidates gathered for audio:1:0 [29472:4615:0715/083540:VERBOSE3:transport.cc(565)] Transport: audio, component 1 allocation complete [29472:1799:0715/083540:VERBOSE3:transport.cc(581)] Transport: audio allocation complete [29472:1799:0715/083540:VERBOSE3:session.cc(719)] Candidate gathering is complete. [29472:4615:0715/083610:VERBOSE3:port.cc(709)] Jingle:Port[audio:1:0::Net[en0:192.168.4.100/32]]: Port deleted [29472:4615:0715/083610:VERBOSE3:basicportallocator.cc(651)] Jingle:Port[audio:1:0::Net[en0:192.168.4.100/32]]: Removed port from allocator (5 remaining) [29472:4615:0715/083610:VERBOSE3:p2ptransportchannel.cc(1199)] Removed port from p2p socket: 2 remaining [29472:4615:0715/083610:VERBOSE3:port.cc(709)] Jingle:Port[audio:1:0::Net[vnic0:10.211.55.2/32]]: Port deleted [29472:4615:0715/083610:VERBOSE3:basicportallocator.cc(651)] Jingle:Port[audio:1:0::Net[vnic0:10.211.55.2/32]]: Removed port from allocator (4 remaining) [29472:4615:0715/083610:VERBOSE3:p2ptransportchannel.cc(1199)] Removed port from p2p socket: 1 remaining [29472:4615:0715/083610:VERBOSE3:port.cc(709)] Jingle:Port[audio:1:0::Net[vnic1:10.37.129.2/32]]: Port deleted [29472:4615:0715/083610:VERBOSE3:basicportallocator.cc(651)] Jingle:Port[audio:1:0::Net[vnic1:10.37.129.2/32]]: Removed port from allocator (3 remaining) [29472:4615:0715/083610:VERBOSE3:p2ptransportchannel.cc(1199)] Removed port from p2p socket: 0 remaining [29472:4615:0715/083610:VERBOSE3:port.cc(709)] Jingle:Port[audio:1:0:local:Net[en0:192.168.4.100/32]]: Port deleted [29472:4615:0715/083610:VERBOSE3:basicportallocator.cc(651)] Jingle:Port[audio:1:0:local:Net[en0:192.168.4.100/32]]: Removed port from allocator (2 remaining) [29472:4615:0715/083610:VERBOSE3:port.cc(709)] Jingle:Port[audio:1:0:local:Net[vnic0:10.211.55.2/32]]: Port deleted [29472:4615:0715/083610:VERBOSE3:basicportallocator.cc(651)] Jingle:Port[audio:1:0:local:Net[vnic0:10.211.55.2/32]]: Removed port from allocator (1 remaining) [29472:4615:0715/083610:VERBOSE3:port.cc(709)] Jingle:Port[audio:1:0:local:Net[vnic1:10.37.129.2/32]]: Port deleted [29472:4615:0715/083610:VERBOSE3:basicportallocator.cc(651)] Jingle:Port[audio:1:0:local:Net[vnic1:10.37.129.2/32]]: Removed port from allocator (0 remaining)

[Mallinath Bareddy]

Chrome always had disabled the incoming TCP connection, so due to that reason we stopped allocating TCP candidates by default now. If you want to allocate TCP candidates you need to use this flag "enable-webrtc-tcp-server-socket".

/Mallinath

--
 
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[bryand...@gmail.com]

This is concerning an outgoing TCP connection, not incoming.  Outbound (active) tcp connections appear to be broken broken.

[Mallinath Bareddy]

On Mon, Jul 15, 2013 at 9:41 AM, <bryand...@gmail.com> wrote:

oncerning an outgoing TCP connection, not in

True, but Chrome always had port 0 for TCP candidates. Hence we removed the tcp candidates from the candidates list by default. If flag is used, chrome should emit tcp candidates.

[bryand...@gmail.com]

Sorry, I don't understand.

I have an MCU that listens on a TCP socket.

If I provide an offer to Chrome, then Chrome should be able to connect to the server over TCP.  This works in all versions but the latest Canary.

Are you saying that I now need to set a flag on Chrome so that it can connect to an MCU over TCP ?  

If so, then it seems that you no longer support ICE-TCP at all.  Is this right?

--

[Mallinath Bareddy]

That's the case currently, you need to have flag added to make outgoing TCP connections. The goal was not emit tcp candidates when incoming connections are not allowed, but still be able to connect. We will fix this bug in the next iteration.

[bryand...@gmail.com]

Can you comment on when the next iteration that enables outbound tcp will happen?

[Mallinath Bareddy]

I hoping in tomorrow's Canary.

[Deep Pai]

Has this been fixed? Will chrome now support outbound tcp?
Also, I don't see chrome generating TCP candidates when using a turn server. Is RFC 6544 supported by chrome?

[Vikas]

Posting Mallinath's response. Not sure why it shows as post deleted.

Chrome supports outbound TCP connections. But it doesn't support TCP allocations on the TURN server, and at this point we have no plans to support it.