CoTurn does not allocate IPv6 RELAY address

[Parixit Kaira]

I have a CoTurn setup which is deployed using docker and listening on both IPv4 & IPv6 addresses.  For this setup, IPv4 & IPv6 public addresses are directly assigned to the  host machine.

Everything works correctly, and we have been using this setup for 2-3 years now.

I recently noticed that this configuration works fine for IPv4 to IPv4 and Ipv6 to Ipv4 combination but not for IPv6 to IPv6. 

I looked at the ice candidates which are gathered by IPv6 clients, and found that the server always allocates IPv4 addresses for relay which works if the other side is on IPv4. However, if the other side is also IPv6 and cant reach IPv4 addresses than the ICE negotiation fails completely.

I have 2 questions based on the above behavior

1) Why does CoTurn does not allocate IPv6 relay candidates along with IPv4 candidates? Is observed behavior the correct behavior? If not, what needs to be changed for IPv6 relay candidates to be allocated.
2) On a dual stack network, why aren't the clients using IPv6 as host candidates? In my testing only IPv4 host candidates were exchanged.

I know that it is rare to find 2 clients on IPv6 only network, but I do fear that we will encounter that situation soon (especially with mobile devices).

[Parixit Kaira]

Please ignore my #2 question, as it seems like the issue is in my client setup. I can see atleast one of the client sending IPv6 address as host candidate.

[Mészáros Mihály]

What is your turn client? Is your turn client a web browser?
See option -A --allocation-default-address-family=<ipv4|ipv6|keep> in latest master.

--
You received this message because you are subscribed to the Google Groups "TURN Server (Open-Source project)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turn-server-project-rfc57...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/turn-server-project-rfc5766-turn-server/e21246ae-f6b2-4be8-9827-ef57b90b3ea8n%40googlegroups.com.

[Parixit Kaira]

Thanks for the response. 

Our TURN client composition is 60% web browsers, 30% ios webrtc library and 10% SIP Client library.