No relay candidates for IPv6 user

[Shockwave]

Hi,

I'm new to webrtc and ICE Negotiations, Currently when I try trickle ice from a machine which is on IPv6 network, the relay candidates are not generated. Thus causing the IceConnectionState of webrtc peer go into "checking" state for a long time. I can see that host and srflx candidate are generated and the username password for turn server is also correct as it works when I switch to an IPv4 network.

Is there any special setting which I have to make in my coturn configuration ???

[shakeeb]

Hi Sagar,

>>Is there any special setting which I have to make in my coturn configuration?

No. 

Running TURN server so that it allocates even IPv6 address is very easy.

You need to run coturn or rfc5766-turn-server on an instance where a global IPv6 address is available. If you don't configure listening or relay Interface in the config or command line,

Coturn or rfc5766-turn-server will detect IPv6 address and listen on it and will allocate IPV6 addresses.

You can also configure it manually. Then you have to specify global IPv6 and IPv4 address for relay Interface and Listening address. ( for IPv4 to IPv6 relay and for IPv6 to IPv4 relay) 

Please don't use the link-local address or site-local IPv6 address.    

I have tested using test_turn_client from http://turnserver.sourceforge.net. Everything is working fine.

But In my testing, I have found that google chrome doesn't support IPv6 allocation at all. I think this feature is not still complete. 

Thanks,

Shakeeb

[Sagar Pilkhwal]

Hi Shakeeb,

Thanks for your reply. I have setup VPC on aws and on aws ec2 dashboard, I can see that the aws instance where coturn is installed has been allocated an IPv6 address + IPv4 address. But using that IPv6 address I can't access the aws instance using ssh.
I think that the IPv6 allocation to that aws instance is having some issue but do you have any pointers for this issue I'm facing ?

Regards,
Sagar

[Sagar Pilkhwal]

Fixed the Issue related to IPv6 address not getting pinged from other network, but now when I try trickle ice from my IPv6 network machine, there are no srflx & relay candidates generated by the turn server and I get an error saying "Not Reachable" same error is there for another coturn server on IPv4 network but stun:stun.l.google.com:19302  is returning srflx candidates.

I don't know why the Turn servers are behaving this way, might be some issue with my IPv6 network which I have setup using Mac Mini Nat64 networking sharing.
Any help is appreciated.

Regards,
Sagar

[shakeeb]

Hi Sagar,

You can run tcpdump on the server and wireshark on the client and run the test.

You may get one the following things 

1) no request is sent from client to the turnserver and server is not receiving anything on the turn port.

2) request is sent from client to the turnserver but server is not receiving anything on the turn port.

3) request is sent from client to the turnserver and server is receiving some data on the turn port.

If you get (1) then the issue is the related to the Client. 

If you get (3) then the issue is the related to the Server.

If you get (2) then the issue is the related to the Network Configuration.

Thanks,

Shakeeb