ERROR-CODE 443 (*Unknown error code*): Peer Address Family Mismatch (4)

238 views
Skip to first unread message

Sachin Parnami

unread,
Apr 26, 2016, 5:12:10 PM4/26/16
to TURN Server (Open-Source project)
Hi Team,

I am using 4.5.0.3 Version (https://github.com/coturn/coturn/wiki/Downloads).

I see my allocation request passed for IPv4 and got allocated  XOR-RELAYED_ADDRESS with port.
But when i try to do CreatePermission on same port with IPv4 i get above error.

As per RFC 
Receiving a CreatePermission Request

   If an XOR-PEER-ADDRESS attribute contains an address of an address
   family different than that of the relayed transport address for the
   allocation, the server MUST generate an error response with the 443
   (Peer Address Family Mismatch) response code


When Address family is different, and i missing, i am using same address family for my request.

Could there be something else which needs to be looked into ?

Regards,
Sachin

Oleg Moskalenko

unread,
Apr 26, 2016, 5:48:02 PM4/26/16
to Sachin Parnami, TURN Server (Open-Source project)
Investigate your request, through wireshark, it may be requesting ipv6 permission.

Sent from my iPhone
--
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 post to this group, send email to turn-server-project...@googlegroups.com.
Visit this group at https://groups.google.com/group/turn-server-project-rfc5766-turn-server.
For more options, visit https://groups.google.com/d/optout.

Sachin Parnami

unread,
Apr 26, 2016, 6:09:08 PM4/26/16
to Oleg Moskalenko, TURN Server (Open-Source project)
Thanks for your response Oleg, did try that already, it is actually
requesting on IPv4.
Regards,
Sachin Parnami

Oleg Moskalenko

unread,
May 8, 2016, 1:36:04 PM5/8/16
to Sachin Parnami, Agalya RAMACHANDRAN, TURN Server (Open-Source project)
Start wireshark and look into message number 19. Open the attributes
of the request. You are requesting IPv6 relay. So, when you are later
requesting permission for an IPv4 address, it gives you the 443 error
that means that the address families are mismatched.

Oleg

Sachin Parnami

unread,
May 9, 2016, 9:57:30 AM5/9/16
to Oleg Moskalenko, Agalya RAMACHANDRAN, TURN Server (Open-Source project), webr...@gmail.com
Thank you for looking into it Oleg.

Regarding Message 19(Allocation request) which got success(Allocation)
in message 20 with relay port 50594.
Request for create permission only went out for this port(50594) in
message 69 (CreatePermission) and got success response for it in
message 70.

Our concern is for IPv4 address(TCP/UDP)
1) which got allocation success in message 28 and failed create
permission in message 41 for port 16367
2) which got allocation success in message 32 and failed create
permission in message 47 for port 28639
3) which got allocation success in message 12 and failed create
permission in message 57 for port 18942
4) which got allocation success in message 8 and failed create
permission in message 59 for port 57110

Please let us know if our understanding is incorrect.

Regards,
Sachin Parnami

Oleg Moskalenko

unread,
May 9, 2016, 12:37:21 PM5/9/16
to Sachin Parnami, Agalya RAMACHANDRAN, TURN Server (Open-Source project), webr...@gmail.com
Sachin, you are probably mixing who and for what is creating
permission. The allocation was created in message 19 - with IPv6 relay
address. Then in message 41 you are trying to set permission for IPv4
peer. You cannot set communication between IPv6 and IPv4 addresses.
This is why it returns error.

Oleg

Sachin Parnami

unread,
May 9, 2016, 2:30:44 PM5/9/16
to Oleg Moskalenko, Agalya RAMACHANDRAN, TURN Server (Open-Source project), webrtc qa
Thanks again Oleg!
I might be misunderstanding it here.
just to clarify the scenario we have.

Would it be possible for a clientA to get allocation on IPv4 and IPv6
with TCP and UDP successful, response for it with XOR-RELAY-ADDRESS
assigned for all 4 above combination, if the sequence is
1) IPv4 with UDP from portx
2) IPv4 with TCP from portx1
3) IPv6 with UDP from portx2
4) IPv6 with TCP from portx3

Does step 3 and 4 overrides step 1 and 2 from Co-TURN point of view or
does CO-TURN maintains mapping of all 4 combinations?
Regards,
Sachin Parnami

Oleg Moskalenko

unread,
May 9, 2016, 6:12:18 PM5/9/16
to Sachin Parnami, Agalya RAMACHANDRAN, TURN Server (Open-Source project), webrtc qa
When you create an allocation you define the relay ip version and it cannot be changed

Sent from my iPhone

Sachin Parnami

unread,
May 10, 2016, 9:50:09 AM5/10/16
to Oleg Moskalenko, Agalya RAMACHANDRAN, TURN Server (Open-Source project), webrtc qa
ok, so if i create allocation from a client for IPv4 and IPv6, are
both of my allocations are valid at same time, or only one will be
valid?

Regards,
Sachin Parnami

Oleg Moskalenko

unread,
May 10, 2016, 11:24:38 PM5/10/16
to Sachin Parnami, Agalya RAMACHANDRAN, TURN Server (Open-Source project), webrtc qa
The server does not know whether allocations are from the same client.
For the server, any combination <remote-IP>:<remote-port> is a
separate independent client. In your case, the server will see two
unrelated clients: one for IPv4, another for IPv6.

Oleg

Sachin Parnami

unread,
May 11, 2016, 10:17:17 AM5/11/16
to Oleg Moskalenko, Agalya RAMACHANDRAN, TURN Server (Open-Source project), webrtc qa
Thank you Oleg!
I think i am on same page now.
Regards,
Sachin Parnami
Reply all
Reply to author
Forward
0 new messages